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

# Test your agent

> Try your agent directly from the browser using your microphone.

## Browser-based testing

Every agent can be tested directly from your dashboard without needing a phone number. This lets you iterate quickly on instructions and voice settings.

### Start a test call

1. Navigate to your agent's page in the dashboard.
2. Click the **microphone button** in the bottom-right corner.
3. Allow browser microphone access when prompted.
4. Start speaking — your agent will respond in real time.

> [!TIP]
>
> Test calls appear in your call history marked as "Test call" so you can review transcripts afterwards.

### What to test

* **Greeting** — does the agent introduce itself correctly?
* **Knowledge retrieval** — ask questions that require knowledge base content.
* **Edge cases** — try unexpected questions to see how the agent handles them.
* **Transfer triggers** — say something that should trigger a call transfer.
* **Language** — verify the agent responds in the correct language.

### Test minutes

Test calls consume **test minutes** from your plan's test allowance, which is separate from your production minutes.

> [!NOTE]
>
> Free plans include a limited number of test minutes. Paid plans include more generous test allowances. See [plans](https://docs.assist.fm/billing/plans) for details.

## Tips for effective testing

> [accordion] Use a quiet environment
>
> Background noise can affect speech recognition. Use a quiet room or a headset for the best results. The noise reduction setting on your agent also helps — try "Near field" for close-range microphone usage.

> [accordion] Test different scenarios
>
> Don't just test the happy path. Try edge cases like:
>
> * Asking about something not in the knowledge base
> * Speaking in a different language than configured
> * Interrupting the agent mid-sentence
> * Staying silent to test timeout behavior

> [accordion] Review transcripts after each test
>
> After ending a test call, check the call history for the full transcript. This helps you spot misunderstandings and refine your instructions.


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