How to build a WhatsApp support bot that hands over well

Start from data, not a flowchart

Export a month of conversations and tag them. You will usually find a handful of questions — order status, returns, pricing, timings — make up most of the volume. Automate those first.

Grounded answers beat clever answers

An AI agent should answer from your content: website, help centre, policies. If a question is not covered, the right answer is “let me get someone who can help”, not a guess. Fix gaps by improving the content, then re-sync.

Deterministic where it matters

Use a flow for anything with steps or rules (collect an order number, check eligibility, book a slot) and let the AI handle open questions. In ChatRhino a flow can delegate a step to an AI agent and fall back to a fixed path if the agent cannot complete it.

The handoff is the product

• Tell the customer what happens next and when.
• Route to a team that is on shift, not to someone on leave.
• Give the agent a summary and the details already collected.
• Do not make the customer repeat themselves.

Respect the WhatsApp window

Replies inside the 24-hour window are free-form and free; after it, you need a template. Design follow-ups accordingly — see the 24-hour window.

Measure

• Share of conversations resolved without a person.
• Handoff reasons, and which ones you could fix with content.
• Customer replies after a bot answer (a “that didn't help” signal).
• Time to first human response after handoff.

Step by step

1. Find the top questions. Export a month of conversations and group them. The top 20 usually cover most volume.
2. Write or collect the answers. Make sure your website and help pages answer them clearly; that is what the AI will learn from.
3. Add lookups. Connect order, booking or CRM systems so the bot can answer “where is my…?” with real data.
4. Design the handoff. Hand over on low confidence, on request and on sensitive topics, with a summary for the agent.
5. Test on real conversations. Turn past conversations into test cases with the answer you expect, and run them before publishing.
6. Launch gradually and review. Start after hours or on one channel, then review handoffs and unanswered questions every week.