Piga Dialer
Overview Campaigns Wallboard Settings

Sign in required

Settings are only available to an administrator.

Add a phone system

Editing

Choose what Piga should connect to.

Most PBXs ship a self-signed certificate. Leave this off unless you have installed a real one.

Add a line

A line is the route calls leave by, and its limits. The channel limit is the one that bites: under "calls go out through your PBX" each call uses two of the PBX's channels, not one.

What the PBX licence allows at once.
Operators throttle or block bursty callers.
Must be a number you own.

People

An agent's extension is the phone Piga rings when they click to dial. Without it, click-to-dial refuses rather than guessing.

Add someone

Editing
The phone Piga rings when they click to dial.
Lets their CRM dial as this person.
An administrator manages the system rather than taking calls, so they need no extension. Give them a Supervisor or Agent account as well if they should dial.

Send events from your PBX to Piga

On the PBX, open Integrations › API, tick Webhook Event Push and paste the address below. Events travel outward from the PBX, so it needs nothing open to the internet.

One setting decides whether any of this works. In Advanced Settings › Extension Status Monitor, tick the agent extensions. Until you do, the PBX sends no status updates, Piga never sees an agent become free, and campaigns sit there dialling nobody while everything looks healthy.

API keys

A key lets your CRM place calls through Piga — this is how a click-to-dial button authenticates.

Send call results to your systems

Piga posts every finished call to these addresses, signed. Delivery is queued and retried, so a system being down never slows the dialer.