> For the complete documentation index, see [llms.txt](https://helpdocs.ycloud.com/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.ycloud.com/help-center/chatbot/chatbot-components/agent-takeover.md).

# Agent Takeover

“Agent takeover” represents **agent taking over the conversation**. When connected to the “Agent takeover” component, the conversation between the customer and the Chatbot will be assigned to an online agent for handling.

In "Agent takeover," you can choose the assignment rules:

1. Consistent with the assignment rules set for the current number.
2. Assign to a specific team for handling
3. Assign to a specific agent/sale for handling.

## Applicable Scenarios

It is used to handle complex conversations that the Chatbot cannot resolve, or it is recommended to place it towards the later stages of the Chatbot's process.

*For example: When the Chatbot's dialogue task has progressed to the later stages, you can add a component asking if the customer's needs have been met. When the customer indicates that the Chatbot has not solved the problem, you can connect the “Agent Takeover” component, allowing the agent to take over the current conversation to continue handling more complex issues.*

<figure><img src="/files/WTxZWCwaBmssJHTY5SfC" alt=""><figcaption></figcaption></figure>

Alternatively, you can also set up specific keywords that trigger human customer service. Once the corresponding Chatbot is triggered, the conversation will automatically be transferred to an agent.

<figure><img src="/files/FH5fRRdOv3BVxMtFKzFz" alt=""><figcaption></figcaption></figure>


---

# 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://helpdocs.ycloud.com/help-center/chatbot/chatbot-components/agent-takeover.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.
