​
Before creating a campaign

Confirm:
  • bot has passed test calls
  • outbound carrier numbers are configured
  • CSV has clean phone numbers
  • campaign time window is approved
  • concurrency is safe for available fleet and SIP capacity
  • retry rules match client expectations

​
Campaign wizard steps

The campaign wizard has five steps:
  1. Basics
  2. Number Pool
  3. Upload CSV
  4. Dialler Config
  5. Review

​
1. Basics

Set:
FieldGuidance
Campaign NameUse client, segment, date, and purpose.
BotSelect the bot already tested for this campaign.
After a campaign has started or been restarted, campaign identity and contacts are locked for audit safety. Use Clone if you need a new contact set.

​
2. Number Pool

Select outbound numbers. These become the pool CXB Dialler uses for campaign calls. Ops guidance:
  • choose numbers approved for the client/campaign
  • avoid using inbound-only DIDs
  • use enough numbers for the intended concurrency
  • confirm carrier trunk capacity separately

​
3. Upload CSV

CSV requirements:
  • must include phone_number
  • max size: 50 MB
  • max rows: 500,000
  • invalid numbers are skipped
  • duplicate numbers within the same CSV are skipped
  • every other non-empty column becomes a per-call variable
Example: 
phone_number,CUSTOMERNAME,due_amount,loan_bucket
+919999999999,Rajesh,50000,NPA-30
919888888888,Neha,12000,PRE-DUE

​
4. Dialler Config

Set:
FieldMeaning
Concurrency LimitMax simultaneous connected conversations (seats). Default 50. This is the seat budget that feeds the pacing formula — it is not the dial rate.
Campaign Modesingle_day or continuous — see below.
Time WindowAllowed dialing window in the selected timezone.
AMD (machine detection)Optional answering-machine detection — see below.
Callback DetectionEnable to let the bot schedule customer callbacks.
Max AttemptsMaximum attempts per contact.
Retry DelayMinutes before a retry can be scheduled.
Retry on System DispositionsSystem outcomes eligible for retry.
Custom Retry DispositionsBusiness dispositions from analysis that should retry.
Concurrency Limit (seats) is not carrier CPS. Concurrency caps how many conversations can be live at once (fleet protection). Carrier CPS caps how many new SIP dials launch per second (carrier protection) and is configured per carrier, not on the campaign. Both apply; the tighter one wins. See Pacing & retries.
Default retryable system outcomes are: 
no_answer, rejected, RNR, error, timeout

​
Campaign mode

ModeBehavior
single_dayWhen the time window ends, the campaign closes. Waiting contacts (pending/retry/callback) are moved to window_closed and the campaign is marked completed.
continuousThe campaign keeps running across days; contacts outside the window simply wait for the next window.

​
Answering-machine detection (AMD)

AMD is optional and configured in system settings (dialler.amd). When enabled, answered calls are briefly screened before attach:
SettingMeaning
enabledTurn AMD on. Default off.
action_on_machineteardown (default) or continue when a machine is detected.
action_on_unknowncontinue (default) or teardown when the result is uncertain.
See Answering-machine detection for outcomes and metrics.

​
Callback detection

Enable config.callback_detection.enabled to let the bot schedule customer callbacks. This is the campaign half of the callback double-gate; the bot must also have its callback toggle enabled. See Callbacks.

​
5. Review

Before clicking Create:
  • bot name is correct
  • number pool count is correct
  • CSV preview looks right
  • concurrency is safe
  • time window is correct
  • retry rules match the campaign brief
After creation, the campaign remains draft until Start is pressed.