Skip to main content

​
Overview

The Batch Calls list view provides comprehensive management capabilities for all your outbound call batch calls. From here you can create, monitor, and control batch call execution.

​
Batch Call List View

The batch calls list displays all batch calls in your project with key information:

​
Displayed Information

ColumnDescription
Batch Call NameName of the batch call
Total RecipientsNumber of recipients in the batch call
StatusCurrent batch call status

​
List Actions

From the list view, you can:
  • Create a new batch call
  • Search batch calls by name
  • Select an batch call to view details
  • Rename batch calls
  • Delete batch calls

​
Batch Call Statuses

Batch Calls move through various states:
StatusDescriptionActions Available
SCHEDULEDBatch call is scheduled to run (Send Now: picked up by worker every minute; Schedule: at selected date/time)Cancel, Delete, Rename, Reload
PENDINGBatch call is created but not yet startedCancel, Delete, Rename, Reload
RUNNINGBatch call is actively placing callsPause, Cancel, Delete, Rename, Reload
PAUSEDBatch call execution is temporarily stoppedResume, Cancel, Delete, Rename, Reload
COMPLETEDAll recipients have been processedRetry (if failures), Delete, Rename, Reload
CANCELLEDBatch call was manually stoppedRetry, Delete, Rename, Reload
FAILEDBatch call encountered a fatal errorRetry, Delete, Rename, Reload
Batch call statuses are updated in real-time. Refresh the page or use the Reload action to see the latest status.Note: The API returns RUNNING status, but in the dashboard it is displayed as “In Progress”. All other status values match between API and dashboard.

​
Batch Call Actions

​
Rename

Availability: Always Process:
  1. Click the actions menu (⋮) on the batch call
  2. Select “Rename”
  3. Enter new name (1-100 characters)
  4. Save changes
Renaming a batch call doesn’t affect its execution or recipients. Only the display name changes.

​
Reload

Availability: Always Behavior:
  • Fetches latest data from the server
  • Shows a loading indicator
  • Displays a success message on completion
  • Updates all batch call information
Use Cases:
  • Refresh batch call status
  • Update recipient counts
  • Get latest progress information
  • Verify current state

​
Pause

Availability: RUNNING batch calls only Process:
  1. Click the actions menu (⋮) on a RUNNING batch call
  2. Select “Pause”
  3. Confirm in the dialog
  4. Batch Call status changes to PAUSED
Behavior:
  • Stops placing new calls immediately
  • Calls in progress continue to completion
  • Batch Call can be resumed later
  • No data is lost
Pausing a batch call requires confirmation. In-progress calls will complete before the pause takes effect.

​
Resume

Availability: PAUSED batch calls only Process:
  1. Click the actions menu (⋮) on a PAUSED batch call
  2. Select “Resume”
  3. Confirm in the dialog
  4. Batch Call status changes to RUNNING
Behavior:
  • Batch Call continues from where it paused
  • Remaining recipients are processed
  • Respects time range constraints
  • Uses available concurrency capacity

​
Retry

Availability: FAILED, CANCELLED, or COMPLETED batch calls (with failures) Process:
  1. Click the actions menu (⋮) on eligible batch call
  2. Select “Retry”
  3. Confirm in the dialog
  4. Batch Call status changes to SCHEDULED (worker picks up within a minute), then RUNNING
Behavior:
  • Uses the same batch call ID
  • Retries only FAILED and NO_ANSWER recipients
  • Completed recipients are skipped
  • Batch Call restarts with remaining recipients
Retry only attempts calls for recipients that failed or didn’t answer. Successfully completed calls are not retried.

​
Cancel

Availability: SCHEDULED, PENDING, RUNNING, or PAUSED batch calls Process:
  1. Click the actions menu (⋮) on eligible batch call
  2. Select “Cancel”
  3. Confirm in the dialog
  4. Batch Call status changes to CANCELLED
Behavior:
  • Stops batch call execution permanently
  • Cannot be resumed (must use Retry instead)
  • In-progress calls complete before cancellation
  • Pending calls are not placed
Cancelling a batch call is permanent. You cannot resume a cancelled batch call, but you can retry it to attempt failed calls again.

​
Delete

Availability: Always Process:
  1. Click the actions menu (⋮) on the batch call
  2. Select “Delete”
  3. Confirm deletion
  4. Batch Call is permanently removed
Deleting a batch call is permanent and cannot be undone. All batch call data and history will be lost.

​
Batch Call Details View

Click any batch call to open the details view with comprehensive information.

​
Header Actions

The batch call header includes quick actions:
  • Reload - Fetch latest data
  • Retry - Retry failed calls (if available)
  • Delete - Remove batch call

​
Summary Tab

Displays batch call overview: Information Shown:
  • Batch Call status
  • Total recipients count
  • Start time
  • Progress (completed vs total)
  • Agent name
  • From number
Progress Indicators:
  • Visual progress bar
  • Completed count
  • Remaining count
  • Percentage complete

​
Configuration Tab

Shows batch call settings: Displayed Settings:
  • Send type (Send Now or Schedule)
  • Schedule date & time (if scheduled)
  • Timezone
  • Time range (start and end times)
  • Allowed days of the week
  • Reserved concurrency
Read-Only:
  • Configuration cannot be changed after creation
  • View-only for reference

​
Search Functionality

​
Searching Batch Calls

The search bar allows real-time searching by batch call name:
  1. Enter Search Query
    • Type in the search bar
    • Search is case-insensitive
    • Searches batch call names only
  2. View Results
    • Results update as you type
    • Matching batch calls are shown
    • Non-matching batch calls are hidden
  3. Clear Search
    • Click the X button or clear the search field
    • All batch calls are shown again
Example Searches: 
"Q1 2024" → Finds batch calls with "Q1 2024" in name
"follow-up" → Finds all follow-up batch calls
"test" → Finds all test batch calls

​
Concurrency Management

​
How Concurrency Works

Automatic Management:
  • Concurrency limits are defined by your subscription plan
  • Users do not see or manage live availability
  • Batch calls are SCHEDULED to run; the worker fetches them every minute, then they start (RUNNING)
  • Calls are queued and executed as capacity becomes available
Example Scenario: 
Plan allows 2 concurrent calls:
- Only 1 is available at batch call start
- Batch Call starts immediately with 1 call
- Second call starts automatically when capacity frees up
- Remaining calls queue and execute as capacity becomes available
Key Points:
  • Batch Calls never fail due to concurrency limits
  • Batch Calls never pause due to concurrency limits
  • All calls eventually execute
  • Execution may be gradual under high load
You don’t need to check or manage concurrency. The system handles it automatically based on your subscription plan limits.

​
Scheduling Management

​
Scheduled Batch Calls

SCHEDULED Status:
  • Send Now: Batch call is created with SCHEDULED status; the queue and worker fetch batch calls every minute, then it transitions to RUNNING
  • Schedule: Batch call is scheduled for a future date/time; the worker fetches every minute and picks it up when the scheduled time arrives, then it transitions to RUNNING
  • Shown in list with SCHEDULED status until picked up
  • Cannot be paused (not running yet)
  • Can be cancelled before start
Automatic Start:
  • The queue and worker fetch batch calls every minute
  • When a batch call is due to run (Send Now: immediately; Schedule: at scheduled time), the worker picks it up and status changes from SCHEDULED to RUNNING
  • No manual intervention required

​
Time Range Constraints

Deferred Calls:
  • Calls outside time range are deferred
  • Not skipped or lost
  • Execute when next valid time window arrives
  • Batch Call continues running
Example: 
Time Range: 9 AM - 6 PM, Monday-Friday
Batch Call starts Friday at 5:30 PM with 100 recipients

Result:
- First 10 calls placed immediately (within range)
- Remaining 90 calls deferred to Monday 9 AM
- Batch Call status remains RUNNING
- All calls eventually execute

​
Best Practices for Management

​
Regular Monitoring

Daily:
  • Check batch call statuses
  • Review progress on active batch calls
  • Monitor for failed batch calls
Weekly:
  • Review completed batch calls
  • Analyze success rates
  • Clean up old batch calls

​
Action Timing

Pause When:
  • Need to temporarily stop execution
  • Want to review progress before continuing
  • Testing batch call behavior
Resume When:
  • Ready to continue paused batch call
  • Want to process remaining recipients
Retry When:
  • Batch Call has failed recipients
  • Some recipients didn’t answer
  • Want to attempt failed calls again
Cancel When:
  • Batch Call is no longer needed
  • Want to stop permanently
  • Need to free up resources

​
Troubleshooting

​
Batch Call Stuck in SCHEDULED

Possible Causes:
  • Worker runs every minute—batch call may not be picked up yet
  • Scheduled time hasn’t arrived yet (for Schedule type)
  • System clock issue
  • Timezone mismatch
Solutions:
  • Wait up to a minute for Send Now; worker fetches batch calls every minute
  • Verify scheduled time and timezone for Schedule type
  • Check current system time
  • Cancel and recreate if needed

​
Batch Call Not Progressing

Possible Causes:
  • All calls are deferred (outside time range)
  • Concurrency limits reached
  • Network or system issues
Solutions:
  • Check time range settings
  • Verify concurrency capacity
  • Use Reload to refresh status
  • Check for system notifications

​
Cannot Perform Action

Possible Causes:
  • Action not available for current status
  • Batch Call in terminal state
  • Permission issues
Solutions:
  • Check batch call status
  • Verify action availability
  • Review action requirements
  • Contact support if persistent

​
Next Steps

Creating Batch Calls

Learn how to create batch calls

Recipients & Status

Manage recipients and track call statuses

Best Practices

Optimize batch call management