Launch automated outbound call batches by creating structured CSV items in the Outbound Calls CSV files column on the Workflow Builder page — queue calls and define call reasons for each recipient.
Define the outbound call list
To start a batch of calls, you must create a new item on the Workflow Builder page under the Outbound Calls CSV files column containing your CSV data.
Navigate to the Workflow Builder page in the Builder.
Locate the Outbound Calls CSV files column.
Click the + (plus) button at the top of the column to create a new item.
Enter a Title for the batch (e.g., "Leads Batch 1").
Paste your structured CSV data into the Body field.
Click Save.
Once saved, the AI Employee analyzes the data and queues the calls. You can create multiple batches by adding new items to the Outbound Calls CSV files column.
🗒️ NOTE
Once a CSV item has been processed, the system records it as a completed task and won't re-run it — even if you edit the body. To re-run calls (including the same phone numbers), create a new item by clicking + in the Outbound Calls CSV files column. This ensures the system treats the data as a fresh batch.
CSV format requirements
Your data in the Body field must be formatted as standard CSV.
Header row: Include a header row to define column names (e.g.,
Phone Number,Reason to Call). This helps the agent accurately identify the data.Phone numbers: Ensure phone numbers are in a valid international format (e.g., include the country code like
+1...). Invalid formats may prevent the call from being placed.Commas inside field values: Because CSV uses commas as delimiters, any field value that contains a comma must be wrapped in double quotes (
"). Without quotes, everything after the first comma in that value is treated as a new column and gets silently dropped.To include a literal double-quote character inside a quoted field, escape it by doubling it (
"").
❗❗ IMPORTANT
Avoid duplicate phone numbers in the CSV. Duplicates can lead to issues with calling logic and result tracking.
Example CSV data
Basic example (no commas in field values):
Phone Number,Reason to Call +1234567890,Follow up regarding the recent laptop purchase. Ask if they are satisfied with the service. +1987654321,Check in regarding their account. Inform them the account has been upgraded to premium status.
Example with commas in the Reason field:
If the reason text contains commas, wrap the field in double quotes. To include a literal " inside the quoted value, write it as "".
Phone Number,Reason to Call +12314123846,"Call to follow up on their recent visit. Mention the new membership tiers — Basic, Plus, and Premium — and ask which best fits their needs."
Without the surrounding quotes, everything after the first comma in the reason text would be silently dropped — the agent would only receive the partial string up to that comma.
Retrieve call results
Once the agent processes the calls, the results are written to a project attribute.
Navigate to the Attributes page.
Search for the
project_attributes_outbound_call_table_csv_resultattribute.Copy the content from the attribute value.
Save the content as a
.csvfile (e.g.,results.csv) to open it in spreadsheet software for analysis
🗒️ NOTE
If your list contains many entries (typically more than 50), the system will automatically generate multiple result attributes (e.g., ..._batch_1, ..._batch_2) to store the data.
You can also monitor and review outbound call activity in the following sections:
Sessions — Each outbound call creates a session. Review individual call transcripts and outcomes here.
Conversations — Call interactions appear in Conversations, useful for reviewing dialogue history per contact.
AKB > Task Manager — Shows the status of queued call tasks so you can monitor which calls are pending, in progress, or completed.
Related guides
Outbound SMS via CSV list — Launch automated SMS batches using the same CSV-based workflow. Navigate to the Outbound SMS CSV files column on the Workflow Builder page to queue two-way SMS conversations instead of voice calls.