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

# Test an agent with Simulations

> Replay real conversations or write customer scenarios, and see whether a change made the agent better before customers hear it.

Simulations let you try an agent on realistic conversations without calling or texting anyone. Replay calls you already had, or write the situations you worry about, then compare the results before you change the live agent.

Open **Agents › Simulations**. Admins and team managers can run them.

> [!NOTE]
>
> Nothing goes to a customer. A simulation never places a real call, sends a text, or books a visit.

## Two ways to test

> [card] Replay conversations
>
> Run recent real calls through the agent again. Choose how far back to look and how many times to replay each one. Best for checking that a change didn't break what already works.

> [card] Create scenarios
>
> Write the situations your team cares about. Best for something new, like a recall push or a tricky trade-in question.

For a quick check while you set up an agent, the **Quick simulation** in the setup steps runs one call or text. See [Set up an agent](https://docs.revdesk.com/app/agents.md#set-one-up).

## Run one

**1. Pick the agent**

Choose which agent to test.

**2. Pick the conversations**

Replay recent calls, or create scenarios. To start from a common worry, use one of these: **First impressions**, **Getting to the right person**, **Difficult callers**, **Inventory uncertainty**, **Booking a visit**, or **Callback follow-through**.

**3. Make the customer harder**

Add caller challenges such as **Talk over the agent**, **Correct an earlier detail**, **Noisy customer speech**, **Voicemail-like speech**, **A teammate takes over**, or **Ask to stop contact**.

**4. Review and run**

Check the setup and start the run. Results fill in as each conversation finishes.

## Read the results

Each conversation is checked against a few plain questions:

* Did the customer get a useful next step?
* Were answers and promises supported?
* Did the opening match this agent's setup?
* Was each action, such as a booking or a transfer, handled correctly?
* On calls: did it sound natural and responsive?

Each attempt is marked **Passed**, **Needs attention**, or **Not verified**. Replays also say whether the agent did **Better**, **Worse**, or the **Same** as the original call, with a score before and after (for example, `Score 45 → 82 · 8 better · 3 same · 1 worse`). Open any conversation to read it and see why it was marked that way.

## What to test before going live

| Scenario | What to check |
| - | - |
| **Booking a visit** | It offers real open times and books the right salesperson. |
| **Price or availability question** | The answer matches your knowledge and inventory. |
| **A time you're closed** | It offers other times instead of booking. |
| **A question it can't answer** | It says so and offers a callback. It doesn't guess. |
| **An upset customer** | It stays calm and gets them to a person. |
| **"Let me talk to a manager"** | It transfers or takes a message, as you set up. |
| **"Stop calling me"** | It confirms and stops. |

## Fix what you find

| What you see | Where to fix it |
| - | - |
| Wrong hours | The line's hours under **Bookings › Hours**. |
| Can't answer a basic question | Add it to [Knowledge](https://docs.revdesk.com/concepts/knowledge-base.md). |
| Sounds stiff | Try another voice or loosen the personality in [agent settings](https://docs.revdesk.com/app/agents.md#change-how-it-sounds-and-what-it-says). |
| Offers times when you're busy | Check the [calendar](https://docs.revdesk.com/concepts/your-calendar.md) connection. |
| Doesn't transfer | Check **Replies & Handoffs** on the agent. |

Then run the same simulation again and compare. Keep testing after launch: whenever you change instructions or knowledge, replay last week's calls before customers hear the change.


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