> For the complete documentation index, see [llms.txt](https://guide.tiledesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.tiledesk.com/ai-chatbots-and-automation/quick-start/how-to-transfer-my-chatbot-to-a-live-agent.md).

# How to transfer my chatbot to a live agent

#### Intro <a href="#intro" id="intro"></a>

What if, during a conversation, you want a **chatbot-human handoff**? Chatbot-human handoff is when you are transferring the conversation from a chatbot to a live agent.

Tiledesk's No Code Visual Builder allows you to set up a live chat with the option to hand over the conversation to a human agent when available. Additionally, if no agents are online, you can collect customer contact information for follow-up. In this tutorial, we'll guide you through the three easy steps to achieve this.

{% embed url="<https://www.youtube.com/watch?embeds_referring_euri=https://gethelp.tiledesk.com/&v=YuWQWdN6HjY>" %}

#### Step 1: Set Up Your Start Message <a href="#step-1-set-up-your-start-message" id="step-1-set-up-your-start-message"></a>

* Begin by setting up your chatbot's start message.
* Add a button to the start message to lead to agent handoff when clicked.

#### Step 2: Draw a Path for a New Block <a href="#step-2-draw-a-path-for-a-new-block" id="step-2-draw-a-path-for-a-new-block"></a>

* Draw a Path from the button exit port to create a new block by choosing “If Online Agent” from the menu
* Name it (e.g., "Handoff").

#### Step 3: Create 2x Paths  <a href="#step-3-create-2x-paths" id="step-3-create-2x-paths"></a>

* From the “**Online**” exit port, draw a path to create a corresponding block by choosing “**Agent Handoff**”. You can also include a “Reply” that advises the customer that somebody is about to hop on the chat
* In case the Agent isn’t online, draw a path from the “**Else**” to create a second block by choosing a “**Reply**”, and inserting, for example, an invite for your customer to leave a message

Congratulations! You've successfully set up a live chat with agent handoff and contact info collection using Tiledesk's No Code Visual Builder. Your chatbot will now efficiently handle customer interactions, transferring them to human agents when available, and collecting contact information for follow-up when needed.

<figure><img src="https://1328774413-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVguk6y5OMn3pAaHZSiwU%2Fuploads%2FnPq0nG4gYH1JP8I3UCpT%2Fimages.png?alt=media&amp;token=e9ea4841-95c7-4e66-a699-a9c2470d156f" alt=""><figcaption></figcaption></figure>

Do you have any feedback on this article? Please send it to us at <info@tiledesk.com>

Enjoy Tiledesk!


---

# 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://guide.tiledesk.com/ai-chatbots-and-automation/quick-start/how-to-transfer-my-chatbot-to-a-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.