> ## 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.

# Set up an agent

> Pick the work an agent should do, check what it will say, try it, and turn it on.

An agent is an AI teammate that handles one kind of work: new internet leads, calls to a line, follow-up after the sale, and so on. Every agent works from the same contact record and calendar, so a lead who calls, then texts, is one conversation.

Agents handle the logistics. Your salespeople still sell: when a lead is ready, the agent books the visit or hands the conversation to a person.

## What an agent can do

Open **Agents** and choose **New AI agent**. Start from the work you need done.

| Card | What the agent does |
| - | - |
| **New internet leads** | Calls and texts a new lead within minutes, qualifies, and books a visit. |
| **Calls to a line** | Picks up when the floor can't, answers questions, books, or transfers. |
| **After the sale** | Checks in after the sale or service visit and asks for a review. |
| **Customers gone quiet** | Gives past customers a reason to come back. See [Reactivate past buyers](https://docs.revdesk.com/app/reactivate.md). |
| **Open recalls** | Tells owners about an open recall and books the fix. |
| **Inspections due** | Reminds owners before a warranty inspection is due. |
| **Business prospects** | Works a list of business prospects. |

None of these fit? Choose **Or describe it** and write the job in a sentence. RevDesk drafts the agent for you.

## Set one up

**1. Start**

Pick a card or describe the job. Under **More options** you can name the agent, choose **Where they work** (the whole workspace or one team), limit **Knowledge access**, and add a playbook.

**2. Review**

Read what the agent is told (**Instructions**), what it must never do (**Never**), **What it sends**, and **Where it runs**. Change anything that doesn't sound like your store.

**3. Simulations**

Run a **Quick simulation** by **Call** or **Text**. Nothing is sent or booked. For deeper testing, see [Simulations](https://docs.revdesk.com/app/simulations.md).

**4. Go live**

Read **What happens when you turn it on**, add a phone line if the agent should answer one, and choose **Turn it on**. Nothing starts before this step.

> [!TIP]
>
> A phone line is optional. An agent with no line still works its playbooks, such as follow-up texts and outbound calls. Choose **Get a number** to add one. See [Phone numbers](https://docs.revdesk.com/start/phone-numbers.md).

## Change how it sounds and what it says

Open an agent to see its tabs: **Results**, **Voice & Personality**, **Instructions**, **Knowledge & Tools**, **Call Flow**, **Replies & Handoffs**, and **Playbooks**.

| Setting | What it controls |
| - | - |
| **Name** | What the agent is called in RevDesk and on the call. |
| **How they answer** | With an AI voice, or by playing a recording. |
| **Voice** | Twelve voices with North American, Southern U.S., British, Irish, Australian, Filipino, and Brazilian Portuguese accents. |
| **Language** | **Multilingual (Auto-detect)** by default: the agent hears the caller's language and answers in it, even if they switch mid-call. |
| **Background sound** | **Silent** or **Quiet office**. |
| **Greeting** | The first thing it says when it picks up. Keep the recording notice if you change it. |
| **Voicemail** | What it leaves when nobody answers: AI voice or a recording. |
| **Personality and instructions** | Tone, rules, business context, and the qualifying questions it asks. |
| **Call memory** | Whether it remembers past calls **Per contact**, **Per agent**, or not at all (**Off**). |
| **Knowledge & Tools** | What it can look up, such as your [knowledge](https://docs.revdesk.com/concepts/knowledge-base.md), web search, and booking. |
| **Replies & Handoffs** | When and where it transfers a call, and what it says first. |

Business hours live on the line (**Bookings › Hours**), and quiet hours live in **Shared defaults**, so every agent follows the same rules. For outbound calls, the opening comes from the playbook step, not the inbound greeting. For reusable instructions across agents, see [Custom prompts](https://docs.revdesk.com/getting-started/customization/custom-prompts.md).

> [!NOTE]
>
> If someone asks whether they're talking to a person, the agent says it's an AI. When your workspace requires it, **AI disclosure and consent** is on for every agent.

## Give it playbooks

A playbook is a piece of work the agent runs: follow up with new leads, remind owners about recalls, win back quiet customers. Open the **Playbooks** tab and choose **Add to agent**. One agent can run several. To see each person a playbook is working, open the run and pick a person. See [Tasks](https://docs.revdesk.com/concepts/tasks.md) for how a run decides the next step.

## Keep it working

* **Status.** Each agent shows what it's doing now: **On a call now.**, **Ready to work.**, **Finish setup.**, or **No number rings this agent yet.**
* **Pause.** From the **⋯** menu. A paused agent doesn't take or place calls, and its running work pauses too. Resume it from the same menu.
* **Duplicate.** Copy an agent to run the same job for another team.
* **Remove.** Choose **Remove agent**. Move its active work and phone lines to another agent first.

## What agents will and won't do

> [card] Will
>
> Answer from your knowledge and inventory. Book on the right salesperson's calendar. Qualify with your questions. Transfer to a person when the customer asks or the conversation calls for it. Follow up by call, text, or email.

> [card] Won't
>
> Guess when your knowledge doesn't have the answer. Promise terms outside your policies. Claim to be human. Contact someone who opted out or during quiet hours.

When a question falls outside what it knows, the agent takes the details and offers a callback from a person. Read those conversations and add the missing answers to [Knowledge](https://docs.revdesk.com/concepts/knowledge-base.md).

## Check the first leads

After you turn an agent on, open its first few conversations in [Messages](https://docs.revdesk.com/app/messages.md):

* Did it answer quickly and ask the right questions?
* Did the visit land on the right salesperson's calendar, or the handoff reach the right person?
* Can a manager see why the lead was booked, handed off, or closed?

If a lead repeats information, check that your [lead source](https://docs.revdesk.com/start/lead-sources.md) maps the fields. If the wrong salesperson gets booked, check [routing](https://docs.revdesk.com/start/team-and-routing.md) and [calendar](https://docs.revdesk.com/concepts/your-calendar.md) settings.

> [!NOTE]
>
> **For developers.** The `/agents` resource in the [API reference](https://docs.revdesk.com/api-reference.md) returns runtime assistants, the voices attached to phone numbers and campaigns. They are not the same objects as the agents on this page, so counts won't match. Scopes are `agents:read` and `agents:write`.


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