When an AI should hand a WhatsApp conversation to a human: the triggers, the handover that works, and what not to hand over
Hand over on a rule — a topic, a value, a missing capability, sentiment, a flood — before the reply, not after a wrong one. What the person needs to see, why the agent stays silent until handed back, and the ten percent that should be a person's.
Selling with an AI6 of 10 in this topic
An AI should hand a WhatsApp chat to a person when your rules say so (a topic, an order size, a discount request, an upset customer) and always when the customer asks for one. The handover should happen before the AI replies, the AI should stay quiet until someone hands the chat back, and the person taking over should see everything the customer has already said, so nobody has to repeat themselves.
On this page

When handover usually goes wrong
Most chatbots hand over when the customer types "agent" or the flow runs out. By then the bot has usually said the wrong thing twice. A good handover is decided before the reply: the AI reads the message, sees it's one for a person, and a person answers instead. The customer never sees the AI try.
When a person should answer
| Trigger | Example | Why a person |
|---|---|---|
| A topic | Hazardous goods; a symptom; a legal threat; a complaint about a delivery | A wrong answer costs more than a lost sale |
| An order size or value | A 50,000 sq ft requirement; an order above ₹5 lakh | Negotiating is where your margin lives |
| A discount request | "Can you do better on the price?" | The AI shouldn't be the one who gives margin away |
| Something the AI can't do | "Can you build a custom itinerary?" | Better a handover than an improvised promise |
| An upset customer | Anger, or "I already told you this" | A person calms things down; a bot repeats itself |
| The customer asks | "Can I talk to someone?" | Always, at once, in any language |
What a good handover looks like
- Before the reply. The AI doesn't answer the message that needs a person.
- With context. The chat lands with your team showing why it was handed over and every detail already collected, so nobody asks the customer to repeat themselves.
- Quiet until handed back. The AI doesn't jump back in because the customer wrote again. Someone on your team hands it back when they're done.
- Honest with the customer. "Priya from our team will take this from here", with a time if it'll be a while. Not silence, and not a bot pretending to be Priya.
- On record. Who took over, when and why, so you can see which rules fire and which you're missing.
In Linkubit
You choose the topics, answers and kinds of customer that go to a person, and anyone who asks for a person gets one. The AI stops before replying, the chat is assigned to the right owner and they're told at once, with the reason and everything captured so far. The AI stays out of that chat until someone on your team hands it back.
What not to hand over
The first answer, the qualifying questions, the catalogue quote, the visit confirmation, the reminders, the document list and the payment request. These are the forty-times-a-day tasks a person does slower and later. A team that hands everything over has a chatbot with extra steps; the point is to keep your people for the one chat in ten that needs judgement.
What if nobody is available to take the chat?
The chat waits with your team and the customer is told a person will reply, and roughly when. The AI doesn't fill the gap with guesses.
Can a customer ask for a human in Hindi?
Yes. A request for a person works in whatever language the customer writes in.
How many handover rules should I set?
Start with three or four: complaints, discount requests, large orders and anything medical or legal for your trade. Add more when a real chat shows a gap.
Read next
More on Selling with an AILinkubit vs other toolsWhatsApp templatesCost calculatorPricing
Try it on your own number. Start free, no card, or see the pricing.