This guide shows you how to design a WhatsApp chatbot that users actually enjoy talking to. You’ll learn how to keep messages short and readable, make the bot’s purpose obvious, and give people a clear way to leave the conversation whenever they want. You’ll need access to your chatbot’s backend (where you edit conversation flows) and a test WhatsApp number.
What You’ll Need
- Admin access to your chatbot platform (Twilio, Dialogflow, ManyChat, or similar)
- A test WhatsApp number that can receive messages
- A list of the most common questions your users ask
- Pen and paper (or a digital whiteboard) to sketch the flow
Step-by-Step
- Start with a one-line introduction. The very first message should say who you are and what you can do. Example: “Hi! I’m the Acme Store assistant. I can help with orders, returns, or store hours. Type ‘menu’ anytime to see options.” Keep it under 40 words.
- Use numbered menus for navigation. Instead of asking users to type free text, give them a simple list: “1) Track order, 2) Return an item, 3) Talk to a human.” Users just reply with the number. This works better than open questions because it reduces typing errors and confusion.
- Keep every message to one idea. WhatsApp is read on small screens. Break any long explanation into multiple short messages. For example, instead of one 200-character paragraph, send three messages of about 60 characters each. This makes each message easier to scan and reply to.
- Always show the current options. After every user input, repeat the relevant menu or next steps. If they chose “Track order,” immediately show: “1) By order number, 2) By email, 3) Back to main menu.” Users should never wonder what to type next.
- Add a persistent exit command. Program the words “exit,” “stop,” “menu,” and “human” to always work, no matter where the user is in the flow. When they type “exit,” send a final message: “You’ve left the chat. Type ‘hi’ to start again.” Then end the session.
- Offer a human handoff after two failed attempts. If the bot doesn’t understand a reply twice in a row, don’t loop the same error. Say: “I’m having trouble understanding. Would you like to talk to a person? Reply 1 for yes, 2 to try again.” This prevents frustration and churn.
- Confirm before taking any action. If the bot is about to cancel an order, change a setting, or share personal data, ask for confirmation: “You want to cancel order #12345. Reply 1 to confirm, 2 to cancel.” This prevents costly mistakes and builds trust.
- Set a timeout for inactivity. If the user doesn’t reply for 10 minutes, send a gentle nudge: “Still there? Reply ‘menu’ to continue or ‘exit’ to leave.” After another 10 minutes, end the session automatically with a goodbye message.
- Test the exit path on every screen. Go through each branch of your flow and type “exit,” “stop,” and “menu” at every step. Make sure they all work. Also test what happens if the user sends a random word like “pizza” — it should fall back to the main menu, not crash.
- Log and review conversations weekly. Look at where users drop off or type “exit.” If many people leave at a specific step, that step is probably confusing. Rewrite that message and test again.
Common Mistakes
- Writing walls of text. A 300-character message is a wall. Users skim or leave. Split it into 2-3 short bubbles.
- Forgetting the exit option. If users can’t find a way out, they’ll just block the number. Always keep “menu” and “exit” visible in the last message of every turn.
- Using jargon or internal terms. “Your ticket has been escalated to tier 2” means nothing to most users. Say “A specialist will message you within 2 hours.”
- Asking for too much info at once. Don’t ask for name, email, order number, and date of birth in one message. Ask one question at a time.
- Looping the same error message. If the user types something unrecognized, don’t repeat the same “Sorry, I didn’t get that” three times. Offer the human handoff after the second miss.
Tips
- Use quick reply buttons where your platform supports them. WhatsApp’s interactive buttons make choices one tap instead of a typed number, which speeds things up.
- Mirror the user’s language. If they write in short, informal text, respond the same way. If they write formally, match that tone.
- Put the most common action first. If 80% of users want order tracking, make it option 1, not option 4.
- Add a small delay between messages. Sending three messages instantly feels robotic. A 0.5–1 second pause between each makes it feel more natural.
- Always end with a question or a menu. The last line of every bot reply should tell the user what to do next, like “Reply 1 to continue or 2 to exit.”
Troubleshooting
Users still get stuck. If you see high drop-off at a specific step, rewrite that message to be shorter and more concrete. Test it with a friend who hasn’t seen the flow before — if they hesitate, it’s still unclear.
The exit command doesn’t work in some branches. This usually means the exit keyword is only programmed in the main menu, not in sub-flows. Go through every node in your bot builder and add the exit condition to each one.
Users type full sentences instead of numbers. That’s fine. Make sure your bot also understands common phrases like “track my order” or “talk to a person.” Use simple keyword matching, not just numbers.
The bot sends too many messages. If users complain about spam, reduce the number of follow-up nudges. One nudge after 10 minutes is enough; don’t send three reminders.
Handoff to a human fails. Check that your human agent queue is actually connected. If no agent is available, the bot should say “No one is free right now. We’ll message you within 2 hours.” and then store the conversation for later.
Frequently Asked Questions
How short should each bot message be? Aim for under 100 characters per message, and never more than 200. If you need to say more, split it into two or three separate messages.
What’s the best exit word to use? “Exit” and “menu” are the most intuitive. “Stop” also works, but it can be confused with stopping a service. Program all three to be safe.
Should I use buttons or typed numbers? Buttons are better for mobile users because they require one tap. Typed numbers are a good fallback for users on older devices or when buttons aren’t supported.
How many menu options should I show at once? Keep it to 3–5 options. More than that overwhelms users. If you have more options, group them into sub-menus.
What if a user types “help”? “Help” should show the main menu plus a line like “Type ‘exit’ to leave the chat.” This is a common fallback and should always be programmed.
Can users exit mid-conversation and come back later? Yes, if your platform saves the conversation state. When they return, greet them with “Welcome back. You were checking your order. Reply 1 to continue or 2 to start over.”
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix msmpeg2vdec.dll Errors in Windows
- How to Update Sonos App and Speakers
- Unlock iPad Without Apple ID: Is It Possible?
- iOS 18 WhatsApp Notifications Not Working? Fix
- Fix Windows Cannot Locate Suitable Printer Driver
- How to Group Text and Pictures in Word