How should an AI hand a customer chat over to a human?
When an AI assistant should pass a WhatsApp or Instagram chat to your team, what context to send with it, and how to avoid customers repeating themselves.
Anadoris Digital · · 4 min read

Handover is where most customer chatbots succeed or fail. A bot that answers routine questions well but traps an upset customer in a loop does more harm than having no bot at all. A good handover feels like being passed to a colleague who already knows the story.
For a small D2C brand with a lean team, the goal is simple: let automation handle what it can answer correctly, and get everything else to the right person quickly with enough context to resolve it in one reply.
The triggers that should always hand over
- Topic triggers: refunds, payment problems, damaged items, allergic reactions, legal threats, bulk or wholesale enquiries.
- Behaviour triggers: the customer asks for a person, repeats the same question, uses angry language or sends several messages without a resolution.
- Confidence triggers: the AI cannot find the answer in its approved sources, or the order lookup fails.
- Value triggers: high-value orders, repeat customers you have flagged, or influencer and press contacts.
Write these rules down in plain language before configuring anything. They are business decisions, not technical ones, and the founder or support lead should own them.
Be careful with keyword triggers on their own. Customers often use words like refund or cancel casually (“I don’t want to cancel, just checking the date”), and a bot that hands over on every mention will flood your team. Combining the keyword with the AI’s reading of intent, and with whether the order is already dispatched, gives far fewer false alarms. Equally, a calm message can hide a serious issue, such as a skin reaction described politely, so safety topics should hand over regardless of tone.
What the human should receive
The single biggest frustration in handover is making the customer repeat themselves. The AI has already read the conversation, so it should prepare a short brief for your team.
A good brief takes a few seconds to read and lets the team member reply with the answer, not with questions.
- A one-line summary of what the customer wants.
- The order number, status and items if an order is involved.
- The reason for handover (topic, mood or low confidence).
- The customer’s own words for the key complaint, not a paraphrase.
- Anything the bot already told the customer, so your team does not contradict it.
What the customer should hear
The message at the moment of handover sets expectations. It should say plainly that a team member will reply, give an honest idea of when (for example, during working hours), and avoid promising an outcome such as a refund. If your team is offline, say so and confirm the conversation is saved. Silence after a handover message is the worst result; customers read it as being ignored.
Channel matters too. On Instagram, many conversations start as replies to stories or comments, and some customers expect a quick public acknowledgement. Never move a complaint into public view; acknowledge briefly and continue in direct messages. On WhatsApp, keep the handover inside the same chat rather than asking the customer to call or email, which feels like being sent away.
Designing the queue on your side
Handover only works if someone is watching. In a small team that often means one shared inbox with clear ownership by shift. Decide who picks up handed-over chats, how they are marked as taken, and what happens if nobody responds within your working-hours target. A simple reminder to the founder or a backup person is usually enough.
Once a person takes over, the bot should stay quiet in that chat until the person closes it. Bots that jump back in mid-conversation cause confusion and contradictory answers.
When the person closes the chat, record the outcome in a few words: resolved, refund approved, replacement sent, no action needed. These notes make your weekly review far quicker, and over time they show which handover reasons lead to real work and which could be answered by the bot with a better knowledge base. They also give the founder a quick view of what customers are struggling with each week.
A handover checklist
- Written list of topics that always go to a person.
- A visible “talk to a person” option in every automated flow.
- A short handover brief attached to every handed-over chat.
- One named owner per shift for the handover queue.
- Bot paused in any chat a person has taken.
- An out-of-hours message that is honest about reply times.
- A weekly review of handed-over chats to find questions the bot could safely learn to answer, and ones it should stop attempting.
Where to start
Pull a week of past WhatsApp and Instagram conversations and mark every one that needed a person. Group them by reason. Those groups become your handover rules. Then decide who owns the queue before switching any automation on. Anadoris Digital can help design handover rules and connect them to the inbox your team already uses.
Related service: AI & Automation · More on this topic: AI & Automation articles
