Automate the predictable, not the personal
The highest-performing WhatsApp bots handle a narrow set of genuinely repetitive questions — order status, business hours, pricing tiers, basic troubleshooting — and hand off everything else to a human immediately. The failure mode is trying to make the bot sound human and cover every possible question, which produces a maze of menus that frustrates customers who just want to talk to someone.
Design the handoff before you design the bot
The single most important design decision is how and when the bot gives up and routes to a person. Get this wrong and you get the classic complaint: "I typed 'agent' five times and it kept showing me a menu."
- Offer a one-word escape ("agent," "help," "human") that works from any point in the flow
- Route to a human automatically after two failed attempts to understand the customer
- Preserve full conversation context so the human does not ask the customer to repeat themselves
- Set a clear expectation ("A team member will reply within 10 minutes") the moment it hands off
Use buttons and lists instead of free-text menus where possible
The API supports interactive reply buttons and list messages — tappable options rather than "reply 1 for sales, 2 for support." These convert noticeably better because customers do not have to guess the exact phrase the bot expects, and they reduce the ambiguous free-text responses that trip up simple bots.
Respect the 24-hour window in your bot logic
A bot that tries to re-engage a customer outside the open conversation window with free text will simply fail to deliver, because that requires an approved template. Build bot flows that are aware of conversation state: inside the window, reply freely; outside it, trigger a template-based re-engagement instead of a silent failure.
Measure the bot like a team member
Track containment rate (conversations the bot resolves without a human), handoff rate, and — critically — complaint and block rate for bot-only conversations versus human-assisted ones. A bot that resolves 40% of volume but doubles the block rate on those chats is not actually saving the business anything once quality-rating damage is accounted for.
Where this lives in Messages Pilot
Messages Pilot's automation builder is designed around this handoff-first philosophy: every flow has an explicit escalation path to the shared inbox, and conversations the bot touches stay fully visible to agents, with the full exchange already in context when a human picks it up.
Run the WhatsApp Business API without the busywork
Messages Pilot gives your team a shared inbox, templates, and automation on top of the official API — so you can focus on customers, not infrastructure.
Start Free Trial