Campaigns & Calls

Callbots

A callbot is the phone-number-facing identity: inbound DNIS routing lands on it, outbound campaigns dial from it. Each callbot has scenario schedules (which scenario answers, when) and one active scenario. The callbot page shows both, with a one-click path into the scenario's v2 canvas.

Campaigns

A campaign dials a contact list through a callbot's published scenario.

1. Create the campaign in a project and pick the scenario.
2. Load contacts — each contact row's columns become scenario variables, so in a prompt renders per call.
3. Schedule and pace — business-hours windows and dialing pace; the compliance engine enforces consent and quiet hours regardless of what the schedule says (ADR-0011).
4. Run — the campaign page shows per-contact state (queued, dialing, answered, finished, failed) and campaign-level outcome counts as they happen.

Campaign groups collect related campaigns for reporting.

Calls

Every call — inbound or outbound — gets a page of record:

• the transcript, turn by turn, with the node that produced each bot line;
• the recording, when recording was on for that leg;
• tags attached by TAG nodes or afterwards by an operator;
• the scenario version that actually ran, linked — so an old call is explained by the flow it really executed, not by whatever the scenario looks like today;
• the outcome, duration, transfer target if the caller reached an agent, and the compliance events for the leg.

The calls list filters by callbot, campaign, scenario, outcome, and date range; every row links into the call page.