Skip to main content
Batch Calls schedule many outbound calls from one lead file. Each accepted lead can produce a real, billable call, so validate the agent, file, destination coverage, schedule, and queue timing before starting a job. DialNexa runs one batch campaign per organization at a time, so a new job may enter waiting behind an existing running or waiting batch.

​
Lifecycle

​
Before upload

  • Publish the agent version the batch should use.
  • Use one row per destination and include all prompt variables as column headers.
  • Validate E.164 phone numbers and remove duplicates in your source file.
  • Start with a small test batch before a production audience.

​
Recovery

Do not repeat a timed-out create request until you list recent batches and confirm the first job was not created. Status transitions can fail when the batch is already in an incompatible state; fetch the batch and choose the next valid action. active can appear in legacy data, but new queue behavior uses scheduled, waiting, and running.