> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# DialNexa Call Data Model

> Understand the DialNexa call data model, including status, direction, type, transcript, recording, summary, sentiment, post-call output, transfer data, retries, duration, credits, and deletion flags.

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.

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

## Core Call 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 sensitive artifacts were deleted.                                                                                                                                 |

## 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. |
| `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.

<CardGroup cols={2}>
  <Card title="Agent version" icon="git-commit" href="/agents/agent-versions-and-publishing">
    Shows which agent version handled the call.
  </Card>

  <Card title="Campaign context" icon="list-checks" href="/batch-calls/recipient-results">
    Links calls to batch campaigns and retry chains.
  </Card>

  <Card title="Workflow context" icon="workflow" href="/workflows/lead-history-and-debugging">
    Links calls to workflow lead and node execution.
  </Card>

  <Card title="Transfer context" icon="phone-forwarded" href="/calls/call-transfer">
    Connects call logs to transfer sessions and child calls.
  </Card>
</CardGroup>

## Data Model Review Questions

<AccordionGroup>
  <Accordion title="Why is status not completed?">
    Use status, end reason, and recording to understand final state.
  </Accordion>

  <Accordion title="Where are custom fields?">
    Post-call values are extracted from JSON output task data and displayed in call detail.
  </Accordion>

  <Accordion title="Why does a workflow call show metadata?">
    Workflow lead id and node id link the call to lead history.
  </Accordion>
</AccordionGroup>

## Related Reading

<CardGroup cols={2}>
  <Card title="Statuses" icon="list" href="/reference/statuses">
    Understand status values.
  </Card>

  <Card title="Call Detail Page" icon="panel-right" href="/monitoring/call-detail-page">
    See model fields in UI.
  </Card>

  <Card title="Exporting Call Data" icon="download" href="/monitoring/exporting-call-data">
    Export data fields.
  </Card>
</CardGroup>