> For the complete documentation index, see [llms.txt](https://orimon.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://orimon.gitbook.io/docs/product-guides/setting-up-live-chat/transferring-to-live-agent.md).

# Transferring To Live Agent

This is a guide on how user will transition from a conversation with your bot to a live agent.

There are 2 ways a user can request a conversation with a live agent

### 1. By Clicking on live chat icon in the Chat Window Header

A simple button representing a chat-agent can be seen right next to the button to close the chat window as shown below

<figure><img src="https://55912965-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxUW02x9klXneNc1Bxtt6%2Fuploads%2FO1AJ5G4AitdiY9bmMgIb%2FScreenshot%20from%202023-06-13%2019-21-49.png?alt=media&amp;token=fe4ad223-cef7-4245-9d0c-489c47304763" alt=""><figcaption></figcaption></figure>

*Note : This button is only available after a few messages have been exchanged between the user and bot*

When the User clicks on this button, all members who are present on their dashboard will receive a notification of the user requesting live chat.

*Learn about the various components on a Live Agent Screen* [*here*](/docs/product-guides/setting-up-live-chat/live-chat-agent-screen.md)

### 2. By making a request through message

Orimon is a smart, human-like, virtual salesperson and can dynamically understand a user's requirements even if they write it directly into the message box!\
To request a chat with a Live Agent a user can directly say so in a message.

For example :    Typing "seek human intervention" will directly trigger a call to any available agents

<figure><img src="https://55912965-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxUW02x9klXneNc1Bxtt6%2Fuploads%2FZLr1cvmNCxn6YfWIo270%2FScreenshot%20from%202023-06-14%2013-15-40.png?alt=media&amp;token=129c85f7-00ab-4d3e-b330-a5ebc68e9d48" alt=""><figcaption></figcaption></figure>

Users can type in virtually any variation of this such as "talk to agent", "transfer to agent", "talk to human", "i need human assistance" or "can I chat with a customer support representative?"

The bot will automatically understand their request and transfer your chat to the live chat waiting queue.

*Learn about the various components on a Live Agent Screen* [*here*](/docs/product-guides/setting-up-live-chat/live-chat-agent-screen.md)

That's it! Your users can now transition smoothly from chatting with a bot to chatting with a human.

*Read about accepting and resolving a Live Chat request* [*here*](/docs/product-guides/setting-up-live-chat/live-chat-process.md)*!*&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://orimon.gitbook.io/docs/product-guides/setting-up-live-chat/transferring-to-live-agent.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.