Human Handoff: When Your Chatbot Should Pass the Chat to a Person

Every chatbot reaches a point where it shouldn't continue. The customer is angry, the question is unusual, or there's money or health or a decision involved. What happens at that point decides whether customers trust your automation or avoid it.

A good handoff feels like being passed to a colleague who already knows the story. A bad one feels like being dropped. Here's how to get it right.

Why handoff matters more than the bot

Most people don't mind talking to a bot for simple things. What they mind is being stuck. The fastest way to make customers hate your chatbot is to trap them in a loop of "Sorry, I didn't understand" with no way out.

Handoff also protects you. A bot that tries to handle a refund dispute or a medical question on its own can make promises you can't keep or say something it shouldn't. Clear handoff rules keep the bot inside its lane.

When the bot should hand off

Think of handoff triggers in four groups.

1. The customer asks

If someone types "human", "agent", "real person", "call me" or the equivalent in their language, hand over. No arguing, no "Are you sure? I can help with lots of things!" Just do it.

Remember people say this in many ways. "Manche sanga kura garna paryo", "staff lai dinus", a phone number with "call garnus", Hindi, Arabic, all of it. An AI chatbot can recognise intent across languages; a keyword list usually can't.

2. The topic needs a person

Decide in advance which topics always go to your team:

• Complaints, damaged or wrong orders, refunds
• Payment disputes or failed payments
• Medical, legal or financial advice
• Bulk, wholesale, corporate or custom orders
• Negotiating price or making exceptions
• Anything involving personal or sensitive information beyond basic contact details

For complaints in particular, see handling complaints in DMs.

3. The bot isn't confident

If the answer isn't in the bot's knowledge, it should say so and hand over, not guess. A wrong answer about price or delivery creates a bigger problem than a short wait for a person. Unanswered questions are also your best signal for what to add to the knowledge base.

4. The conversation is going badly

Signals that a person should step in:

• The customer repeats the same question
• Frustration in the language ("this is useless", lots of capitals)
• The chat has gone back and forth many times without progress
• A high-value buyer is close to deciding and has a specific concern

How to hand off well

The moment of transfer is where most setups fall down. A smooth handoff has four parts.

1. Tell the customer what's happening. "I'm passing this to our team. They'll see everything you've written, so you won't need to repeat it."
2. Set a realistic time. "Someone will reply within about 15 minutes" or "Our team is back at 10 am." Only promise what you can deliver.
3. Pass the full context. The staff member should see the whole conversation, which channel it came from, and anything the bot already collected (name, phone, order number, product).
4. Let the bot step back. Once a person takes over, the bot should stay quiet in that conversation until it's handed back. Two voices answering at once is confusing.

I've passed this to our team with your order details. Someone will reply here shortly, usually within 15 minutes during shop hours.

What to do outside working hours

Most businesses don't have staff online at 11 pm. That's fine, as long as the bot is honest.

• Say when the team will reply, specifically.
• Collect what the team needs to act quickly in the morning: name, phone, order number, a description of the problem, maybe a photo.
• For complaints, acknowledge the problem and apologise without promising a specific resolution.
• Make sure after-hours handoffs are at the top of the queue the next morning, not buried under new chats.

On Meta platforms, keep timing in mind. In general, businesses can reply freely for a limited period after a customer's last message, with more restrictions after that. Check Meta's current policy, and don't leave after-hours handoffs until the afternoon.

Making sure people actually pick up

A handoff is a promise. The bot did its part. Now someone has to answer.

• Decide who receives handoffs, by topic or by shift.
• Make handoffs visible. They should stand out in your inbox, not look like every other chat. This is much easier when everything lands in one place; see what a unified inbox is.
• Watch handoff wait times. If customers wait hours after the bot said "shortly", the problem isn't the bot.
• Hand back when done. If the person solves the issue and the customer has a routine follow-up, the bot can pick up again.

Mistakes to avoid

• No way to reach a person at all.
• Asking the customer to restate their problem after the handoff.
• Promising a reply time nobody can meet.
• The bot and a person replying at the same time.
• Handing off everything "to be safe", which overloads your team and defeats the point.
• Never reviewing handoffs. Read them weekly. Each routine question in there is a gap you can fill.

A scenario

Say a customer messages a clothing store in Dubai at 10 pm in a mix of English and Arabic: the dress they received is the wrong size, and they need it for a wedding on Saturday.

The bot recognises a wrong-order complaint with a deadline. It apologises, collects the order number and the size they need, says the team opens at 10 am and will reply first thing, and flags the chat as urgent. At 10 am, the staff member sees the full story at the top of the queue and arranges an exchange. The customer explained once, got an honest timeline, and got a fix.

How Orbit handles it

In Orbit, handoff rules are part of the setup our team does with you: which topics go to people, how confidence is handled, what happens after hours. Conversations move to your team in the same unified inbox with the full history attached. If you want to see what a good handoff looks like on your own channels, book a demo.