When should a WhatsApp chatbot hand over to a human?

Start with the customer's explicit choice. If someone asks to speak to a person, provide that path without making them finish a sales questionnaire. Then list the decisions your team reserves for people. These might include a custom commercial quote, a disputed charge, or an exception to a published cancellation policy.

A routine policy question can stay with automation when there is a current, applicable answer. Deciding whether to waive that policy is a different job. Name the team authorised to make that decision.

Worked example: a refund request. A customer says the item arrived damaged and asks for a refund outside the usual return period. The bot can collect the order reference and record the complaint. It should not promise a refund or reject the claim based only on the standard return period. Send the conversation to the team authorised to review it. That team needs the request, the order reference, and the reason an exception is being considered.

Write each rule so a teammate can test it with a sample message. 'Hand over when appropriate' is too vague to check. 'When the customer requests a refund outside the published policy, collect the order reference and send the request to support' identifies a condition, an input, and an owner.

Use this worksheet for each situation. Decide how your chosen software will detect the condition; an AI model's statement that it is confident is not evidence that an answer is correct.

Keep the acknowledgement specific. Explain the unresolved task and where it is going. Only say a teammate has joined when that has actually happened. Sending a request to a queue is an earlier step.

Illustrative order enquiry: Customer: 'The tracking link does not work. Has my order shipped?' Bot: 'I could not confirm the shipment status. I have sent your order reference and this conversation to support for checking.'

Illustrative sales enquiry: Customer: 'Can you give us a custom rate for several locations?' Bot: 'That needs a sales review. Which locations should the team include in the quote?' After routing succeeds: 'I have sent the request to sales. A teammate will reply here.'

If routing fails, the bot must give the actual available support path instead of claiming that a team received the request. Avoid a promised reply time unless your staffed process can support it.

Give the team's actual staffed hours and explain whether the enquiry has been saved for review. An acknowledgement should not imply that a live agent is waiting. Decide who checks overnight enquiries at the next staffed period, including requests that arrived before a holiday.

Example to adapt after the request has been saved: 'Your request is in our support queue. Our team replies during [days and hours, timezone]. You can add any further details here.' Replace the brackets with your actual schedule before using it. Offer an alternative contact method only if someone monitors it.

Keep the original conversation available. Asking the customer to start again by email may be necessary in some cases, but it should be a deliberate support choice with a clear reason.

Pass the customer's request, facts already supplied, the unresolved question, and any action attempted. Distinguish an observed result from an assumption. 'Order lookup timed out' is useful; 'order is probably delayed' is an unsupported conclusion.

The conversation history is the evidence. A summary, if your system supplies one, is a convenience that a person should be able to check against that history. Do not assume every handoff includes an AI-generated summary. Keep internal notes out of the customer-facing reply and share only information the receiving team needs.

WhatsApp permits automated responses during the customer-service window while requiring a clear escalation path. An in-chat transfer is one option; its policy also lists alternatives such as email and a support form. A human reply does not bypass the messaging window. Outside 24 hours of the last customer message, the Business Platform requires an approved message template. Check the current WhatsApp Business Messaging Policy when designing your queue and follow-up process. Consent and opt-out requirements still apply.

Run sample conversations through the full path. Check the destination inbox as well as the customer's view. A message saying 'transferred' does not prove anyone received it. Record the expected outcome and the actual result for each case, then correct failed cases before publishing the workflow.

Choose one recurring exception and give it an owner. Use the WhatsApp human handoff guide to understand conversation context and assignment, then check your inbox setup. If missing business information causes the handoffs, work through the chatbot knowledge-base checklist before expanding what the bot answers.