10 WhatsApp Chatbot Examples That Actually Convert (With Templates)

A customer messages your business on WhatsApp at 11 PM asking where their order is. Nobody's online. By morning, they've already asked the same question on Instagram, then given up and filed a refund request.

That's the gap a good WhatsApp chatbot closes. Not by replacing your team, but by handling the predictable 70-80% of conversations so your team can focus on the ones that actually need a human.

This article walks through 10 WhatsApp chatbot examples that Indian businesses use to convert more chats into sales and fewer tickets into escalations. Each one comes with the actual message flow, when to use it, and what it can't do. Copy the pattern, adapt the wording, and you'll have a working chatbot faster than you'd expect.

1. The Welcome and Menu Bot

This is the first message a customer sees, and it sets the tone for everything after.

The flow:

1. Customer messages your WhatsApp number for the first time
2. Bot replies with a greeting and 3-4 quick-reply buttons: "Track Order," "Browse Products," "Talk to Support," "Something Else"
3. Each button routes to a different flow

A jewellery brand running festive-season campaigns, for example, could use buttons like "New Arrivals," "Track Order," and "Custom Design Enquiry" so first-time chatters get routed correctly without typing a word.

Benefits: Sets clear expectations, reduces "what do I do now" confusion, and gives you clean data on why people are messaging.

Limitations: If your button labels are vague or there are more than 4-5 options, people get overwhelmed and just type anyway. Keep it short.

Template CTA: Start from a ready-made welcome flow in Mindlytics' WhatsApp chatbot builder and edit the button labels to match your business.

2. The FAQ and Knowledge Base Bot

This is the workhorse. It answers the questions your team answers 50 times a day: return policy, delivery timelines, sizing, store hours.

The flow:

1. Customer asks a question in their own words ("do you ship to Kochi?")
2. Bot searches your knowledge base (the PDFs, help center articles, or Q&A pairs you've uploaded) for the most relevant answer
3. Bot replies with that answer, and offers to connect to a human if it isn't confident

A SaaS company onboarding new signups can use this same pattern to answer product FAQs and walk users through setup, instead of a support agent repeating the same three steps all day.

Benefits: Handles genuinely unpredictable phrasing, not just exact keyword matches. Reduces repetitive tickets significantly, since customers get answers instantly instead of waiting for business hours.

Limitations: It's only as good as the knowledge base behind it. If your return policy PDF is outdated, the bot will confidently give the wrong answer. Review and update your source documents regularly.

Template CTA: Upload your FAQs as PDFs, URLs, or plain Q&A pairs in Mindlytics' WhatsApp chatbot builder and the AI agent retrieves the right answer before every reply.

3. The Order Tracking Bot

For any business shipping physical products, "where is my order" is the single most repeated question on WhatsApp.

The flow:

1. Customer asks about their order, or clicks "Track Order" from the welcome menu
2. Bot asks for the order number (or looks it up automatically if the number is linked to their WhatsApp)
3. Bot pulls live status directly from your store (for example, a Shopify order lookup) and replies with fulfillment stage and tracking link
4. If the order shows a delay or exception, bot offers to escalate to a human

A D2C skincare brand shipping across tier-2 India, where delivery timelines vary a lot by pin code, can use this to cut "where's my order" tickets without hiring extra support staff.

Benefits: Customers get an instant, accurate answer instead of a canned "we'll check and get back to you." No manual copy-pasting order data between systems.

Limitations: Only works as well as your store's own order data. If your courier partner's tracking updates lag, the bot will pass that lag on to the customer.

Template CTA: Connect your Shopify store once, and the same order-lookup flow runs on autopilot inside your chatbot builder.

4. The Cart Recovery Flow

Someone added a product to cart, got distracted, and never came back. This flow nudges them back on WhatsApp, where open rates are far higher than email.

The flow:

1. Triggered a few hours after an abandoned cart (via your store integration)
2. Bot sends a message with the specific product they left behind and a direct checkout link
3. If they reply with a question ("does this come in blue?"), the bot answers from your product knowledge base
4. Optional: a time-bound discount code if they complete checkout within a set window

Benefits: WhatsApp messages get opened and read far more reliably than marketing emails, so cart recovery messages actually get seen.

Limitations: Overuse burns trust fast. Sending a discount on every single abandoned cart trains customers to always wait for one. Use it selectively, and always inside Meta's messaging guidelines for promotional content.

Template CTA: Pair this flow with a broadcast campaign to reach recent cart-abandoners at the right time.

5. The Lead Qualification Bot

Before your sales team spends 20 minutes on a call, this flow figures out if the lead is worth that time.

The flow:

1. Lead messages in after clicking a Click-to-WhatsApp ad or filling a website form
2. Bot asks 2-3 qualifying questions (budget range, timeline, use case) using quick-reply buttons where possible
3. Based on the answers, the bot either books a call, sends relevant info, or politely routes low-intent leads to a nurture sequence
4. Qualified leads get handed off to a sales rep with the full conversation summary attached

Real estate brokers and ed-tech companies running admissions campaigns use a near-identical version of this to separate serious buyers from window-shoppers before a human ever gets involved.

Benefits: Sales reps stop wasting time on unqualified leads, and serious leads get faster attention because they're flagged and routed automatically.

Limitations: Ask too many questions and people drop off mid-flow. Three questions is usually the ceiling before qualification starts costing you leads.

Template CTA: Combine this with Click-to-WhatsApp ad campaigns so every ad click lands directly into a qualifying conversation.

6. The Appointment Booking Bot

For clinics, salons, gyms, and consultants, this flow replaces the back-and-forth of "are you free Tuesday?" messages.

The flow:

1. Customer asks to book an appointment, or taps a "Book Now" button
2. Bot shows available slots (pulled from your calendar or booking system)
3. Customer picks a slot, bot confirms with date, time, and location
4. Automated reminder sent 24 hours and 1 hour before the appointment

Benefits: Fewer no-shows because of the automatic reminders, and no staff time spent manually checking availability for every enquiry.

Limitations: Needs a connected calendar or booking system to show real availability. Without that, you're back to manual confirmation, which defeats the purpose.

Template CTA: Build this as a guided flow in your chatbot builder, with a human handoff option for anyone who needs a custom time slot.

7. The COD Verification Bot

Cash-on-delivery still makes up a large share of e-commerce orders in India, and it's also where return-to-origin (RTO) losses hurt sellers most. This flow confirms genuine orders before they ship.

The flow:

1. Immediately after a COD order is placed, bot messages the customer to confirm the order details
2. Customer confirms with a simple "Yes" button, or cancels if it was a mistake
3. Orders that go unconfirmed after a set time get flagged for manual review before dispatch

Benefits: Fewer fake or accidental COD orders reaching the shipping stage, which directly reduces RTO costs and wasted logistics spend.

Limitations: Some customers ignore the confirmation message entirely, so this reduces RTO risk, it doesn't eliminate it. Pair it with your existing fraud checks rather than replacing them.

Template CTA: This is one of the simplest flows to set up: three steps, one confirmation button, and it plugs directly into your order pipeline.

8. The Feedback and Review Collection Bot

Getting reviews on your website or Google listing usually means asking in an email nobody opens. Asking on WhatsApp, where the order confirmation already lives, works better.

The flow:

1. Triggered a day or two after delivery is confirmed
2. Bot asks a simple 1-5 rating question
3. High ratings get a follow-up asking for a public review, with a direct link
4. Low ratings route straight to a human agent instead of a public review link, so issues get resolved privately first

Benefits: Higher response rates than email surveys, and a built-in way to catch unhappy customers before they leave a public complaint.

Limitations: Don't send this immediately after delivery. Give the customer time to actually use the product, or you'll get shallow, low-value feedback.

Template CTA: Set the trigger delay once inside your automation flow and it runs for every order going forward.

9. The Event and Webinar Reminder Bot

For businesses running webinars, workshops, or in-person events, this flow handles RSVPs and cuts no-shows.

The flow:

1. Customer registers via a form or ad, and gets an instant WhatsApp confirmation
2. Bot sends a reminder 24 hours before, and again 1 hour before
3. On the day, bot sends the joining link or venue details automatically
4. Post-event, bot sends a short feedback question or a recording link

Benefits: Attendance rates improve meaningfully with timely reminders, since WhatsApp notifications are far harder to miss than an email buried in a promotions tab.

Limitations: Works best for events with a fixed date and time. For open-ended or rolling registrations, you'll need a slightly different trigger setup.

Template CTA: Chain this together with a broadcast list for your registered attendees.

10. The Human Handoff Bot

This isn't really a standalone flow. It's the safety net underneath every flow above, and it's the difference between a chatbot that frustrates people and one that quietly does its job.

The flow:

1. At any point in a conversation, the customer can ask for a human, or the bot detects low confidence in its own answer
2. Bot replies letting them know a team member is being looped in
3. The conversation routes into your shared team inbox, along with a summary of what's already been discussed
4. Your agent picks up the conversation with full context, instead of asking the customer to repeat everything

Benefits: Customers never feel stuck talking to a bot that can't help. Your team never starts a handoff cold, which makes the actual human conversation faster.

Limitations: This only works well if your team is actually monitoring the inbox during business hours. A handoff that sits unanswered for six hours is worse than no handoff at all.

Template CTA: This comes built into the Mindlytics AI Agent: when confidence is low or a customer asks for help, it escalates automatically with the full conversation attached.

How to Pick the Right Flow for Your Business

Don't try to build all 10 on day one. Start with whichever one solves your loudest current problem.

• Getting flooded with "where's my order" messages? Start with #3.
• Losing sales to unanswered questions after hours? Start with #2.
• Spending sales time on unqualified leads? Start with #5.
• High RTO on cash-on-delivery orders? Start with #7.

Every other flow can be layered in once the first one is working. Most Mindlytics customers get their first flow live within about 15 minutes, since setup is mostly naming the bot, connecting a knowledge base or calendar, and turning it on.

One more thing worth knowing: every message these chatbots send still runs on Meta's official WhatsApp Business API, and Mindlytics passes through Meta's per-message rate with zero markup. You're not paying extra for the automation itself, only for the messages Meta charges for.

FAQ

Do I need to know how to code to build these flows? No. All 10 flows above are built with a drag-and-drop, no-code chatbot builder. If you can describe the steps of a conversation, you can build the flow.

How is a WhatsApp chatbot different from an AI agent? A traditional chatbot follows a fixed decision tree: button A leads to message B. An AI agent (like the one described in flows #2, #3, and #10 above) understands free-text questions, retrieves answers from your own knowledge base, and calls tools like order lookups before deciding whether to answer or hand off to a human.

Can I use my own AI model for the chatbot? Yes, if your platform supports "bring your own key." That means you connect your own OpenAI, Anthropic, Google Gemini, or Groq account, so you control the model, the cost, and where your data goes.

Will customers know they're talking to a bot? It's good practice to say so upfront, in the welcome message. Most customers don't mind talking to a bot for simple questions as long as getting to a human is always one message away.

What happens if the bot doesn't know the answer? A well-built flow always has a handoff path. If the bot's confidence is low, or the customer explicitly asks for a person, the conversation should route to your team inbox with context attached, not leave the customer stuck.

Do these flows work on the free WhatsApp Business API plan? Basic flows like the welcome menu and simple FAQ bots typically work on free or starter plans. More advanced automation (like AI agents connected to a knowledge base, or unlimited flows) is usually part of paid plans, so check what your platform includes at each tier.

How long does it take to set up a chatbot like this? For the simpler flows (#1, #6, #7, #9), most businesses are live within an hour. Knowledge-base-driven flows (#2, #3, #10) take a bit longer since you need to upload your FAQs or connect your store first, but it's still usually a same-day setup.

Is this the same as WATI's or Interakt's chatbot builder? The building blocks are similar across most WhatsApp platforms: drag-and-drop flows, quick-reply buttons, and template libraries. What differs is depth of AI capability (knowledge base retrieval, tool calls like order lookup, and human handoff with context) and, in Mindlytics' case, that you pay Meta's message rate directly with no markup layered on top.

Start Building

Reading about flows is one thing. Having one live on your number by this afternoon is another.

Pick the flow from this list that solves your biggest current problem, whether that's order tracking, FAQ overload, or leads slipping through the cracks. Then build it in Mindlytics' WhatsApp chatbot builder, where you can start from a template, connect your knowledge base or store, and turn it on the same day, with zero markup on every message you send.