Skip to main content

Campaigns are stateful orchestration objects, not static configs.

Use bulk_call_campaigns to manage dial strategy, schedule windows, and downstream reporting flows.

Endpoint families

  • Core CRUD: list/create/get/update
  • Lifecycle controls: launch, pause, resume, cancel
  • Cloning: clone, clone_prefill, save_as_template
  • Runtime insight: tasks, analytics, dispatch_health
  • Output paths: results_export, collection export
  • Planning helpers: capacity_preview, audience_timezone_analysis
1

Create in draft state

Validate agent assignment, number pool, schedule timezone, and concurrency.
2

Run preflight checks

Use capacity and timezone analysis before first launch.
3

Launch and monitor dispatch health

Validate task creation, first outcomes, and number health.
4

Pause/resume for controlled tuning

Tune script, schedule, or concurrency using pause-resume loops.
5

Export and reconcile

Pull results export and analytics for CRM and BI handoff.

Create and launch

Monitor and control

State transition guidance

Failure and rollback patterns

  • If launch fails with validation errors, fix campaign configuration before retrying.
  • If dispatch health degrades, pause campaign and investigate number health, schedule windows, or contact quality.
  • If analytics mismatch appears, compare webhook dedupe logs with tasks and results export output.