Voice campaigns

A campaign answers four questions: who gets called, by which agent, from which number, and inside which hours. It is the most configuration-dense screen in the voice surface, and every field on it is a compliance decision wearing a plain label.

Draft

Edit anything

Pending approval

Configuration locks

Approved

Configuration snapshotted

Running

Pause and resume return here

Completed

Terminal, with stopped and archived

Create the campaign

Audience classification

Calling windows, caps and retries

Retries are configured for you: a lead is retried on busy, no answer and provider failure. The Cooldown (min) is what stops that becoming harassment.

Import leads

The lifecycle

A campaign has nine statuses. Which buttons appear depends on where it is.

Button	What it does
Submit for approval	Draft → pending approval. Configuration edits lock until the decision
Approve…	Opens the approval dialog. Disabled until a passing preflight exists
Schedule…	Sets a future start on an approved campaign
Start	Begins dialing. Preflight re-runs server-side; launch is refused if any check fails
Pause	In-flight calls finish, no new dials until you resume
Resume	Preflight re-runs; resume is refused if any check fails
Stop	Cannot be undone. Remaining leads are never dialed by this campaign
Edit	Available while draft or paused. Changes require re-approval when the checks demand it

The statuses are draft, pending approval, approved, scheduled, running, paused, stopped, completed and archived. Stopped, completed and archived are terminal.

Approving

Arm queue: the shortcut for agent dial queues

A dial queue created from a lead gets a single confirmation instead of the full ladder. Click Arm queue — the dialog runs preflight automatically and reads One confirm approves and starts this agent's dial queue. Read any warnings, then click Arm queue & start calling.

It stays disabled until preflight passes: Preflight must pass before the queue can be armed. Once armed you get Queue armed — dialing proceeds within its calling windows. Ordinary campaigns keep the full submit → approve → schedule → start path.

The lead roster

The Leads table shows every lead with its membership status, attempts made, next attempt, last disposition and — the useful one — Block reason.

Lead statuses are pending, queued, dialing, in call, completed, retry scheduled, exhausted, opted out, suppressed, blocked and canceled.

Dial now dials one lead immediately. Its tooltip is precise: Dial this lead now (skips the schedule; every safety check still runs). It skips the schedule, not the per-dial preflight.

Call a lead from the CRM

You do not have to build a campaign to call one person.

Troubleshooting

Symptom	Cause	Fix
Approve is greyed out with Run a passing preflight first	No passing preflight result exists yet	Click Run preflight and resolve every error
The Approve dialog will not submit and nothing is failing	Warnings are present and need the typed acknowledgment	Type the phrase from the label exactly
Leads sit at pending and never get dialed	Outside the calling window, cooldown not elapsed, or the daily cap is reached	Read the Block reason column; widen the window, lower the cooldown, or raise the cap
Leads show blocked as suppressed or opted out	The number is in the opt-out registry or marked do-not-contact	Suppressed leads are never dialed — remove them, or restore opt-in from the call detail page
Imported rows are missing	Suppressed numbers are skipped server-side	Expected — they never enter the roster
The campaign was stopped by mistake	Stop cannot be undone	Create a new campaign; the remaining leads are not dialed by the stopped one
Dialing has not started although the campaign is running	The dispatcher works on a tick, inside each lead's local window	Wait for the window; check Block reason if it persists

Related

• Preflight check reference
• Reading call records
• Create your first voice agent
• Voice & Telephony settings