Skip to main content

Adding calls

You can add new numbers to an existing campaign — a batch of calls. The numbers are appended to the campaign’s existing contacts; the launch file and its signature stay untouched.

Which campaigns accept calls

A batch is accepted by any campaign that has not ended: a draft, a scheduled, a running or a paused one. A completed or cancelled campaign does not accept calls. When the added numbers are dialed depends on the campaign status:
  • running — the numbers join the dialing queue right away;
  • paused — after the campaign is resumed; the accepted batch shows the line “The campaign is paused — dialing continues after it is resumed”;
  • draft — after the campaign is launched.

How to add a batch

  1. Open the campaign card on the Campaigns page.
  2. Find the Add a batch of calls block — it is below the attestation block (in a draft, below the contacts upload).
  3. Tick the permission attestation checkbox. Until it is ticked, the file is not accepted.
  4. Drop the file into the field or click Choose a file.
The attestation checkbox is cleared after every upload — accepted or refused — and when the attestation wording version changes. Tick it again for the next batch. Batches can be added by every role that has campaigns: Admin, Developer, Manager and Member. The batch signature is recorded in the name of whoever uploaded it — the same as the launch signature. More on permissions — Roles and access. If the campaign’s agent has been hidden from members, a batch for a campaign that is already launched is still accepted: hiding an agent does not stop a running campaign. A batch for a draft on a hidden agent is accepted too, but a Manager or Member cannot launch such a campaign — after the batch is accepted, the cabinet shows this as a blocker. File requirements: CSV or XLSX, up to 1,000 rows per batch, up to 10 MB. The columns are the same as in the campaign’s main contact file.

A batch is accepted or refused as a whole

Half a file never gets in. If the batch has even one row with an error, or even one number on the do-not-call list, no contact is added — the cabinet names the reason and shows a row-by-row report:
  • Batch of calls refused whole: rows with data errors;
  • Batch of calls refused whole: numbers on the do-not-call registry.
If the batch has both data errors and do-not-call numbers, the data errors are named as the reason. A refused batch stays in the Upload history with its row report. Fix the file and upload it again.
  • The same file is not accepted twice — neither a repeat of the launch file nor a repeat of an accepted batch. This way a double upload cannot duplicate numbers. A number that is already in the campaign but comes in a different file is accepted as a new contact and dialed again.
  • If the campaign has “Call in the contact’s local time” on (the Kazakhstan profile), every row of the batch needs a time zone.

After a batch is accepted

The cabinet shows Batch accepted: N contacts added and, below it, what currently prevents dialing, if anything does.
  • If the batch lacks a column the agent’s signature requires, this is a blocker: the numbers are not dialed while the column is missing.
  • If the batch lacks a column the launch file had and the agent uses, the cabinet warns you: for these numbers the variable will be empty.

An attestation for every batch

The signature under the launch file does not cover the added numbers: the right to call is confirmed for each batch separately. The batch signature is shown in the campaign card under the import results — who signed and when.

What the With call additions label means

The label is not about whether calls can be added, but about what happens when the queue runs empty:
  • a regular campaign completes by itself as soon as every contact is processed. After that, calls cannot be added;
  • a campaign With call additions does not complete when its queue is empty and accepts new batches until its end date. Only the end date or a cancellation closes it.
Until such a campaign ends, the list shows Waiting for new calls under its progress. When the queue is empty, the Scheduler state block of the campaign card shows the line “The queue is empty: the campaign waits for new calls and will not complete on its own — it closes on its end date … or when cancelled.” The label is set only when the campaign is created — with the Open the campaign to call additions checkbox on the Schedule step or through the Web API — and does not change afterwards. Such a campaign must have an end date no more than 30 days ahead, or it would never end. If the campaign reaches its end date with numbers still queued, they are closed as Exhausted.
Through the API a batch is added by the same mechanism: POST /v1/campaigns/{id}/calls. The numbers go in the JSON list calls (up to 1,000 items), the attestation confirmation goes in the body as "attestation": {"confirmed": true}; the Idempotency-Key header is required. The row checks, the do-not-call list and the all-or-nothing rule are the same as in the cabinet. Double sending is prevented by the idempotency key: repeating a request with the same key does not create a second batch. Details are in the Web API.