Before You Begin
List the variables used by the published agent and collect one valid recipient row for each important scenario. Use consented test numbers before preparing a production file.Expected CSV Shape
Keep recipient files boring and predictable.
The upload flow reads headers from CSV files and supported spreadsheet files. For Excel uploads, DialNexa converts the mapped sheet data to CSV before sending it for campaign parsing.
Template Behavior
The download template changes with the selected number and agent version.Agent defaults first
The template uses default dynamic variable keys from the selected agent version when available.
Fallback placeholders
If no agent variables are available, the template includes generic placeholder variable columns.
Recipient preview
Parsed recipients are displayed in a table before launch.
File upload checks
The page validates CSV type and rejects large or invalid uploads.
Match Uploaded Columns
After upload, the Match CSV Columns modal lets you align the file with the selected agent version before the table is created.
When you confirm the mapping, DialNexa normalizes the selected phone column to
phonenumber and renames mapped variable columns to the expected agent variable keys. This lets operators upload files with readable business headers without editing the source spreadsheet first.
Review AI Name Suggestions
If the uploaded file has a mapped name column and fewer than1,000 leads, the create page can check the names for cleanup suggestions before building the recipient table. This is an optional dashboard review step. If name cleanup fails, DialNexa continues with the original names.
The Review AI Name Suggestions modal shows the original value, the suggested value, and row-level controls.
For batches over
1,000 contacts, the dashboard skips AI name cleanup and shows a warning. Review names in the source file before upload when large campaigns need standardized salutations.
Duplicate Phone Number Handling
The create page skips duplicate phone numbers by default before the recipient table is built. When the same non-empty phone number appears more than once, DialNexa keeps the first mapped row and removes later rows with that number. After upload, the page shows how many duplicate phone numbers were skipped.
Turn duplicate skipping off only when repeated calls to the same phone number are intentional for that campaign.
Prepare A Clean File
1
Select the outbound number first
This lets the page know which agent version variables to use.
2
Download the template
Start with headers that match the selected agent.
3
Fill realistic values
Use production-ready names, dates, amounts, and transfer destinations.
4
Upload and inspect rows
Check the preview table before saving or starting.
5
Fix errors before launch
Do not launch a file whose preview already looks wrong.
File Requirements
When Rows Fail Validation
The upload parser checks recipient phone numbers against the same destination validation rules used by single outbound calls. Duplicate removal happens before this validation when Skip duplicate phone numbers is enabled. Failed rows are grouped by reason, and larger failures offer a downloadable errors CSV. See Common Upload Errors for each error type, what it means, and how to fix the file.Verify The Recipient File
After upload, confirm the phone-number column, variable mappings, row count, duplicate handling, and validation results. Run a small batch and verify that spoken values match the intended CSV row.Related Reading
Dynamic Variables
Map variables to CSV columns.
Common Upload Errors
Fix file issues.
Recipient Results
Review row outcomes.