Campaigns
Campaigns organize outbound calls for a defined group of contacts. Use this page to create, launch, monitor, and review calling campaigns.What campaigns do
A campaign lets you:- prepare a list of contacts for outbound calls
- assign an agent and calling settings
- define when calls should run
- monitor campaign progress and results
- open individual calls for review
Campaigns list
When you open the Campaigns tab, you see the Total: N counter — how many campaigns match the current filters — and the Create campaign button. Use the filters to find a campaign:- Search by name — search campaigns by name.
- All statuses — Draft, Scheduled, Running, Paused, Completed or Cancelled.
- All agents — filter by the assigned agent.
- Only with call additions — keeps the campaigns that are open to having numbers added.
AutoTest are service entities of automated tests. They are not shown in the list or in the filters, for any role.
The campaign table shows:
- Name — campaign name.
- Agent — agent assigned to the campaign.
- Status — current state: Draft, Scheduled, Running, Paused, Completed or Cancelled, see Campaign statuses. Next to the status there may be the With call additions mark — the campaign is open to call additions — and the Dialing stopped mark, see Dialing stopped by the platform.
- Dates — campaign date range.
- Speed — dialing rate. A campaign on auto speed shows Auto · N/min, where N is the speed it dials at after the last recomputation, or just Auto before the first recomputation.
- Contacts — number of contacts in the campaign.
- Progress — the share of processed contacts: done, exhausted and suppressed. A draft has no progress. A campaign with call additions that has not ended shows Waiting for new calls under the progress.
- Created — creation date and time.

Campaign statuses
A campaign moves Draft → Scheduled → Running ⇄ Paused → Completed.- Draft — the campaign is created but not launched.
- Scheduled — the campaign is launched, but its start time has not come yet. At the start time it becomes Running on its own. If the start time has already come at launch, the campaign becomes Running straight away.
- Running — the campaign is dialing.
- Paused — dialing is suspended, by hand or by the platform, see Automatic pause.
- Completed — the queue is empty: every contact is processed. A drained queue does not complete a campaign with call additions. Any campaign also completes on its end date.
- Cancelled — the campaign was cancelled. A campaign can be cancelled from any non-final status, including a draft and a scheduled campaign.
Campaign details
The card header holds the campaign name, its status with its marks, and a line under the name: the campaign ID, Created with the date, the campaign time zone with the current time in it, Source — where the campaign was created (cabinet or API) — and Launched from, when the campaign was launched by a different route than it was created. Below the header are the key metrics. A draft has none: the metrics appear after launch.- Contacts — how many contacts the campaign holds.
- Reached — how many were reached, and what share of the total that is.
- Goal achieved — for how many contacts post-call analytics marked the call successful, and what share of the reached contacts that is. Next to it is the analysis coverage: “analyzed X of Y”, and when some calls cannot be analyzed, also “N not analyzable”. The card is shown only when the campaign agent has post-call analytics and Call success evaluation with a success criterion switched on.
- Average duration — the caption under it says what it counts: connected calls only.
- Dials — how many dialing attempts were made, with “contacts dialed: N” on its own line. When there were retries after technical failures, “infrastructure retries: N” is shown next to it.

Outcome and dialing configuration
-
Outcome breakdown — summarizes the outcomes of campaign calls. The card has two tabs:
- Contacts — each contact is counted once. A contact with at least one attempt that got through is counted by the best of those outcomes, in this order: Human Conversation, Transferred to operator, Call Screener – Human Handoff, Voicemail, Call Screener – Voicemail Handoff, Call Screener – No Handoff, Connected, no conversation, No media from callee. A contact whose attempts never got through is counted by its last finished attempt. Under the bars of this tab is the Goal achieved line — under the same conditions as the Goal achieved card. It is an overlay: it is not part of the category sum.
- Calls — each finished attempt is counted by its own outcome, with its own total. Cancellations before the dial are not calls, so their rows are not shown on this tab.
-
Dialing configuration — a card with the General and Schedule tabs.
- The General tab shows the agent, Classification, SIP trunk, Subgroup, Caller ID, Dialing speed (Auto on auto speed), Duplicate numbers, Retries, Voicemail policy, Dialing rules for the expert dialing logic, and Call in the contact’s local time (not shown on the US market profile). Retries are labelled as a pair of figures plus the interval mode: “9 retries · 10 dials, every 15 min”, “9 retries · 10 dials, intervals: 2 min, 5 min, 1 d” or “No retries · 1 dial”. The voicemail policy names its source: Campaign override, Organization policy or Organization default — not configured, see Voicemail message policy.
- The Schedule tab shows Start, End, the working hours and Time zone.
- Permission attestation — a separate card, on launched campaigns only: Signed by — who signed and in which capacity, organization user or operator on the organization’s behalf; Signed at; File with its row count and the file not stored mark when the source file is not stored; Fingerprint (sha256); Wording version. The call purpose itself — marketing, servicing or debt collection — and the consent tier derived from it sit in the Classification row of the dialing configuration. If the campaign has no signature, the card says “No attestation”.



Other blocks of the card
- Launch — on a draft. The button opens the Launch campaign window with the check: blockers, warnings and the attestation signature, see Campaign launch.
- Download report and Reports — reports on the calls of this campaign.
- Frequency settings — the campaign’s frequency limits, see Call frequency.
- Contacts upload — on a draft; Add a batch of calls — in any non-final status, see Adding calls.
- Upload history — when there was more than one file: the file versions, the launched mark and Download source file while the source is stored; see Campaign contacts.
- Campaign contacts — the contacts table with the Search by number and Search by contract fields, each contact’s state and its number of attempts.
Dialing speed after launch
On a scheduled, running or paused campaign you can change the dialing speed and turn auto speed on or off — the only settings that are not frozen at launch.- Open the campaign card and click Settings in the header.
- In the Campaign settings window pick a new value in Dialing speed, or tick Set a custom speed and enter any whole number from 1 to 200 in Calls per minute. To let the platform pick the speed, tick Auto-speed mode — the campaign needs an end date, and a campaign over several days also needs working hours, see Auto speed. All other fields in the window are read-only.
- Click Save — the button is active only when the speed or the mode differs from the current one and the value is valid.
Pause and cancel
The control buttons are in the campaign card header:- Pause — on a running campaign only.
- Resume — on a paused campaign only. The button opens the Resume campaign window with the same check as at launch: while there are blockers, the campaign does not resume.
- Cancel campaign — in any non-final status, including a draft and a scheduled campaign. Cancelling is irreversible, so the cabinet asks you to confirm it.
Automatic pause
The platform pauses a running campaign on its own when:- under the US market profile a contact has no location — without it the lawful calling window cannot be determined. Fix the file and upload the contacts again;
- the pre-call function answers “cancel” too often — the share of calls it cancelled has grown too large.
Dialing stopped by the platform
If something goes wrong with dialing, the platform can stop outbound calls for your organization. You then see the banner “Outbound dialing is stopped by the platform. Campaigns will not dial until it is lifted. Inbound calls keep working.”- Campaigns keep their status and get the Dialing stopped badge. They place no new calls; contacts wait in the queue and no attempts are spent. Once the stop is lifted, campaigns continue dialing on their own.
- The end date does not move. If the stop lasts past the end date, the campaign completes and the remaining contacts are closed as Exhausted.
- Calls in progress finish. Transfers and inbound calls keep working.
- The call button in the cabinet is disabled, and calls through the Web API are refused with
409 dialing_stopped(Calls). - Launch and Resume still work, with a warning: the campaign becomes Running (or Scheduled, if its start time has not come yet) and starts dialing only after the stop is lifted.
- Only the platform can lift the stop. If you see the banner, contact support.
Scheduler state
The Scheduler state block shows contacts by state — Waiting, Dialing, Done, Exhausted, Suppressed, and Awaiting evaluation when there are such contacts — a Next dial line with the target and actual pace (on auto speed — “auto · target N/min · actual M/min”, with “(subgroup limit)” when the target has hit a ceiling; under an organization concurrent call limit it is followed by Concurrency: how many calls are in flight, how many of them are talking and how many are allowed), Holds with the reason for each deferral, Suppressed by policy, DNC suppression phases, and the backpressure and infrastructure-retry counters. What each contact state means. The contacts table below the block shows the state under its own label — the second column. In brackets is the value the Web API returns.
Done, Exhausted and Suppressed are final states: these contacts are not called again, and the campaign progress counts them as processed.

Frequently asked questions
The campaign is running slower than I expected. Most likely some contacts are waiting for their window: in the US, a person in another time zone may only be reachable for a few hours of your day. Contacts are not lost — they are dialed once the permitted time arrives. Some contacts were never dialed. Three usual reasons: the number is on the do-not-call registry; the row was rejected at upload (check the import report); the contact is still waiting for its window. All three are visible on the campaign card. Why did calls stop at 20:00 when I set 21:00? That state’s law is stricter than federal. A campaign may narrow the window, never widen it. Outside the US profile the same logic applies to the organization calling window. What happens when the rules are updated? The rules are maintained and updated as laws change. A change applies to all subsequent calls, and already-deferred contacts are recomputed under the new rules. The change history is available for review. I changed the agent. Will a running campaign pick it up? Yes, once you publish. A campaign does not pin the agent version at launch: every new call takes the agent’s current published version. Draft changes that are not published are invisible to the campaign. Calls in progress at the moment of publishing finish on the old version. You do not need to pause the campaign to make a change; pausing helps only if no call at all may go out on the old version while you edit. Can the restrictions be switched off for one campaign? Depends which ones. Legal restrictions — no: state caps, Reg F and the calling windows cannot be disabled or widened, neither through the interface nor through the API. Narrowing your own window is allowed. Your own frequency limits — yes, by a platform administrator, for one campaign or for the whole company; see Switching the limits off.What is expected from you
- The right to call. The platform records your attestation but does not verify it: the grounds for calling are yours to establish.
- Accurate location data — for US campaigns the time zone and state are derived from what you supplied.
- A current do-not-call registry. If someone asked not to be called by another route — a letter, your website, an operator — add the number to the registry: the platform only learns of it from the conversation, and only on the US profile.
- A clean export. Duplicates, empty numbers, and lost leading zeros in ZIP codes are the most common reasons rows get rejected.
Campaign workflow
A campaign is assembled in a five-step wizard — covered in detail on Campaign launch:- Campaign — name, agent, and call classification.
- Schedule — dates, time zone, working hours.
- Dialing — telephony, speed, duplicates, retries, and dialing logic.
- Contacts — file upload and the import report.
- Review and launch — blockers, warnings, and the attestation signature.
Related pages
Campaign contacts
The contact file and its requirements, adding batches to a running campaign, file retention and do-not-call screening.
Call frequency
How often one number may be called, where the numbers come from, how to switch the limits off and what the switch does not touch.
US campaigns
Calling windows in the contact’s local time, and the geography the file must carry.
Launching a campaign
The five-step wizard: agent and classification, schedule, dialing, contacts, review and attestation.