Quick answer
To hand a chat from a chatbot to a human well, define the triggers (the customer asks for a person, the bot is unsure, the topic is sensitive or the customer is upset), keep a "talk to a person" option visible, tell the customer what happens next and when, route the chat to the right agent with the full history, and pause the bot so it does not interrupt.
Key takeaways
- Hand over when the customer asks, when the bot is unsure, when the topic is sensitive and when the customer is clearly frustrated.
- Keep a "talk to a person" option visible at every step and recognise the words customers use, in English and Kiswahili.
- Tell the customer what happens next and roughly when, especially outside working hours.
- Route the chat to the right person with the full history, and pause automation on that chat.
- Measure how long handed-over customers wait for a person and fix the gaps.
The moment a chatbot passes a customer to a person is where most bots succeed or fail. Done well, the customer barely notices the switch: someone picks up, already knows what was said and solves the problem. Done badly, the customer repeats themselves, waits without knowing why, or gets trapped in a menu that will not let them out.
This guide is for businesses using a WhatsApp or website chatbot, rule-based or AI, that want a hand-over customers do not resent. It covers when to hand over, what to say, how to route and what the agent should do first.
Before you start
You will need:
- A chatbot or automation running on WhatsApp or website chat.
- A shared team inbox where handed-over chats arrive, rather than one staff member's phone.
- Your working hours and who covers which topics (sales, support, accounts, a specific branch).
- A list of sensitive topics that must always go to a person.
On chat.or.ke, automation flows, the AI assistant and the shared WhatsApp inbox sit in one place, so a hand-over moves the chat to a person without switching tools.
Step 1: Decide when the bot should hand over
Write down the triggers before you build anything. Most businesses need five:
| Trigger | Example | Why it matters |
|---|---|---|
| Customer asks for a person | "agent", "nataka kuongea na mtu", "call me" | Ignoring this request is the fastest way to lose trust |
| Bot is unsure | Question not covered by the knowledge base or menu | A guess can be worse than no answer |
| Sensitive topic | Payment disputes, medical questions, legal matters | Errors here cost money or cause harm |
| Frustration | Repeated messages, capital letters, "this is useless" | Another menu makes it worse |
| High-value moment | Large order, wedding booking, bulk quote | A person closes better than a bot |
The chat.or.ke AI assistant hands the chat to your team when the customer asks for a person or when it is not sure of the answer. For rule-based flows, you add the hand-over as an explicit step or option.
Step 2: Make "talk to a person" easy to find
Put a way out on every menu. With WhatsApp reply buttons you can show up to three options, so reserve one for "Talk to us" on the main menu; in a list message, make it the last row.
Also catch typed requests. Add keywords such as agent, person, human, help, customer care, mtu and msaada, and route them straight to the hand-over. Customers often ignore buttons and type, especially when annoyed.
Step 3: Write a hand-over message that sets expectations
When the bot hands over, say three things: a person is coming, roughly when, and what the customer can do meanwhile.
During working hours:
Thanks, Achieng. I am passing you to our team now. Someone will reply within about 10 minutes. 🙏
Outside working hours:
Thanks, Achieng. Our team is offline now and back at 8am. Your message is saved and they will reply first thing. If it is urgent, call 07XX XXX XXX.
Only promise times you can keep. "Within 10 minutes" that becomes two hours does more damage than "this morning". Use your real number instead of the placeholder above.
Step 4: Route the chat to the right person
A hand-over that lands in a general queue nobody watches is not a hand-over. Send each chat to whoever can resolve it:
- By topic: if the customer chose "Payments" in the menu, assign accounts; if "Orders", assign the orders team.
- By brand or branch: a group running several shops or clinic branches can file chats under the right brand so only that team sees them. chat.or.ke's multi-brand setup lets a welcome menu ask which brand the customer wants.
- By job: if the issue needs follow-up work, such as a refund or a repair, open a ticket from the chat in the helpdesk so it is tracked against your response and resolution targets.
Step 5: Pause the bot on that chat
Once a person takes over, stop the automation for that conversation. Otherwise a keyword in the customer's next message can trigger an auto reply in the middle of the agent's conversation, which looks careless.
In chat.or.ke, agents can pause automation, or the AI, on a single conversation with one click and reply personally. When the issue is resolved, automation can be switched back on for that chat.
Step 6: Give the agent the full context
The agent should never need to ask "How can I help you?" after a hand-over. Before replying, they should see:
- The whole conversation, including everything the bot or AI said.
- Answers the flow captured, such as name, order details, preferred date or budget.
- The contact's history: previous chats, notes, tags and open tickets.
In a CRM that saves every conversation to a contact profile, this is automatic. The agent's first message can then be specific:
Hi Achieng, Brian here. I can see your 2 kg birthday cake request for Saturday. It comes to KES 4,800 including the message on top. Shall I send the Till number?
The amount is the bakery's own price in this example, not a platform fee.
Step 7: Watch the WhatsApp 24-hour window
On WhatsApp you can reply freely only within 24 hours of the customer's last message. If a hand-over happens on Friday evening and nobody replies until Monday, you will need an approved template message to restart the conversation.
Plan staffing so handed-over chats get a person well within the window. chat.or.ke tracks the window for every chat and tells you when a template is required. For Facebook Messenger and Instagram, Meta allows a person on your team to reply for up to 7 days. More detail is in the WhatsApp 24-hour window explained.
Step 8: Measure and improve the hand-over
Review hand-overs every week. Look at:
- Wait time after hand-over: how long customers wait for the first human reply. See how to reduce first response time.
- Hand-over reasons: if the same question keeps going to people, add it to the bot or the AI's knowledge base.
- False hand-overs: chats passed on that the bot could have answered.
- Missed hand-overs: conversations where the customer asked for a person and did not get one quickly. Fix these first.
Published 20 October 2026 Updated 20 October 2026 Plain-text version
