> ## 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 Voice AI Documentation

> Start with DialNexa Voice AI documentation: understand agents, calls, workflows, integrations, monitoring, keys, and dashboard concepts before building live phone automation.

DialNexa Voice AI documentation helps you turn phone conversations into reliable work: answer a caller, collect facts, trigger the right follow-up, and review what happened. Start here if you need the product map before editing agents, assigning phone numbers, running batch calls, connecting integrations, or reading call outcomes.

<Note>
  A Voice AI platform has more moving parts than a prompt box. The prompt matters, but so do the number, version, voice, transcriber, webhook, retry rule, and the CSV that gets blamed only after lunch.
</Note>

## Choose A Useful Starting Point

If you are brand new, build something first: the [Quickstart](/quickstart) takes you from an empty workspace to a live test call in about 15 minutes. Otherwise, pick the section that matches the thing you are trying to understand right now.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Create an agent, buy a number, and place your first live test call.
  </Card>

  <Card title="Voice AI Foundations" icon="mic" href="/voice-ai/overview">
    Learn the speech, model, voice, latency, language, and privacy concepts that explain how calls behave.
  </Card>

  <Card title="Agents" icon="sparkles" href="/agents/overview">
    Understand the agent builder, published versions, prompts, variables, settings, and test calls.
  </Card>

  <Card title="Calls And Batch Calls" icon="phone" href="/calls/overview">
    Learn how phone numbers, inbound calls, outbound calls, web calls, campaigns, retries, and recipient files fit together.
  </Card>

  <Card title="Monitoring" icon="activity" href="/monitoring/overview">
    Read transcripts, recordings, call details, transfers, audio cache data, post-call fields, and exports.
  </Card>
</CardGroup>

## The Product Objects In Plain English

Use this table when a term appears before you have built the mental model.

| Object        | What it means                                                                                                                                  | Where you see it                                    |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| Agent         | The configured Voice AI caller, including prompt, language, voice, model, transcriber, settings, functions, and published version.             | Agents tab and agent builder                        |
| Agent version | A saved version of an agent that can be published and assigned to calls. Live traffic should point to a tested version.                        | Agent history, phone number assignment, batch calls |
| Phone number  | The inbound or outbound route that connects callers to a published agent version.                                                              | Phone Numbers tab                                   |
| Batch call    | A campaign that calls many recipients from a CSV file using the agent attached to an outbound number.                                          | Batch Calls tab                                     |
| Workflow      | A node-based automation that can call leads, wait, branch, send messages, and record lead history.                                             | Workflows tab                                       |
| Call log      | The audit record for a phone or web call, including status, recording, transcript, summary, extracted fields, transfer data, and cost details. | Call History tab                                    |
| Integration   | A connection or action that moves call results into WhatsApp, email, CRM, support, spreadsheets, or another business system.                   | Integrations tab and integration catalog            |

## Read Based On Your Role

<Tabs>
  <Tab title="Builder">
    Start with Voice AI Foundations, then Agents, then Agent Settings. This path helps you make a caller that sounds right and survives real callers.
  </Tab>

  <Tab title="Operator">
    Start with Phone Numbers, Batch Calls, Workflows, and Monitoring. This path helps you launch calls and confirm what happened.
  </Tab>

  <Tab title="Developer">
    Start with Platform Concepts, Keys, Webhooks, Data, and Reference. This path explains the product contract before you wire external systems to it.
  </Tab>
</Tabs>

## A Good First Reading Order

<Steps>
  <Step title="Get one call working">
    Follow the [Quickstart](/quickstart) end to end. Everything else in the docs is easier to place once you have seen one real call in Call History.
  </Step>

  <Step title="Map the system">
    Read the [platform map](/platform-map) so Agents, Phone Numbers, Batch Calls, Workflows, Integrations, Call History, Keys, and Webhooks have clear jobs.
  </Step>

  <Step title="Understand one live call">
    Read how Voice AI works, then read Calls Overview and Call Detail Page. This connects the live conversation to the evidence later shown in the dashboard.
  </Step>

  <Step title="Configure one agent carefully">
    Read Agents Overview, Prompts And Welcome Messages, Dynamic Variables, and the settings pages before publishing.
  </Step>

  <Step title="Send traffic slowly">
    Use test calls first, then a small outbound call or a small batch. Review Call History before scaling.
  </Step>
</Steps>

## Small Mistakes That Create Big Confusion

<AccordionGroup>
  <Accordion title="Editing a draft and expecting live behavior">
    A draft is not the same thing as the published version attached to phone numbers or campaigns. Confirm which version receives traffic.
  </Accordion>

  <Accordion title="Skipping the phone number assignment">
    An agent can be beautifully configured and still receive no calls if no inbound or outbound number points to it.
  </Accordion>

  <Accordion title="Treating post-call analysis as the transcript">
    The transcript records the conversation. Post-call analysis extracts specific fields from it, such as customer interest, outcome, age, or qualification result.
  </Accordion>

  <Accordion title="Ignoring KYC readiness">
    Batch Calls and some outbound actions depend on account readiness. If the UI blocks a launch, check KYC before tuning the agent.
  </Accordion>
</AccordionGroup>

## Related Reading

<CardGroup cols={2}>
  <Card title="Platform Concepts" icon="map" href="/platform-concepts">
    Learn the product objects before changing live configuration.
  </Card>

  <Card title="Agents Overview" icon="sparkles" href="/agents/overview">
    Understand the agent list and builder entry points.
  </Card>

  <Card title="Calls Overview" icon="phone" href="/calls/overview">
    Learn how calls start and where their evidence goes.
  </Card>

  <Card title="Monitoring Overview" icon="activity" href="/monitoring/overview">
    Use call evidence to debug and report outcomes.
  </Card>

  <Card title="Dashboard Integrations" icon="plug" href="/dashboard-integrations/overview">
    Connect call results to WhatsApp, email, workflows, and external tools.
  </Card>

  <Card title="Common Use Cases" icon="list-checks" href="/common-use-cases">
    Pick the product path for booking, reminders, support intake, and follow-up.
  </Card>
</CardGroup>