Human handoff
WhatsApp AI Human Handoff: When a Person Should Take Over
An AI customer-service workflow needs a reliable way to stop and bring in a person. On WhatsApp, a good handoff makes the next step clear to the customer and gives the teammate enough context to continue the same conversation.
Define handoff triggers before writing replies
Do not make the assistant decide from a vague instruction such as “escalate when needed.” Write specific conditions the team can review. A direct request for a person is the clearest trigger. Other triggers can include repeated misunderstanding, missing or conflicting business information, a complaint, a negotiation, or a decision outside the assistant’s authority.
Map triggers to the business. A restaurant may hand off allergy questions or a changed order. A service business may route a custom scope or scheduling exception to a specialist. The point is to define a boundary that protects the customer and gives the team confidence about when to step in.
- The customer asks to speak with someone.
- The request is unusual, sensitive, or not covered by approved information.
- The assistant has tried to clarify but the customer still cannot get a useful answer.
- The answer requires a price exception, approval, negotiation, or personal judgment.
Tell the customer what will happen next
A handoff message should be brief and specific. Acknowledge the request, say that a teammate will continue in this conversation, and set a realistic expectation for when the customer should hear back if the business knows it. Do not promise an instant reply if the team may be away.
The customer should not need to message a different number or repeat the conversation. If a delay is expected, say so plainly and provide the next available step. Clear expectations matter more than a polished transfer phrase.
Pass the context the teammate needs
The teammate needs the original question, the reason for the handoff, and the useful details the customer has already provided. A short summary can help, but the original conversation should remain available so a person can verify what was said.
Keep the transfer focused. Include relevant product or service choices, quantity, timing, and any agreed next step. Avoid collecting personal information that is not needed to answer the request. The business should decide who owns the response and how the customer will know that ownership has changed.
Make ownership visible and return control deliberately
Once a person takes over, the AI should stop sending customer-facing replies in that conversation until the team deliberately returns it to automation. This avoids two voices giving different answers. The handoff is not complete if the AI keeps responding after the customer has been told a person is taking over.
When the teammate is finished, decide whether the conversation should stay with the team or return to AI for a clearly defined routine task. Record the next step so the customer is not left wondering who is responsible.