DialNexa Batch Call Common Upload Errors

Fix common DialNexa batch call upload errors such as missing phone numbers, wrong CSV type, large files, mismatched variable headers, and route readiness problems.

Common DialNexa batch call upload errors usually come from file format, recipient phone number values, dynamic variable headers, file size, or selected outbound route. Fix the CSV preview before saving or starting a campaign.

If the preview table looks wrong, the campaign will not become wiser after launch.

Upload Error Checklist

Use this table before retrying an upload.

Problem	What to fix
No phone number column	Add a clear phone number column to the CSV.
Wrong file type	Upload a CSV file. Spreadsheet files should be exported to CSV first.
File too large	Reduce the file size or split the campaign.
Variable header mismatch	Use headers that match the agent version variables.
Empty required values	Fill required recipient numbers and important variables.
No selected outbound number	Select a number with an outbound agent version before downloading or uploading the template.
Unsupported country or prefix	Enable the destination route in Workspace Settings > Telephony Config, or change the recipient number.
Many row-level validation failures	Download the errors CSV, fix the listed rows, and upload the corrected recipient file.

Clean A Failed Upload

1. Download the template again

   Use the template for the currently selected number and agent version.

2. Copy data into the template

   Keep headers unchanged while moving rows over.

3. Remove formatting clutter

   Avoid merged cells, hidden formulas, and non-CSV spreadsheet features.

4. Upload a small sample first

   Test the first few rows before uploading the full list.

5. Check the preview

   Confirm phone numbers and variables appear in the expected columns.

File Problems That Look Like Product Bugs

Headers differ by one character

The agent expects the exact variable key. Keep names consistent.

Phone numbers include country twice

Check whether your file already includes country code before entering local digits.

Many rows show the same validation error

The dashboard groups destination validation failures by message and row number. When more than three rows fail, use Download errors CSV to get position, phone_number, and failed_parsing_reason for each failed row.

Values contain commas

CSV values with commas need proper quoting. Use a spreadsheet export instead of hand-editing when possible.

The selected agent changed

Template variables depend on the selected published agent version.

Related Reading

Recipient Files

Prepare a clean CSV.

Dynamic Variables

Match headers to placeholders.

Recipient Results

Review uploaded rows and outcomes.