Chatbot-to-Human Handoff: A Simple Telegram Guide

Chatbot-to-human handoff means a person takes over when a bot cannot give the right answer. The customer should stay in the same conversation and know exactly how to ask for help.

With a SUCH AI support bot, a customer can send /human at any time. SUCH moves the chat from Closed to Open and notifies the team. Agents can reply in the same Telegram conversation or in the SUCH web app. When the team closes the chat after helping, AI replies can work again.

An AI bot gives the best handoff when it has a small, clear job. In app.such.chat, open your bot's Project Settings, turn on Bot AI, and choose Support bot. Add short Bot AI Instructions that say what the bot can answer and how it should speak.

Then add the correct facts in Bot Knowledge. Keep each fact in its own short block. For example, add one block for prices, one for account access, and one for common steps. A focused bot gives clearer answers and makes it easier for the team to take over when a person is needed. See how to build an AI chatbot without code for the full AI setup.

Put one direct sentence in the welcome message: Need a person? Send /human and our team will reply here. This tells customers that they do not need to start another chat or look for a separate contact address.

Use the same sentence in a useful command reply, such as /support or /help. In Bot AI Instructions, tell the AI to suggest /human when a question needs the team. Keeping the option visible makes the next step simple.

Create a private Telegram group and add your support bot. Then send /team to @SUCH, connect the group, and add the right group members as agents in Manage Permissions. Agents can reply when a user messages the bot.

Team members can answer in Telegram or in app.such.chat. This keeps the customer in one conversation while the team chooses the reply method that is fastest for them. For the full no-code setup, use this Telegram support bot guide.

The chat state controls who is answering. AI replies happen in Closed chats. When a customer sends /human, the chat becomes Open, so the team can reply. A team member can also open a chat when they need to take over.

Use Snoozed when the team needs to reply later. A new message from that user moves the chat back to Open. Use Closed when the issue is finished. This makes the support routine clear: answer Open chats, Snooze the ones waiting for a later reply, and Close completed conversations.

Let a person handle questions that need a real decision, a careful explanation, or information the bot does not have. It can be as simple as a customer asking for a person, a request that needs a special answer, or a message where the team should decide what happens next.

The important part is not making the bot answer every question. It is giving a useful first answer, then making it easy to continue with the team. This is one reason chatbots can improve customer service when they are used alongside people.

Test the experience on your own phone before sharing the bot.

1. Start the bot and read the welcome message.
2. Send a normal question that AI can answer.
3. Send /human and check that the chat becomes Open.
4. Reply as an agent in Telegram or in the web app.
5. Snooze the chat, then send a new user message and check that it becomes Open.
6. Close the chat, then send a new question and check that AI replies again.

This small test proves that the customer, the bot, and the team all have a clear next step.

No. The customer sends /human to the same SUCH bot. The team replies in that conversation.

Yes. A team member can open a chat when the team needs to reply.

No. Sending /human moves the chat to Open for the team. Closing the chat enables AI replies again.

No. Create the bot in BotFather, connect it to SUCH, set up Bot AI, and connect the team group with /team.