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

# Monitor your voice agent

> See what happened on every Bolna Voice AI call: call history, webhooks, the executions API, extractions, call and hangup statuses, and latency metrics.

Every call your agent handles produces an **execution** — a record with the transcript, recording, cost, duration, status and any data extracted from the conversation. Read it in the dashboard, receive it on your server, or pull it over the API.

<CardGroup cols={2}>
  <Card title="Call history" icon="clock-rotate-left" href="/docs/agent-setup/call-history">
    Review conversations, recordings, metrics and logs in the dashboard.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/docs/post-call/polling-call-status-webhooks">
    Receive call status updates on your server as they happen.
  </Card>

  <Card title="Execution payload" icon="brackets-curly" href="/docs/post-call/execution-payload">
    What every field in a call record means: status, transcript, extracted data, cost, usage and latency.
  </Card>

  <Card title="Executions API" icon="code" href="/docs/fetch-agent-executions">
    Fetch one call or every call for an agent over the API.
  </Card>

  <Card title="Extractions" icon="table-list" href="/docs/prompting/using-extractions">
    Turn each conversation into structured fields you can act on. [Test them](/docs/prompting/testing-extractions) and read the [output format](/docs/prompting/extraction-output).
  </Card>

  <Card title="Call analytics" icon="chart-column" href="/docs/agent-setup/call-analytics">
    See how many calls complete, how many become conversations, and the best day and hour to call.
  </Card>

  <Card title="Latency" icon="gauge" href="/docs/concepts/latency">
    Understand what drives response time and what you can tune.
  </Card>
</CardGroup>

<Warning>
  Wait for the `completed` status before reading cost, duration, recording or extracted data. At `call-disconnected` those fields are still empty.
</Warning>

## Reference

| Page | Use it to |
| - | - |
| [Call statuses](/docs/post-call/list-phone-call-status) | Understand each state a call moves through |
| [Hangup statuses](/docs/post-call/list-phone-call-hangup-status) | Find out why and by whom a call was ended |
| [Latency metrics](/docs/concepts/call-latencies) | Break down where response time is spent on a call |

Workflow runs report separately through the [workflow execution webhook](/docs/workflows/execution-webhook).

When something looks wrong, start with [troubleshooting](/docs/troubleshooting/calls-fail-or-drop-early).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.