Batch campaigns receive contacts from CSV files. Each row represents one queued call, and the column names become fields that the campaign can map to phone numbers, timezones, and flow variables.
Prepare the CSV
- Include a header row with non-empty, distinct column names.
- Include a phone-number column with country codes where required.
- Keep each file at or below 10 MB.
- Remove contacts that should not be called before uploading the file.
Use consistent values within each column. For example, keep phone numbers in one format and use valid timezone values if the campaign maps a timezone field.
Upload and map the fields
- Create or edit a Batch Calling campaign.
- Upload one or more CSV files in Select Trigger Type.
- Review the detected columns.
- Map the contact phone number and any optional timezone or dial-out-number fields.
- In Configure Call Flows, map the source fields used by the selected flow.
If the file or its headers change, review every mapping before starting the campaign.
Verify the import
Use a small CSV containing phone numbers you control. Confirm that each row enters the campaign with the expected values and that the outbound flow receives its mapped variables.
Uploading a CSV can queue real outbound calls once the campaign is running. Verify the list, cadence, phone-number routing, and compliance settings before starting it.
