Export DialNexa Call Data
The exported rows reflect the selected view or batch helper.Export Row Limits And Selected Columns
DialNexa uses the selected export columns to avoid loading conversation text that the CSV does not need. A single export supports up to5,000 matching calls when Call Transcript or Call Summary is selected, and up to 10,000 calls when both are left out.
If an export exceeds its limit, the dashboard shows the server’s exact row count and asks you to narrow the date range or add filters. When a heavy conversation column is selected, the message also explains that clearing both transcript and summary raises the limit to 10,000 rows.
The API accepts an export-only columns query value containing comma-separated column keys. Older clients can omit it and continue receiving the complete export shape under the 5,000 row limit. See List Calls for the request parameter.
Good Export Uses
Exports should support a clear operational process.Campaign reporting
Summarize completed, did-not-pick, and failed rows.
Sales handoff
Send qualified lead rows to a team.
QA review
Sample calls by status, duration, or sentiment.
Billing review
Compare duration and cost-related fields.
Export Hygiene
Filters were too broad
Filters were too broad
Narrow by date, campaign, status, or call id before export. If you do not need transcript or summary text, clear both columns to use the higher row limit.
Columns are missing
Columns are missing
Check whether post-call fields existed on the agent version used by those calls.
Values look inconsistent
Values look inconsistent
Review field definitions and transcript quality.
Sensitive data risk
Sensitive data risk
Treat exported rows as production data outside the dashboard boundary.
Related Reading
Call History
Filter before exporting.
Post-Call Results
Understand extracted columns.
Recipient Results
Export campaign groups.