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

# Test your agent yourself

> Talk to your Brilo agent in the browser and by phone before real callers reach it, and know what to listen for.

Talk to your agent before anyone else does. You can call it from the dashboard in your browser with
no phone number involved, then call it properly from your phone once a number is attached. The browser
test finds most problems in about two minutes.

## Before you start

* An agent, even an unfinished one.
* Speakers and a microphone for the browser test, and your browser's permission to use them.
* A phone number attached to your agent for the phone test. See
  [Buy a phone number](/phone-numbers/buy-a-phone-number).

## Steps

<Steps>
  <Step title="Start a test call in your browser">
    Open your agent and start a test call from the dashboard. Your browser asks for microphone access
    the first time. You will see when your agent is listening and when it is speaking.
  </Step>

  <Step title="Ask the three questions your customers ask most">
    Not the questions you hope it answers. The three that actually come up: what something costs,
    whether you are open, and whether you can do a specific thing.
  </Step>

  <Step title="Try to book something">
    If your agent is meant to book, go through a booking end to end and check it appears in your
    calendar afterwards. See [Book appointments](/actions/book-appointments).
  </Step>

  <Step title="Ask for a person">
    Say "can I speak to someone" and see what happens. This is the moment agents most often disappoint
    callers, and the behaviour is worth confirming rather than assuming.
  </Step>

  <Step title="Now call it from your phone">
    Once a number is attached, ring it from your own mobile. A phone line sounds different from your
    laptop, and problems with pace and interruption only show up here.
  </Step>
</Steps>

## You will know it worked when

* Your agent answered, understood you, and finished the job rather than promising to pass a message on.
* The call appears in your call history with a written record and a score a minute later.
* The three questions you asked were answered from your own material, not invented.

## What to listen for

| Listen for                          | What it means when it is wrong                                                  |
| ----------------------------------- | ------------------------------------------------------------------------------- |
| The greeting                        | It is the one line every caller hears. Fix it first                             |
| Pace, and whether it interrupts you | The most common complaint, and fixable in **Configure**                         |
| Your business name and local terms  | Fix with [names and terms](/knowledge/teach-it-names-and-terms)                 |
| Length of answers                   | Chatty agents lose callers. Tell it to be brief                                 |
| What it does when it does not know  | Should take a message, offer a callback, or transfer                            |
| Whether it invented anything        | The most serious. See [Why it answered wrong](/knowledge/why-it-answered-wrong) |

## What else you can do here

* [Write down the situations worth re testing](/go-live/set-up-test-scenarios) so you can check them
  again after every change. Pro and above.
* [Review what earlier test runs did](/go-live/review-test-results).
* [Read the written record of your test call](/reports/read-a-call-transcript) to see exactly what
  your agent heard.
* [Work through the go live checklist](/go-live/go-live-checklist) before real callers arrive.

## If it did not work

**The browser test will not start.** Your browser is blocking the microphone. Allow it for the
dashboard, then reload. This is almost never an account problem.

**You call the number and nothing answers.** The number is probably not attached to an agent, or the
agent is not turned on. See [My agent is not answering](/calls/my-agent-isnt-answering).

**Your agent hears you but answers something unrelated.** It is filling a gap in its instructions or
its knowledge. See [Why it answered wrong](/knowledge/why-it-answered-wrong).

## FAQ

<AccordionGroup>
  <Accordion title="Can I test my agent before it goes live?">
    Yes, and you should. Start a test call from the dashboard and talk to your agent in your browser
    with no phone number and no real caller involved. It takes about two minutes and finds most
    problems.
  </Accordion>

  <Accordion title="Can I test without a phone number?">
    Yes. The browser test needs no number at all, so you can build and check an agent before buying
    anything. Only the phone test needs a number attached, and that is worth doing before you go live
    because a phone line sounds different.
  </Accordion>

  <Accordion title="Do test calls cost me anything?">
    Test calls use call minutes from your plan in the same way as real calls, so they are not free
    once your allowance runs out. The Free plan's 10 minutes are enough for several test calls. See
    [Limits](/supported/limits).
  </Accordion>

  <Accordion title="Do test calls show up in my reports?">
    Yes. A test call appears in your call history with its written record and its score, which is
    useful: read the record back to see exactly what your agent heard rather than what you thought you
    said.
  </Accordion>

  <Accordion title="Can my team test it too?">
    Yes. Anyone you have invited to your workspace can start a test call, and once a number is
    attached anyone can simply ring it. Having someone who did not build the agent try it is the most
    valuable test you can run.
  </Accordion>

  <Accordion title="Why does my agent sound different on the phone than in the browser?">
    A phone line carries less of the sound than your computer speakers, so every voice is a little
    narrower and small pauses are more noticeable. Judge the voice and the pace by the phone test, not
    the browser one.
  </Accordion>

  <Accordion title="What should I test before I go live?">
    Your three most common questions, one booking end to end, asking for a person, and one question
    your agent should not be able to answer, so you can see how it behaves when it does not know. See
    [Go live checklist](/go-live/go-live-checklist).
  </Accordion>
</AccordionGroup>

## Related

* [Go live checklist](/go-live/go-live-checklist) for the full pre launch list
* [Turn your agent on](/go-live/turn-your-agent-on) when you are happy with it
* [Write what your agent says](/agents/write-what-your-agent-says) to fix what you heard
* [Why it answered wrong](/knowledge/why-it-answered-wrong) if it invented something
* [Read a call transcript](/reports/read-a-call-transcript) to see what it actually heard