> For the complete documentation index, see [llms.txt](https://replai-1.gitbook.io/replai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://replai-1.gitbook.io/replai-docs/features-by-tier/live-tier.md).

# Live tier

## Live tier

**Live** includes everything in **Agent**.

That includes Replai Agent, actions from chat, MCP tools, and white-label.

It adds the human support layer.

### What does Live add?

Live adds:

* Human handoff
* Queueing and presence
* AI summary plus full transcript for the responder
* Up to 6,000 new conversations per month
* Seats for human responders

### How does handoff work?

The visitor can ask for a human, or the assistant can offer one.

The visitor confirms the handoff first.

Then the conversation enters a FIFO queue.

The least-busy online agent gets the chat next.

{% hint style="info" %}
The responder sees the full transcript and an AI-generated summary before replying.
{% endhint %}

### What happens while the visitor waits?

The widget shows queue position and presence.

Typing indicators stay visible during the live chat.

When the human resolves the conversation, control returns to the assistant.

If nobody is online and lead capture is enabled, Replai asks for the visitor email instead.

### How do seats work?

Each **Live** assistant includes **1 seat**.

Extra seats cost **€48.99 / month** or **€489.99 / year**.

Only owners, admins, and staff can hold seats.

### Related links

* [Handoff & lead capture](/replai-docs/answers-and-grounding/handoff-and-lead-capture.md)
* [Plans comparison](/replai-docs/features-by-tier/plans-comparison.md)
* [Replai Agent (in-product copilot)](/replai-docs/features-by-tier/replai-copilot.md)
* [Connecting your own tools (MCP)](/replai-docs/features-by-tier/connecting-your-own-tools-mcp.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://replai-1.gitbook.io/replai-docs/features-by-tier/live-tier.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.