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

# Web & Chat Testing

> Test your agent in your browser with chat or voice

## Testing in Your Browser

Browser testing lets you iterate quickly without placing a phone call.

Click **Test Agent** in the agent header to open the test popover. Choose:

* **Chat** (text-only)
* **Web call** (microphone + live voice)
* **Phone call** (real outbound call)

## How to Run a Browser Test

<Steps>
  <Step title="Open your agent">
    Go to **AI Agents** and select the agent you want to test. Make sure your latest prompt is saved.
  </Step>

  <Step title="Open Test Agent">
    Click **Test Agent** in the top right corner. The test popover opens under the button.
  </Step>

  <Step title="Choose test type">
    Select **Chat** or **Web call** in the segmented control.
  </Step>

  <Step title="Start testing">
    * For Chat: click **Start chat**
    * For Web call: click **Start web call**
  </Step>
</Steps>

## Using Test Variables

Test variables let you simulate different scenarios without changing your agent's prompt:

* Variables defined in the prompt, multimodal prompt, or initial message appear in the test popover
* Update values to test different situations (e.g., "VIP customer", "Trial account")
* Move focus out of a variable field to save the value for future tests

## During the Test Call

After starting a browser test:

* **Chat mode** opens a text chat interface with streaming agent responses.
* **Web call mode** opens the floating call widget with connection state, live transcription, and call controls.
* Both modes stay active while you navigate through the dashboard.

You can continue working in the dashboard while the test call is active.

## Reviewing Test Results

After ending a test call:

1. Go to the **Conversations** tab in the main navigation
2. Find your test call (most recent at the top)
3. Review the transcript, goals achieved, and any tools triggered
4. Listen to audio playback if needed
5. Check that everything worked as expected

## When to Switch to Phone Testing

Use browser tests for fast iteration, then switch to phone testing when you need to:

* Test voice quality and natural speech timing
* Verify answering machine detection (AMD) settings
* Test call transfers to real phone numbers
* Confirm the experience matches what customers will hear

<Note>
  **Performance differences:** Web tests use browser audio and skip the phone network, so response time is usually faster and audio quality is often cleaner than real phone calls. Always test with real phone calls before launch to hear what customers will actually experience.
</Note>

See the [phone testing guide](/test/phone-testing) for detailed instructions on testing with real phone calls.

## Next Steps

<CardGroup cols={2}>
  <Card title="Phone Testing" icon="phone" href="/test/phone-testing">
    Validate voice quality and latency over real phone calls
  </Card>

  <Card title="Web Widget Configuration" icon="sliders" href="/manage/web-widgets/configuration">
    Configure and embed voice widgets on your website
  </Card>

  <Card title="Debugging" icon="bug" href="/test/debugging">
    Troubleshoot issues with conversation logs and diagnostics
  </Card>
</CardGroup>