Skip to main content
Exporting DialNexa call data creates CSV files from Call History. Exports can use current filters and date ranges, call ids, batch campaign ids, transfer details, summaries, custom post-call fields, and recipient-level values for reporting or follow-up. DialNexa Call History export menu showing selected call fields, the Transfer Details option, Dynamic Variables, and Download CSV.
Export only the rows you can explain. Future spreadsheet archaeology is nobody’s dream job.

​
Export DialNexa Call Data

The exported rows reflect the selected view or batch helper.

​
Export DialNexa Transfer Details

Transfer Details is an optional export choice. It expands into four CSV columns:
  • Transfer Outcome
  • Transfer Duration
  • Transfer Agents Dialed
  • Transfer Winner
Calls that did not reach a transfer use NA in all four fields. Leaving Transfer Details unselected avoids loading transfer data when it is not needed.

​
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 to 5,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

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.
Check whether post-call fields existed on the agent version used by those calls.
Review field definitions and transcript quality.
NA means the call has no stored transfer result for that field. Compare the call with its agent configuration and open the transfer tab on the call detail page before treating it as an export problem.
Treat exported rows as production data outside the dashboard boundary.

​
Open Call Exports In Excel

Call History CSV exports include UTF-8 encoding information so Excel can display multilingual text and the rupee symbol correctly. If an older export shows corrupted characters, download it again. Alternatively, import the CSV into Excel with UTF-8 selected instead of using an older saved copy.

Call History

Filter before exporting.

Post-Call Results

Understand extracted columns.

Recipient Results

Export campaign groups.