WhatsApp chatbot guide: how to build one without coding, with 5 example flows

A WhatsApp chatbot is an automated conversation that starts when something triggers it, such as a keyword, a first message or an ad click, and then follows steps you design: messages, buttons, questions and a handover to a person. You can build one without coding, using a drag-and-drop builder from an API provider.

This post is about the rule-based kind, which follows the exact paths you draw and never improvises. That makes it predictable, and it's a sensible first bot. Below you'll find the basic building blocks, five flows to start with, the mistakes that make customers hate bots, and the steps to build one.

What is a WhatsApp chatbot, and how is it different from an AI agent?

A rule-based chatbot follows a script you write; an AI agent writes replies in natural language from information you give it. Both answer on your business number, and many businesses use both. A rule-based bot suits fixed journeys such as order tracking or booking. An AI agent suits open questions such as product advice.

If you want the AI kind, see ConvoBox AI agents. Full chatbots like the ones here run on the WhatsApp Business API, not the ordinary app. If you aren't sure which one you have, read the app vs API comparison.

How does a WhatsApp chatbot work?

Every chatbot is assembled from the same handful of pieces, so once you know them you can read almost any flow.

• Trigger. What starts the bot: a keyword like "MENU", any first message, a click-to-WhatsApp ad, a store event or a webhook.
• Message. Text, image, video or a PDF such as a price list.
• Buttons and lists. Reply buttons show up to three tap-to-answer options. A list opens a menu of up to ten rows. Call-to-action buttons open a link or start a call. Tapping is usually easier for customers than typing on a phone.
• Question. The bot asks for a name, address, location or other detail and saves the answer to the contact.
• Condition. The bot branches on an answer, a tag, a field or the time of day.
• Delay. Wait minutes, hours or days before the next step.
• Handover. The bot assigns the chat to a person or team, who see everything the customer already answered.

One more thing to know is the 24-hour window. Free-form bot messages only work within 24 hours of the customer's last message. After that, the bot has to send an approved message template.

What does a simple chatbot conversation look like?

Below is a main menu for a made-up saree shop. Tap the buttons to follow each path. Every branch ends with an answer or a person, which is the habit worth copying.

Which five chatbot flows should most businesses build first?

Start with the questions your team answers every day. These five are a reasonable starting set for a small business (our suggestion, not a standard), and you can build them one at a time.

1. FAQ and main menu

This is the bot above. Trigger on any first message. Offer a list of the questions people ask most: timings, location, prices, delivery. End each answer with "Anything else?" and a link back to the menu plus a human option.

2. Order status

Ask for the order ID, look it up (through a store connection or a webhook) and share the latest update with a tracking link. Where-is-my-order chats are repetitive, so this one often saves your team the most time.

3. Lead qualification

Say you sell plots near Hosur. Ask budget with three buttons, ask when they plan to buy, then tag the lead and assign the serious ones to sales. The bot asks the same questions in the same order every time, so your salespeople start each call with the answers already in hand.

4. Appointment booking

For clinics, salons, coaching centres and service businesses. A WhatsApp Flow opens a native form inside the chat where people choose a service, a date and a time. Save the answer to the contact and send a reminder before the appointment.

5. Catalog and product finder

Ask what the customer wants (category, budget, size) and send matching products from your WhatsApp catalog. Multi-product messages can show up to 30 products in sections. Add a button to talk to someone for custom requests.

How do you build a WhatsApp chatbot without coding?

Pick a provider with a visual builder, draw the flow on paper first, then build it on the canvas and test it on your own phone. Skip the paper and you'll end up redrawing branches on screen.

1. List the top five questions

   Look at your last week of chats. Which five questions came up most? Those are your first menu options.

2. Sketch the flow on paper

   Draw boxes: welcome, options, answers, human handover. Every branch needs an ending: an answer, a form or a person.

3. Choose a trigger

   A first message or a keyword. For ads, an ad click can start a different flow from your normal menu.

4. Build the messages

   Keep each one short. Use buttons for up to three options and a list for up to ten. Write the way you'd speak at the counter.

5. Add the handover

   Add an assign step to a named agent or team, so people always have a way out. WhatsApp's policy also expects automated chats to have a clear path to a human.

6. Test every branch

   Send the keyword from your own phone and tap every button. Ask a friend to break it by typing odd things.

7. Publish, then read real chats

   For the first week, read what customers actually type. Add the questions you missed and fix any branch where people give up.

What mistakes make customers hate WhatsApp chatbots?

Dead ends and no way to reach a person top the list. The rest are smaller, but they add up.

• Dead ends. A reply with no buttons and no next step leaves people stuck. End every branch with a menu link or a human.
• No human route. If someone is angry or confused, the bot must pass them on quickly.
• Too many options. Three buttons or a short list beats a wall of text. Start with five menu items, not twenty.
• Replying only to exact words. Customers type "hii", "price?" and "ek saree dikhao". When the bot doesn't understand, fall back to the menu instead of repeating "I didn't get that".
• Long messages. Walls of text on a phone screen are easy to skip.
• Ignoring after-hours. Tell people when a human will reply, and keep that promise.
• Never reading the chats. Real conversations show you what to fix, but only if someone looks.

What should you check before you publish a chatbot?

Go through this list on your own phone before customers see the bot. Ticks are saved on this page.

• Every branch ends in an answer, a form or a human
• There is a "Talk to a person" option on the main menu
• Messages are short enough to read without scrolling
• I tested every button and list option on my own phone
• The bot saves names and answers to the contact record
• Someone is assigned to take over handed-over chats
• After-hours chats get a message saying when we'll reply
• Templates for messages after 24 hours are approved
• I'll read real chats after the first week and fix gaps

How do you build this in ConvoBox?

ConvoBox has a drag-and-drop workflow builder with triggers, buttons, lists, questions, conditions, delays, template steps, WhatsApp Flows and an assign-to-agent step. You connect the nodes, test with a keyword from your phone and switch the workflow on. Details are on the chatbot and workflow builder page.

Handed-over chats land in the shared team inbox with the customer's answers attached, and a workflow can also pass open questions to an AI agent. See pricing for which plan includes which builder.