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

# Take over AI agent conversations as a human

> Take over AI conversations and escalate them to Helpdesk tickets for human support.

Takeover lets a teammate step into an AI agent conversation and turn it into a Chatbase Helpdesk ticket. Once taken over, the AI agent stops responding and the teammate handles the rest of the conversation directly. Use it when a customer's issue is too complex for the AI, needs a personal touch, or needs escalation.

Takeover is available on the Chat Bubble, Help Page, Center Stage, Email, WhatsApp, Messenger, and Instagram channels, as well as the Playground and Action previews. You can take over a conversation that is ongoing, paused, or ended. The Helpdesk must be enabled on the AI agent.

## How It Works

When a teammate takes over a conversation, Chatbase:

1. Stops the AI agent from responding to the customer
2. Generates an AI summary of the conversation, which costs no message credits
3. Creates a Helpdesk ticket linked to the conversation
4. Assigns the ticket to the teammate who took over

The new ticket gets:

| Field | Value |
| - | - |
| Status | **New** |
| Type | **Live chat** |
| Assignee | The teammate who took over |
| Team | None |
| Subject and description | From the AI summary |

Because the ticket is assigned straight away, team routing doesn't apply. [Triggers](https://chatbase.co/docs/user-guides/chatbot/help-desk/triggers.md) that run when a ticket is **Created**, including the default **Route to default team** trigger, are skipped. Triggers that run when a ticket is **Updated** do run, because assigning the ticket counts as an update.

## Who can take over

Anyone with permission to work on Helpdesk tickets for that AI agent can take over. It isn't limited to the Support Associate role.

## Which channels support takeover

| Channel | Takeover |
| - | - |
| Chat Bubble and iframe, Help Page, Center Stage | Yes |
| Playground and Action previews | Yes |
| Email | Yes |
| WhatsApp, Messenger, Instagram | Yes |
| API, Phone, Slack, mobile SDKs | No |
| Zendesk, Salesforce | No |

On **Email**, takeover cancels any AI email reply that is still pending or delayed. Later emails in the same thread go to the Helpdesk ticket instead of the AI agent. A brand-new email thread from the same customer may start a new conversation that the AI agent answers.

## Taking Over a Conversation

**1. Open the conversation**

Open **Activity > Conversations** in the dashboard and select the conversation.

**2. Click Takeover**

Click the **Takeover** button in the conversation header. The button is available unless the conversation is already taken over.

![Takeover button in the conversation header](https://mintcdn.com/chatbase/IdwsKzBZnpFWWv1e/user-guides/images/help-desk/take-over/take-over-button.png?fit=max\&auto=format\&n=IdwsKzBZnpFWWv1e\&q=85\&s=d24f449c26b31235023de4ef6230a44c)

**3. View the ticket**

After takeover, the newly created Helpdesk ticket opens in a new browser tab. The ticket includes:

* An AI-generated subject line and summary based on the conversation
* Customer details (name, email, or other identifiers)

![Helpdesk ticket created from a taken-over conversation](https://mintcdn.com/chatbase/IdwsKzBZnpFWWv1e/user-guides/images/help-desk/take-over/taken-over-conversation.png?fit=max\&auto=format\&n=IdwsKzBZnpFWWv1e\&q=85\&s=de37a58b981455733ca55f6d77edc3f4)

**Takeover** and **Take over in a new ticket** open the new ticket in a new browser tab. **Take over in this ticket**, which reopens a locked ticket, stays on the same page.

## Conversation States

Every conversation has an activity state that determines whether takeover is available:

> [accordion] Ongoing
>
> The conversation is active and the AI is responding. Takeover **is available**.

> [accordion] Paused
>
> The AI is paused on the conversation. Takeover **is available**.

> [accordion] Taken Over
>
> A teammate has already taken over the conversation. The **Takeover** button is replaced with a **View Ticket** button that links to the associated Helpdesk ticket.

> [accordion] Ended
>
> The conversation has ended. Takeover **is available**, so you can follow up with the customer.

A conversation becomes **Ended** when:

* It has had no message for **72 hours**. API and Zendesk Messaging conversations are not ended this way.
* The visitor clicks **End chat** in the Chat Bubble.
  A taken-over conversation is never ended for being idle.

## AI-Generated Summary

When a conversation is taken over, Chatbase uses AI to generate a summary so the teammate can understand the context without reading the entire conversation. The summary includes:

* A **subject line** for the ticket
* A **brief summary** of the customer's issue

The summary is generated in the same language the customer used in the conversation. It doesn't use message credits.

## What the Customer Sees

In web chat, such as the Chat Bubble, the customer sees the takeover happen:

1. The AI stops responding immediately
2. A loading spinner appears with the message **"Waiting for support agent to join"**
3. Once the teammate sends their first message, the spinner disappears and the conversation continues as a live chat

![Waiting for support agent to join spinner shown to the customer](https://mintcdn.com/chatbase/IdwsKzBZnpFWWv1e/user-guides/images/help-desk/take-over/waiting-support-agent.png?fit=max\&auto=format\&n=IdwsKzBZnpFWWv1e\&q=85\&s=bf62c4f07fd7e7c57e5cc89d02ce6b5d)

The spinner has no timeout. It stays until a teammate sends a message, or until the ticket is closed and the AI agent resumes.

> [!NOTE]
>
> The waiting message is automatically displayed in the customer's language. See [Localization](https://chatbase.co/docs/user-guides/chatbot/channels.md#localization) for more details.

On **WhatsApp, Messenger, Instagram, and Email**, takeover sends nothing to the customer. They simply start receiving the teammate's replies. On WhatsApp, if the customer's 24-hour messaging window has closed, the teammate must send a template message.

## Handing the Conversation Back to the AI

To let the AI reply again, close the ticket. Moving the ticket to a closed or cancelled status ends the takeover, and the AI picks up the next customer message.

**1. Open the ticket**

Open the taken-over ticket from the Helpdesk.

**2. Change the status**

Click **Update status** in the ticket header and pick a closed or cancelled status, such as **Closed** or **Cancelled**.

You can also close several tickets at once from the inbox. Select them and use **Status** in the bulk action bar.

> [!NOTE]
>
> If the conversation has another ticket that is still open, closing one ticket does not hand it back. The AI resumes only when the last open ticket on the conversation is closed or cancelled.

The closed ticket then locks. To talk to the customer again, see [Locked tickets](https://chatbase.co/docs/user-guides/chatbot/help-desk/ticket-lifecycle.md#locked-tickets). **Take over in this ticket** reopens the locked ticket with the **New** status and keeps its current assignee. That status change runs your **Updated** triggers.

## Multiple Takeovers

A single conversation can go through multiple takeover and AI resume cycles. Each time, the conversation is clearly divided into sections so both the teammate and the customer can follow the flow:

* A **"Live chat"** separator marks where a teammate took over
* An **"AI Resumed"** separator marks where the AI took the conversation back

For example, a conversation might flow like this:

1. Customer chats with the AI
2. A teammate takes over. A **Live chat** separator appears
3. The teammate resolves part of the issue and closes the ticket. An **AI Resumed** separator appears
4. Customer continues chatting with the AI
5. A new issue arises and another teammate takes over. Another **Live chat** separator appears

Each cycle creates a new ticket, unless you use **Take over in this ticket** on a locked ticket. The conversation timeline preserves the full history across all transitions.

![Conversation timeline showing Live chat and AI Resumed separators across multiple takeover cycles](https://mintcdn.com/chatbase/IdwsKzBZnpFWWv1e/user-guides/images/help-desk/take-over/multiple-takeovers.png?fit=max\&auto=format\&n=IdwsKzBZnpFWWv1e\&q=85\&s=4733a22eab0d87d4ab9f93c9c7c93fdf)

## Concurrency

Only one teammate can take over a conversation. If two teammates click **Takeover** at the same time, the first one to complete the action wins and gets the ticket. The second sees a generic error message. They can refresh the conversation to see that it has already been taken over and use the **View Ticket** button to open it.

> [!TIP]
>
> **Best practices:**
>
> * Review the conversation history before taking over so you have full context.
> * Takeover tickets start as New. Set them to On You while you work, and reply quickly.
> * Use internal **Notes** to document any steps you've taken so other teammates can pick up if needed.

## Frequently asked questions

> [accordion] Does takeover use message credits?
>
> No. The AI summary that creates the ticket's subject and description costs no message credits, and replies you send as a teammate don't either.

> [accordion] Why didn't my takeover ticket get a team?
>
> Takeover tickets are assigned directly to the teammate who took over, so triggers that run on ticket creation, including **Route to default team**, are skipped. Set the team on the ticket by hand, or add a trigger that runs when a ticket is **Updated**.

> [accordion] Does the customer get a message when I take over on WhatsApp or email?
>
> No. On WhatsApp, Messenger, Instagram, and Email, the customer receives nothing at takeover time. The first thing they see is your reply.

> [accordion] Does the AI keep answering emails after I take over?
>
> No. Pending AI email replies are cancelled, and new emails in that thread go to your ticket. A new email thread from the same customer may start a new conversation that the AI agent answers.

> [accordion] Can I take over API or phone conversations?
>
> No. Takeover isn't offered for API, Phone, Slack, mobile SDK, Zendesk, or Salesforce conversations.

> [accordion] What happens if I merge a taken-over ticket?
>
> The ticket you keep stays taken over. The ticket that is merged away is closed, and its conversation goes back to the AI agent once no other open ticket remains on it. Email conversations are never handed back this way. See [Merging](https://chatbase.co/docs/user-guides/chatbot/help-desk/ticket-lifecycle.md#merging).


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