Prepare and launch a robot campaign

Before you start

An organization owner needs a robot queue, a registered line and an available server robot. Use contacts authorized for calling. The educational CSV below contains a fictional internal extension; replace it only with an authorized destination.

Click path

1. Open Кампании (/campaigns) and Новая кампания. Set Название кампании, Очередь робота and optionally Начать не раньше. That field shows the browser time zone; the queue calendar uses its own policy time zone.
2. Create the campaign and inspect its copied line, version, calendar, retries, duration and recording policy. Creation produces a draft without starting calls.
3. Choose Файл контактов. An educational CSV has header key,destination,name and row demo-1,301,Educational contact. Review the preview and click Импортировать контакты. key is a stable unique identity within this campaign; destination is the called number; name is optional.
4. Inspect added, duplicate and blocked counts. Do not replace a destination behind an existing key. If the response was lost, Повторить неподтверждённый пакет continues the exact same import.
5. Review Стоп-лист (/stoplist) and add prohibited destinations before launch. Matching uses the saved destination; adding an entry does not hang up a conversation already in progress.
6. Return and click Запустить. Calls follow capacity and schedule. Waiting inbound calls share the robot’s capacity.
7. Приостановить новые вызовы stops new assignments; Продолжить resumes them. To cancel, click Отменить кампанию, read the explanation and confirm. Verify actual active-attempt termination and media cleanup.

Enlarge screenshot

1 2 3 4

1. Запустить
2. Отменить кампанию
3. Файл контактов
4. Обновить контакты

Manage the stoplist

1. In Стоп-лист, complete Номер или добавочный and optional Причина. Click Добавить в стоп-лист and verify the row. Pending matching contacts are blocked; a current conversation is preserved.
2. To lift the prohibition, click Удалить из стоп-листа, then Подтверждаю удаление or Оставить. Removing an entry does not restart previously blocked contacts.

Enlarge screenshot

1 2

1. Номер или добавочный
2. Добавить в стоп-лист

Verify and recover

Inspect contact and active/completed/failed/blocked counts. A contact shows attempt count, last reason and next eligible time. Unconfirmed physical end and pending media cleanup require reconciliation, rather than a manual duplicate call.

Use Звонки for completed calls, Записи for permitted recordings and Супервизия for active conversations. Campaign execution requires no human staffing.

Fix the entire CSV before import: ambiguous columns, empty keys, invalid destinations and conflicting duplicates are rejected. Retry an uncertain import with its original package; refresh and inspect contacts after a revision conflict. If calls do not start, check runtime readiness, registration, scheduled start, calendar, stoplist and occupied capacity. Do not create another campaign to bypass an unconfirmed result.

Reconcile after a brief connection failure

Reopen the existing campaign and compare its contacts, active attempts and the result in Звонки. Losing the cabinet connection does not itself confirm that the telephone conversation ended. Keep the same campaign and contact keys; wait for an established attempt result before any manual retry.

If new assignments are paused, wait for runtime readiness and confirmed capacity release, then click Продолжить in that campaign. If the state stays unconfirmed, give your administrator the time, campaign ID and error text; omit cookies, line passwords and recording content. See the robot queue guide for queue recovery.