Chatbot human handover is the point where an AI agent stops replying and a member of your team takes over the conversation. It should happen for complaints, refunds, medical or legal questions, valued clients and any question the AI cannot answer with confidence. This article lists clear triggers, what the customer should see and how to alert the right person. It is part of our guide to AI WhatsApp agents for UAE businesses.
Why handover design matters
Most customers do not mind talking to an AI assistant. What frustrates them is being stuck: asking the same question three times, or waiting in silence after being told “a colleague will help you”.
A good handover protects three things:
- The customer’s time, because they reach someone who can act.
- Your reputation, because sensitive issues are handled by a person, not improvised by software.
- Your team’s time, because staff join only the conversations that need them, with the full context in front of them.
Handover is not a sign that the AI failed. It is part of the design.
Triggers to hand over
Write your triggers down before the agent goes live. Common ones for UAE businesses:
| Trigger | Example message | Who should take it |
|---|---|---|
| Complaint or strong frustration | “This is the second time my order is late” | Manager or customer care |
| Refund, credit or exception | “Can I return this after 30 days?” | Manager |
| Medical question | “Is this treatment safe for me during pregnancy?” | Clinician or clinic coordinator |
| Legal or contractual detail | “What does clause 4 of my lease mean?” | Qualified staff member |
| Valued or corporate client | A known account, or “I need 200 boxes for our office” | Account owner or sales lead |
| Customer asks for a person | “Can I speak to someone?” | Next available staff member |
| AI not confident | A question outside its knowledge | Relevant team |
For clinics, the rule is simple: the AI collects details and passes clinical questions to clinicians. If a message suggests an emergency, the reply should tell the person to call 999 or 998 straight away, then alert staff.
What the customer should see
The customer should know a person is joining, roughly when, and that they do not need to repeat themselves. A short, honest line is enough.
Thank you for explaining. I am passing this to our team now, and a colleague will reply in this chat shortly. You do not need to send your details again.
Out of hours, be clear about timing rather than vague:
Our team is offline now and will reply here from 9am tomorrow. I have noted your request so they can pick it up first thing.
Avoid promising a time your team cannot meet. “Shortly” during working hours and a named time out of hours are safer than “within 5 minutes”.
Alerting the right staff member
A handover that nobody notices is worse than no handover. Decide in advance:
- Who receives which type. Route by topic: sales questions to sales, complaints to the manager, clinical questions to the clinic coordinator. Our help article on routing leads to your sales team shows how routing by category works.
- How they are alerted. A WhatsApp alert to the right person is quicker to see than an email.
- What the alert says. The customer’s name, the reason for handover and a link to the chat.
- What happens if nobody responds. A second person or the manager receives a reminder after an agreed time.
Example staff alert:
Handover: complaint about a late delivery, order from yesterday. Customer is waiting in the chat.
A daily summary of handovers also helps managers see the pattern. See alerts and daily summaries in the Help Centre.
Reviewing handed-over chats
Handed-over chats are the richest source of improvement, because they show where the AI reached its limit. Once a week:
- Count handovers by reason. A rising number of “AI not confident” handovers usually means missing knowledge.
- Check pick-up times. Long gaps point to an alert or staffing problem, not an AI problem.
- Read a few in full. Was the handover too early, too late or just right?
- Turn repeated questions into knowledge, so the AI can answer them next time, unless they belong with staff.
- Keep sensitive triggers in place even if they are rare. Complaints and medical questions should always reach a person.
How Dub Ai helps
Dub Ai’s WhatsApp assistant hands chats to your team when they match the triggers you set, such as complaints, refunds or questions outside its knowledge, and tells the customer a person is joining. Your staff take over in the shared inbox with the full conversation in view, and leads can be routed to the right person by category. Notifications and alerts tell staff about new messages, orders and leads, with a daily digest so nothing important waits too long. The Dub Ai team helps you set triggers and review handovers in the first weeks.
Frequently asked questions
Can the customer ask for a person?
Yes, and they should always be able to. Treat “can I speak to someone”, or the same request in Arabic, as a handover trigger. The assistant should confirm that a team member will reply, say roughly when and alert staff. Making people fight to reach a human damages trust far more than any time saved by keeping them with the AI.
What if no staff are online?
Tell the customer honestly when the team will be back and what will happen next, for example “our team will reply from 9am tomorrow”. The assistant can still collect useful details so staff start with the full picture. For anything urgent or medical, include clear emergency guidance, such as calling 999 or 998, rather than asking the person to wait.