> ## 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 Quickstart

> Create, publish, and test your first DialNexa voice AI agent, then verify the conversation in Call History before adding live traffic.

This DialNexa Voice AI quickstart helps you create an agent, publish its first version, run a test conversation, and verify the result in Call History. You do not need to buy a phone number before testing the agent.

## Who Is This DialNexa Quickstart For?

Use this guide if you are new to DialNexa and want the shortest safe path to a working voice AI agent. The example uses a Single Prompt Agent because it is the simplest option for one focused task.

By the end, you will have:

* One published agent version
* One completed web or phone test
* A call record with a status, transcript, and recording where available
* A clear next step for live inbound or outbound calls

## Before You Begin

Make sure you have:

* A DialNexa account and workspace
* Permission to create and publish agents
* A browser with microphone access for a web test, or a phone that can receive a test call
* Enough workspace balance or credits if your test method creates billable usage

<Note>
  Start with a test conversation. Buy or connect a phone number only after the agent behaves correctly.
</Note>

<Tip>
  If you have not signed up yet, watch the [creating your DialNexa account video tutorial](/docs/tutorials/platform-videos/creating-your-account) before starting this quickstart.
</Tip>

## Create Your First DialNexa Voice AI Agent

<Steps>
  <Step title="Open Agents">
    Sign in to the DialNexa dashboard and select **Agents** in the left navigation.
  </Step>

  <Step title="Create a Single Prompt Agent">
    Select **Create agent**, choose **Single Prompt Agent**, and name it `Appointment Assistant Test`.

    The name is visible to your team. Callers hear the welcome message and agent responses, not this internal name.
  </Step>

  <Step title="Choose the conversation stack">
    Select the language callers will use. For your first test, keep the default compatible model, voice, and transcriber offered by the builder.

    Test the default stack before comparing providers. This makes it easier to tell whether a problem comes from the prompt or from a provider change.
  </Step>

  <Step title="Add a focused prompt">
    Open the prompt editor and use this starter prompt:

    ```text theme={null}
    You are an appointment scheduling assistant for Acme Clinic.

    Your goal is to understand why the caller needs an appointment and collect a preferred day and time.

    During the conversation:
    1. Greet the caller and ask how you can help.
    2. Ask only one question at a time.
    3. Collect the caller's name, reason for the appointment, and preferred day and time.
    4. Repeat the details back for confirmation.
    5. Explain that the clinic team will confirm the final appointment.
    6. End the call politely.

    Keep responses short. Do not provide medical advice or promise that an appointment is confirmed.
    ```
  </Step>

  <Step title="Set the welcome message">
    Use a short opening that tells the caller what the agent can do:

    ```text theme={null}
    Hello, this is the appointment assistant for Acme Clinic. How can I help you today?
    ```
  </Step>

  <Step title="Publish version 1">
    Select **Publish**, enter a version title such as `v1 first test`, and confirm.

    Publishing creates the version used by test and live call routes. Later draft edits do not change this published version until you publish again.
  </Step>
</Steps>

## Test Your DialNexa Agent

<Steps>
  <Step title="Open the Test menu">
    From the agent builder, select **Test**.
  </Step>

  <Step title="Choose web or phone testing">
    Choose **Test via web** to speak through your browser without buying a phone number. Allow microphone access when prompted.

    Choose **Test via call** if you prefer to receive the test on a phone. Select the correct country code and enter the recipient number in the format requested by the dashboard.
  </Step>

  <Step title="Use realistic caller behavior">
    Ask for an appointment, change one detail, interrupt once, and ask an unrelated medical question. Confirm that the agent stays within scope and asks one question at a time.
  </Step>

  <Step title="End the conversation naturally">
    Confirm the collected details and let the agent close the conversation. Avoid ending the first test immediately after the greeting because you need enough evidence to review its behavior.
  </Step>
</Steps>

## Verify The Quickstart Result

Open **Call History** after the test and select the new call.

| Check          | Expected result                                                                                                |
| -------------- | -------------------------------------------------------------------------------------------------------------- |
| Status         | The call reaches an appropriate final status such as `completed`.                                              |
| Transcript     | The caller and agent turns appear in the correct order.                                                        |
| Recording      | Audio is understandable and the speaking pace feels natural, when recording is enabled.                        |
| Agent behavior | The agent collects the requested details, stays within scope, and does not claim the appointment is confirmed. |
| Version        | The call used the published version you intended to test.                                                      |

Your quickstart is complete when the agent handles the test correctly and the call evidence matches what you heard.

## Troubleshoot Your First Test

<AccordionGroup>
  <Accordion title="The Test menu asks me to publish">
    Publish the current draft, then start the test again. List-level and builder tests should use a published version.
  </Accordion>

  <Accordion title="The browser cannot hear me">
    Allow microphone access for the dashboard, confirm the correct input device is selected, and retry the web test.
  </Accordion>

  <Accordion title="The phone test does not start">
    Check the selected country code, recipient digit length, workspace readiness, and available balance or credits.
  </Accordion>

  <Accordion title="The agent gives long or unfocused answers">
    Make the goal and boundaries more explicit in the prompt. Add instructions to ask one question at a time and keep responses short.
  </Accordion>

  <Accordion title="The transcript is inaccurate">
    Confirm the selected language and transcriber match the caller. Then review background noise, microphone quality, and speaking pace.
  </Accordion>
</AccordionGroup>

## Add Live Traffic After Testing

Choose the next route based on your goal:

<CardGroup cols={2}>
  <Card title="Receive Inbound Calls" icon="phone-incoming" href="/docs/calls/inbound-calls">
    Buy or connect a phone number and assign the tested agent version for inbound calls.
  </Card>

  <Card title="Place One Outbound Call" icon="phone-outgoing" href="/docs/calls/outbound-calls">
    Assign an outbound route, call one recipient, and review the result.
  </Card>

  <Card title="Call A Recipient List" icon="list-checks" href="/docs/batch-calls/overview">
    Prepare a CSV, configure retries, and launch a small batch campaign.
  </Card>

  <Card title="Improve The Agent" icon="sliders-horizontal" href="/docs/agents/testing-agents">
    Test interruptions, silence, variables, transfers, and post-call fields before production use.
  </Card>
</CardGroup>