DialNexa Call Data Model - DialNexa Documentation

The DialNexa call data model describes what a call log can store. It includes call type, direction, status, sentiment, summary, transcript, JSON output, recording URL, end reason, retry context, workflow context, agent version, duration, credits, latency, transfer data, audio cache data, and sensitive deletion state.

The call data model is the dictionary behind Call History. Knowing the fields makes exports far less mysterious.

DialNexa Call Data Model Fields

These fields appear directly or indirectly in monitoring views.

Field	Meaning
type	Phone or web call.
call_direction	Inbound or outbound call direction.
status	Call lifecycle value such as created, initiated, sent, received, completed, did_not_pick, busy, no_answer, failed, cancelled, or retry_expired.
sentiment	positive, neutral, negative, or unknown.
summary	Generated call summary.
transcript	Conversation transcript data.
json_output	Structured output, webhook data, extraction results, workflow metadata, and related values.
recording_url	Audio recording location when available.
end_reason	Why the call ended, such as user disconnected, voicemail detected, user unreachable, destination forbidden, system at capacity, insufficient balance, or network failure.
sensitive_delete	Whether stored sensitive artifacts were deleted. Deletion also removes supported transcript, message-history, and recording URL fields nested inside task output.

End Reason Values

Use end_reason with status to understand whether a call ended normally, failed before connection, or needs retry handling.

End reason	Typical interpretation
`user_disconnected`	The caller or recipient ended the connected call.
`agent_disconnected`	The agent side ended the connected call.
`user_did_not_pick_up`	The destination did not answer, including provider no-answer, no user response, or timer-expired no-answer causes.
`sip_auth_failed`	The carrier rejected SIP authentication or outbound permission before ringing.
`sip_trunk_unreachable`	The configured SIP termination route or endpoint could not be reached.
`unallocated_phone_number`	The carrier reported that the well-formed destination number is not assigned.
`user_busy`	The destination was busy or rejected the call.
`user_unreachable`	The carrier reported a temporary unreachable state.
`invalid_phone_number`	The destination number was invalid.
`destination_forbidden`	The route or carrier rejected the destination.
`network_failure`	A network or carrier failure interrupted the call path.
`voicemail_detected`	Voicemail was detected.
`system_failure`	The platform could not complete call setup after retry handling.
`system_at_capacity`	Provider capacity or rate-limit handling was exhausted.
`insufficient_balance`	Wallet balance was too low to start the call.
`unknown`	No more specific reason was available.

Operational Context Fields

These connect a call to the thing that created it.

Agent version

Shows which agent version handled the call.

Campaign context

Links calls to batch campaigns and retry chains.

Workflow context

Links calls to workflow lead and node execution.

Transfer context

Connects call logs to transfer sessions and child calls.

Data Model Review Questions

Why is status not completed?

Use status, end reason, and recording to understand final state.

Where are custom fields?

Post-call values are extracted from JSON output task data and displayed in call detail.

Why does a workflow call show metadata?

Workflow lead id and node id link the call to lead history.

Statuses

Understand status values.

Call Detail Page

See model fields in UI.

Exporting Call Data

Export data fields.

​DialNexa Call Data Model Fields

​End Reason Values

​Operational Context Fields

Agent version

Campaign context

Workflow context

Transfer context

​Data Model Review Questions

​Related Reading

Statuses

Call Detail Page

Exporting Call Data

DialNexa Call Data Model Fields

End Reason Values

Operational Context Fields

Data Model Review Questions

Related Reading