Chatbot to Human Handoff: When and How to Transfer a Chat

Chatbot human handoff is the moment an AI assistant stops answering and passes the conversation to a person. Get it right and customers barely notice the seam: the bot handles the routine questions, and anything tricky reaches someone who can actually decide. Get it wrong and you get the two classic failures — a bot that loops "I'm sorry, I didn't understand" forever, or a bot that gives up so fast it saves nobody any time. This guide covers when to hand off, how to write the rules, and what to do when nobody is around to take the chat.

Why handoff design makes or breaks an AI chatbot

Modern LLM-based assistants are good at answering questions from a set of facts. They are not good at knowing what they don't know unless you tell them. Without explicit handoff rules, a bot will try to be helpful by guessing — inventing a refund policy, promising a delivery date, or debugging an account problem it can't see.

Handoff is also where customer trust is decided. People are generally fine talking to a bot for simple questions as long as they know a human is reachable. The fastest way to annoy a customer is to make them fight the bot to get to a person.

So think of handoff as a feature you design, not an error path.

Handoff triggers: the six situations that should reach a human

Most support teams end up with some version of these six triggers:

1. The customer asks for a person. "Talk to a human", "operator", "real person". Honor this immediately. Don't make the bot try one more answer first.
2. The bot can't answer from its facts. If the question isn't covered by the instruction or knowledge you gave it, the right move is to hand off, not to improvise.
3. Repeated failure. The customer rephrases the same question two or three times, or says "that's not what I asked". The bot is stuck; a human should step in.
4. Frustration or strong emotion. Complaints, anger, threats to cancel, or messages in all caps. Even if the bot technically could answer, an upset customer usually needs a person.
5. Sensitive topics. Refunds, billing disputes, legal questions, account security, personal data requests, anything health- or safety-related. These carry risk if answered wrong.
6. High-value moments. A large order, a wholesale or partnership inquiry, a demo request, a customer comparing you against another vendor. A salesperson is worth more here than a fast canned answer.

You don't need all six on day one. Start with the first three, then add the rest based on what you see in transcripts.

Writing handoff rules into the bot's instruction

The bot's instruction (its system prompt) is where these triggers live. Be concrete. Vague rules like "escalate when appropriate" leave the decision to the model's mood.

A workable block of handoff rules might look like this:

Transfer the conversation to an operator when:
- the customer asks for a person, an operator or a manager;
- the answer is not in the facts above — do not guess;
- the customer repeats a question or says your answer didn't help;
- the customer is upset or complains;
- the topic is a refund, a billing dispute, account access or a legal question;
- the customer asks about an order over 50 units or a partnership.
Before transferring, tell the customer briefly that a colleague will take over.

A few tips:

• Tell the bot what to say at handoff. One short line — "I'll pass this to a colleague who can check your order" — beats silence or a long apology.
• Ask for missing details first, when it helps. For an order problem, having the bot collect the order number before handing off saves the operator a round trip.
• Use per-topic rules for risky areas. In ChatDeck you can add rules for specific topics, such as refunds or pricing, on top of the main instruction, and each rule can use its own model. A refund rule can simply say: collect the order number, then transfer.

In ChatDeck, handoff is one of the assistant's tools ("transfer to operator"), which you switch on in the assistant settings. The What the assistant can do tutorial shows where. When the bot calls it, the chat moves from the bot's tab into the operators' queue. For more on structuring the whole instruction, see how to write a customer service chatbot prompt.

What the operator should see at handoff

The worst handoff makes the customer repeat everything. The operator should be able to pick up mid-sentence:

• The full transcript, including the bot's answers, so the operator knows what was already said.
• Visitor context: the page the customer is on right now, the referrer, device and browser, approximate location and local time.
• Who the customer is, if your site identifies logged-in users — name, email, plan or any attributes you pass.

The operator's first message should acknowledge the context: "Hi, I'm Sam. I see you're asking about the return for order 1042 — let me check." That one line tells the customer the handoff worked.

Handoff when no operator is online

Handoffs don't only happen during office hours. Decide in advance what happens at 2 a.m.:

• Say so honestly. Tell the customer that operators are offline and when they'll be back. ChatDeck does this automatically outside the working hours you set: the bot tells the visitor when the team returns.
• Collect what you need to follow up. An email address and a short summary of the problem.
• Make sure the chat is waiting in the queue in the morning, not lost.
• For urgent cases, notify someone. If you run an on-call rotation, mobile or desktop notifications let the person on call see the handoff.

More options are in our guide to after-hours customer support.

Measuring handoff: rate, wait time after handoff, CSAT

Three numbers tell you whether handoff is working:

• Handoff rate — the share of bot conversations that reach a person. Very high means the bot lacks facts or the rules are too cautious. Very low can mean the bot is answering things it shouldn't. There's no universal target; watch the trend and read the transcripts.
• Wait time after handoff — how long the customer waits for a human once the bot passes the chat. This is often the weakest link: a fast bot followed by a long silence feels worse than no bot. ChatDeck's analytics track this separately from first response time.
• CSAT after handoff vs bot-only chats — if handed-off chats score much lower, the transition itself may be the problem.

The live chat metrics guide explains how to read these alongside your other KPIs.

Common handoff mistakes

• Hiding the human. Making customers type "operator" five times. If they ask, transfer.
• No message at handoff. The bot stops answering and the customer doesn't know whether anyone is coming.
• Handing off with nobody available, and not saying so.
• Rules that are too broad. "Transfer anything about orders" sends half your volume to humans, including the "how long does shipping take" questions the bot could answer.
• Never reviewing transcripts. Handoff rules should be tuned every few weeks from real conversations.

Frequently asked questions

When should a chatbot transfer to a human agent?

When the customer asks for a person, when the answer isn't in the bot's facts, when the customer repeats themselves or is frustrated, and for sensitive or high-value topics like refunds, billing disputes or large orders. Write these triggers explicitly into the bot's instruction.

How do I stop the bot from handing off too often?

Read the handed-off transcripts and look for patterns. Usually the bot is missing facts — add them to the instruction. Then narrow broad rules: instead of "transfer anything about orders", say "transfer order problems; answer shipping-time questions yourself".

What should the customer see while waiting for a human?

A short message that a colleague is taking over, and an honest expectation of when. If operators are offline, the customer should be told when they'll be back and asked for a way to follow up.

What happens to a handoff outside business hours?

That depends on your setup. A good default: the bot tells the customer when the team is back, collects an email and a summary, and the chat waits in the queue. With ChatDeck, the bot does this automatically based on your working hours.

ChatDeck's AI assistant has handoff built in, and the inbox shows operators the full transcript and visitor context. Create a free workspace and read how to set up an AI chatbot for your website to get started.