Run Batch Outbound Calls

Launch your first campaign end-to-end: Campaign -> Uploads -> Contacts -> Jobs -> Monitoring.

Audience

• Operators launching first outbound campaign
• Admins/support teams validating campaign delivery

Prerequisites

• At least one active agent configured
• At least one purchased/assigned number
• Contact upload file prepared (CSV or XLSX for batch uploads)
• Permission to create campaigns and jobs in workspace

End-to-end playbook

1) Campaign

1. Open Batch Outbound Calls in the sidebar.
2. Go to Campaigns.
3. Create a campaign with a clear operational name.

Expected result:

• Campaign is visible and selectable for job creation.

2) Uploads

1. Open Batch Uploads.
2. Upload a recipient file (CSV/XLSX).
3. Confirm file metadata and parsing complete without critical errors.

Expected result:

• Upload appears with expected contact counts and headers.

3) Contacts review

1. Open Batch Contacts.
2. Verify key fields (at least phone_number, plus any dynamic variables).
3. Resolve obvious data quality issues before launch.

Expected result:

• Contact set is clean enough for campaign execution.

4) Jobs

1. Open Batch Jobs and create a new job.
2. Select:
   • campaign
   • agent
   • upload
   • sending number
3. Start the job.

Expected result:

• Job enters active/running lifecycle and begins dispatch.

5) Monitoring and completion

1. Monitor job status in Batch Jobs.
2. Review progress and completion states.
3. Open logs/report view for outcomes after completion.

Expected result:

• You can confirm successful calls, failures, and completion summary from one workflow.

First campaign success criteria

• Campaign created and linked to a valid job
• Upload accepted with valid recipients
• Job started with selected agent + number
• Status and logs show measurable outcomes

Known constraints

• Concurrency and throughput depend on provider and account limits.
• Invalid recipient formatting can reduce delivery and completion rates.

Troubleshooting

Job starts but no calls dispatch

• Confirm job has valid campaign/upload/agent/number selections.
• Check contact file for missing or malformed numbers.
• Retry with a smaller test cohort first.

Campaign under-delivers

• Review job logs for failed recipients.
• Check provider/permit/concurrency limits.
• Re-run with cleaned contact set.

Duplicates or unexpected recipients

• Re-check upload source for duplicates.
• Validate mapping/headers before relaunch.

If unresolved, contact [e-mail] with workspace ID, campaign ID, batch job ID, and timestamped symptoms.

Related docs

• Campaigns
• Batch Uploads
• Batch Contacts
• Batch Jobs
• Batch Failure and Recovery Runbook
• Troubleshooting Hub