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

# Test Your Agent

> Place test calls, web calls, chats, and emails with sample contact data, then review transcripts, recordings, and action logs before going live.

Test every agent before you start it with real contacts. The **Test** button in the agent editor lets you call your own phone, talk in the browser, chat, or receive an email as if you were a contact, using sample values for each variable. Test conversations are kept in a history so you can compare versions of your script.

## Before you test

* **Save the agent.** The **Test** button appears only when there are no unsaved changes. It's hidden while **Insights Mode** is on.
* **Use an admin account.** Only admins can run tests.
* **Have a channel ready.** Phone tests need a phone number on the agent; chat tests need a messaging number; email tests need a mailbox.

## Test a voice agent

**1. Open the test panel**

Click **Test** in the editor header. The panel shows **Tests history**. Click **Initiate a new test**.

![Agent editor on the Workflow tab with the Test button highlighted in the header and the test panel open on the right, showing an Initiate a new test button and the message No calls made yet](https://mintcdn.com/voxiaai/ELyrb3NxuHh0ILKS/images/documentation/build-your-agent/test-panel.png?fit=max\&auto=format\&n=ELyrb3NxuHh0ILKS\&q=85\&s=2c1d1f71641d963a71aee319b7856f24)

The Test button opens the test panel with Initiate a new test and the tests history.

**2. Choose phone or web**

Pick **Phone Call** to have the agent call you, or **Web Call** to talk in the browser through your microphone. Agents set up for the web widget default to **Web Call**.

**3. Enter your details**

Enter your number in **International Phone Number** (with the country code, for example `+14155550123`). Then fill in a value for each variable. Required variables are listed first.

![Initiate a new test form on the Phone Call tab with required fields for name, International Phone Number, companyName, agentName, and productName, toggles for Load contact memories, Use a different language, and Use a different time zone, and a Start button](https://mintcdn.com/voxiaai/DUXJUr2YtBjwx26G/images/documentation/build-your-agent/initiate-new-test.png?fit=max\&auto=format\&n=DUXJUr2YtBjwx26G\&q=85\&s=a1e0dba56b3ed2f94e974bebcd62bd3d)

Initiate a new test: Phone Call or Web Call, your details, one field per variable, and the test options.

**4. Set options and start**

Adjust the options below and click **Start**. Your phone rings (or the web call connects) within a few seconds. Web calls also show any [in-call forms](https://docs.callers.ai/documentation/widget-agents/in-call-forms.md#test-it) in your script; phone tests don't.

### Test options

| Option | What it does | Default |
| - | - | - |
| Version | Which version to test (**Draft** or **Published**), if your account uses versions. | First published version |
| **Enable Voice Mail Detection** | Runs voicemail detection, so you can test your voicemail message by letting the call go to voicemail. Shown when the agent has voicemail on. | — |
| **Load contact memories** | Uses memories from earlier conversations with this number. | Off |
| **Use a different language** | Tests the agent in another language. Outgoing agents. | Off |
| **Use a different time zone** | Simulates a contact in another time zone. Outgoing agents. | Off |
| **Run Pre-Conversation Actions** | "When disabled, tests skip all configured pre-conversation actions, including any checks or data lookups." | On |

If a pre-conversation action blocks the call, you'll see "Call was not placed because it did not pass pre-call checks".

> [!WARNING]
>
> In-call actions run for real during tests. An action that creates a CRM record or sends a message will do so. Point actions at a sandbox, or use a test contact in your systems.

### Test incoming calls

For an incoming agent, call the agent's phone number from your phone, or use **Web Call** in the test panel. Incoming calls you place yourself are regular calls on the agent.

## Test a Text agent

Click **Test**, then **Initiate a new test chat**. Enter your phone number (international format with country code) and the variable values, then click **Start Chatting**. For incoming chat agents, also enter the **Initial message** the contact sends first. Reply from your phone to continue the conversation. See [Test before you launch](https://docs.callers.ai/documentation/text-agents/overview.md#test-before-you-launch) for channel-specific checks.

## Test an Email agent

Click **Test**, enter the address to receive the email, fill in the variables, and click **Send Test Email**. Reply to the email to test how the agent handles responses. See [Send a test email](https://docs.callers.ai/documentation/email-agents/email-setup.md#send-a-test-email).

## Review a test

Each test appears in **Tests history** with its status. Open a test to see:

* **Transcript**: every turn, plus any actions the agent ran. Click an action to see its request and response.
* **Summary**: the post-call analysis, when the call reached a goal.
* **Recording**: play it back to judge pacing, interruptions, and pronunciation.
* **Failed** tests show the reason.

Answers that came from the knowledge base are marked **Knowledge Base Results**, with the passages the agent used.

## How tests differ from live calls

* Test calls are marked as tests. Webhook payloads include `isTestCall`, so your systems can tell them apart.
* They're excluded from the **US Federal DNC Registry** check.
* They don't count toward insights, per-step statistics, or dashboards.

## A testing checklist

> **Happy path**
>
> Go through the script as the ideal contact. Check that variables are spoken correctly and the call ends cleanly.

> **Every branch**
>
> Answer differently each time to reach each subflow. Make sure each one ends, transfers, or loops back.

> **Objections and questions**
>
> Ask the questions your scenarios and knowledge base should cover. Ask something off-topic to see how the agent recovers.

> **Interruptions and silence**
>
> Talk over the agent, pause for a long time, and say "hold on". Adjust patience and no-interruption settings if needed.

> **Actions and transfers**
>
> Trigger every action and transfer. Check the request and response in the transcript.

> **Voicemail**
>
> Let a test call go to voicemail with **Enable Voice Mail Detection** on, and listen to the message left.

> **Outcomes and webhooks**
>
> Confirm that the success criterion and summary answers match what happened. If you rely on webhooks, check that your endpoint received the payload.

## Troubleshooting

> **The Test button is missing**
>
> Save your changes, turn off **Insights Mode**, and wait for any running test to finish. Only admins can test.

> **My phone didn't ring**
>
> Check the number format (country code included), that the agent has a phone number selected under **Channels**, and that your number isn't on the account's Do Not Call list. Open the test in **Tests history** to see the failure reason.

> **The agent says the wrong name or a placeholder**
>
> A variable value was empty or misspelled. Variable names are case-sensitive; check them in the Variables panel.

> **The web call has no audio**
>
> Allow microphone access in your browser and check that the right input device is selected.

## Related

> **[Versions and split traffic](https://docs.callers.ai/documentation/build-your-agent/versions-and-split-traffic.md)**
>
> Test drafts before publishing.

> **[Variables](https://docs.callers.ai/documentation/build-your-agent/agent-variables.md)**
>
> Values you fill in for tests.

> **[Agent results and insights](https://docs.callers.ai/documentation/using-callers/agent-insights.md)**
>
> Analyze live conversations.

> **[Report a call issue](https://docs.callers.ai/documentation/using-callers/reporting-call-issues.md)**
>
> Tell us when a call goes wrong.

> **[SDK playground](https://docs.callers.ai/sdk/playground.md)**
>
> Try the web widget with your own settings and theme.

> **[Path to production](https://docs.callers.ai/documentation/best-practices/path-to-production.md)**
>
> The go-live checklist: test, start small, monitor.


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