Call Campaigns

Bulk outbound calling — dial a contact segment from one line, with the campaign's own assistant on the answered leg. Creating BUILDS the target list and dials nothing; starting is a separate verb, because from that moment telephones ring in people's pockets and there is no undo.

📄️List calling campaigns (channel manager only)

Recent campaigns, newest first, with their counters and the live queue shape.

📄️Build a calling campaign (channel manager only)

Materialises the target list from the segment and stops — NOTHING is dialled. The counters in the response are what an operator checks before committing: how many will be rung, and how many were skipped because they never consented to calls, have no number, or have a malformed one. 422 when the chosen line cannot place calls.

📄️One calling campaign (channel manager only)

One calling campaign (channel manager only)

📄️Start (or resume) dialling (channel manager only)

Moves the campaign to `running`; the scheduled pass places the calls. Dialling inside the request would place calls at whatever pace the HTTP timeout allowed and none at all if the browser gave up. 422 with `campaign_not_startable` when the campaign is finished or cancelled.

📄️Stop dialling, keeping the queue (channel manager only)

Paused targets keep their place, which is the difference between a pause and a cancel. 422 with `campaign_not_running` when it was not dialling.

📄️Stop a campaign for good (channel manager only)

Calls already in flight are NOT hung up — somebody is talking to them, and cutting a live conversation because a list was cancelled is a worse outcome than the last few calls completing.