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

# Agents

> Create your AI agents, see how the front desk routes between them, and take them live.

Agents are the AI teammates that talk to your customers. Open them from **Build → Agents**.

![The Agents page with the front desk card and the specialist agents](https://mintcdn.com/magicwebs/lXS3DuVdQz1WpiFT/images/console/agents.png?fit=max\&auto=format\&n=lXS3DuVdQz1WpiFT\&q=85\&s=71b55ab8d45f319d5dab96b5b8e11f45)

## The page at a glance

* **Front desk card** (*Your AI team*): the front desk answers first on every channel and hands to your agents. It shows how many agents and conversations you have and the resolution rate. **Test routing** opens the front desk in the playground; **Configure** opens its settings.
* **Your agents**: one card per specialist with its role, tools and stats (conversations, resolution rate, average response). Each has **Test** and **Configure**. Sort by last updated, name or conversations.
* **Follow-up desk**: shows leads today, open leads and conversion rate. See [Leads](https://agent-docs.magicwebs.ai/leads/pipeline.md).
* **Cards / Map**: switch between the card view and the agent map.

### The agent map

The map shows each channel, the agent it goes to, and who each agent can hand over to. Click an agent to change its status, handover line, knowledge and tools in a side panel, then **Save changes**.

![The agent map: website chat to the front desk, then to Meera, Arjun and Priya](https://mintcdn.com/magicwebs/Y5otz65o1vDClhV_/images/console/agent-config.png?fit=max\&auto=format\&n=Y5otz65o1vDClhV_\&q=85\&s=7b7f98ab34b271d91018a792bb033c42)

## Create an agent

Choose **New agent**. There are three ways to start:

> [tab] Template
>
> Pick a ready-made agent: **Sales assistant**, **Lead qualifier**, **Customer support**, **Orders & after-sales**, **Appointment booking** or **Careers assistant**. Each says what it suits and when the front desk hands over to it. Optionally set the name customers see.

> [tab] Describe
>
> Answer **What should this agent do?** in plain words and choose **Draft the agent**. Magic Agent writes the agent using your company description, facts and catalogue.

> [tab] Blank
>
> Fill in **Internal name**, **Name customers see**, **Role** and **Front desk hands over when…**, then **Create agent**.

> [!WARNING]
>
> Every new agent starts as a **draft**. Drafts get no conversations. Review it in the [agent editor](https://agent-docs.magicwebs.ai/build/agent-editor.md), try it in the [playground](https://agent-docs.magicwebs.ai/build/playground.md), then set its status to **Active**.

## How routing works

1. A customer writes on any channel. The **front desk** answers first.
2. It reads each **active** agent's **"Hand over to me when…"** line and picks the one that fits.
3. It hands the conversation over silently. The specialist replies in the same chat.
4. Specialists can hand on to each other the same way. A conversation is never handed back to an agent that already had it for the same message.

For routing to work:

* Every specialist needs a clear "Hand over to me when…" line, written as a **condition**, for example: *"Hand over to me when the customer asks about home loans, EMIs, eligibility, partner banks or the subvention payment plan."*
* The agent must be **Active** and **Available for routing**.

> [!TIP]
>
> Test routing from the front desk's playground. Each reply shows which agents it passed through when **Tool trace** is on.

## Agent statuses

| Status | What happens |
| - | - |
| **Active** | Receives handovers and answers |
| **Draft** | Gets no traffic. You can still test it in the playground |
| **Paused** | Refuses every turn. The front desk can't be paused |


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