Batch calls let you launch a bulk outbound calling campaign. You choose an agent, a phone number, and a list of recipients — Sniko submits the campaign to ElevenLabs, which dials each contact and runs the AI conversation automatically.
How batch calls work
- You create a campaign with a name, an agent, a phone number, and a recipient list.
- Sniko schedules the campaign in ElevenLabs with a
scheduled_time_unix timestamp.
- ElevenLabs dials each recipient and conducts the conversation using the assigned agent.
- Progress is tracked via
total_calls_scheduled, total_calls_dispatched, total_calls_completed, and total_calls_failed counters.
You must accept the ElevenLabs batch calling Terms & Conditions before submitting your first campaign. Submitting without acceptance returns a batch_calling_agreement_required error.
Creating a campaign
Navigate to Batch Calls
Open Batch Calls from the sidebar and click New Campaign.
Fill in campaign details
| Field | Required | Description |
|---|
| Name | Yes | A descriptive name for the campaign |
| Agent | Yes | The AI agent that will conduct each call |
| Phone number | Yes | A number assigned to that agent |
| Scheduled time | No | Date and time to start (defaults to immediate) |
| Timezone | No | Your local timezone for scheduling |
Upload your contact list
Import recipients by uploading a CSV file or entering numbers manually.
Submit
Click Start Campaign. Sniko submits the campaign to ElevenLabs and redirects you to the campaigns list.
phone_number.
phone_number,first_name,account_id
+12025550101,Alice,ACC001
+12025550102,Bob,ACC002
+12025550103,Carol,ACC003
Additional columns beyond phone_number are passed as conversation_initiation_client_data to the agent, making them available as dynamic variables during the conversation.
+12025550100). Rows with an invalid format will fail during dialing.
Validated recipient fields
| Field | Type | Required |
|---|
phone_number | string (E.164) | Yes |
conversation_initiation_client_data | object | No |
Scheduling
If you provide a scheduled time, Sniko converts it from your local timezone to UTC before sending to ElevenLabs. If no time is provided, the campaign starts immediately (scheduled_time_unix defaults to the current Unix timestamp).
// Example payload submitted to ElevenLabs
{
"call_name": "[customer-uuid] Q2 Outreach",
"agent_id": "agent_abc123",
"agent_phone_number_id": "pn_xyz789",
"scheduled_time_unix": 1748736000,
"recipients": [
{
"id": "550e8400-e29b-41d4-a716-446655440000",
"phone_number": "+12025550101"
}
]
}
Monitoring progress
Open a campaign from the list to see its detail page. The detail page shows:
| Metric | Description |
|---|
| Status | pending, in_progress, completed, or failed |
| Scheduled | Date and time the campaign is set to run |
| Total scheduled | Number of contacts in the campaign |
| Dispatched | Calls that have been initiated so far |
| Completed | Calls that finished successfully |
| Failed | Calls that could not connect |
| Progress | Percentage of dispatched vs. scheduled |
Filtering campaigns
From the campaigns list, you can filter by:
- Name — partial text search across campaign name and agent name
- Status — show only campaigns in a specific state
Results are paginated at 12 campaigns per page.
Cancelling a campaign
A campaign that has not yet completed can be cancelled from its detail page.
POST /batch-calls/{id}/cancel
Retrying a failed campaign
If a campaign ends with failures, you can retry it:
POST /batch-calls/{id}/retry
Quota limits
Submitting a new campaign requires the quota.check:batch_calls middleware to pass. If your plan’s batch call quota is exhausted, the POST /batch-calls request returns a 403 error.
Quota is checked at submission time, not at scheduling time. If your quota runs out between creating a scheduled campaign and its scheduled start time, the campaign may still be accepted but may not run.
Campaign isolation
Each campaign name is prefixed with your customer UUID internally (e.g. [uuid] Campaign Name). The UI strips this prefix on display. When loading the detail page, Sniko verifies the prefix matches your account before rendering — unauthorized access returns a “not found” error.