WhatsApp Chatbot Flow Design: Templates & Examples

TL;DR: Building a chatbot flow from scratch is slower than adapting a proven structure. This is a swipe file of 7 ready-to-use flows — support triage, lead qualification, appointment booking, e-commerce ordering, onboarding, abandoned cart recovery, and feedback collection — each with its flow diagram, a sample script, the specific node types it's built from, and a customization tip flagging the most common way that flow breaks. A few rules apply across all of them: keep messages short, favor buttons over free text, always show a "talk to a human" option, and design for what happens when someone drops off mid-flow, not just the happy path.

Building a chatbot flow from a blank canvas is the slowest way to start. Most flows that actually work in production follow a small number of proven shapes — the specifics change by business, but the underlying structure repeats constantly. This is a swipe file: seven ready-to-adapt flow templates covering the use cases most businesses actually need, each with the flow structure, sample messaging, and the nodes it's built from.

A Few Design Rules Worth Following in Every Flow

Before the templates themselves, a handful of principles apply across all of them:

• Keep every message to two or three short sentences. WhatsApp is read on a phone, often one-handed — a wall of text gets skimmed, not read.
• Use buttons and list menus over free text wherever the answer set is finite. A tap is faster and more reliable to parse than typed text, and it removes ambiguity from any branching logic downstream.
• Always include a "Talk to a human" option, visible at every stage, not buried three menus deep. A flow with no visible exit frustrates the exact customers who need help most.
• Design for the drop-off, not just the happy path. Every flow below should account for what happens if someone stops responding mid-way, not just what happens if they answer every question in order.

Template 1: Customer Support Triage & FAQ Flow

Use this when: you're fielding repetitive support questions and want to resolve the easy ones automatically while routing anything complex to a human.

Flow structure:

Greeting → "What can I help with?" (list menu)
  ├── Order status → pulls status from order system → done
  ├── Return/refund → policy summary → "Still need help?" → human handoff
  ├── Product question → AI-answered from knowledge base
  └── Something else → immediate human handoff

Sample script:

Bot: Hi! 👋 What can I help you with today? [Order Status] [Returns & Refunds] [Product Question] [Talk to Someone]

Bot (if Order Status selected): Sure — could you share your order number? Bot (after lookup): Your order #4521 shipped yesterday and should arrive by Thursday. Anything else?

Key nodes: List menu (Question node), API node (order lookup), AI node (product FAQ), Human Transfer node.

Customization tip: the "something else" fallback should never be a dead end — even a generic "Let me connect you with our team" keeps the flow from silently failing on anything unanticipated.

Template 2: Lead Generation & Qualification Flow (BANT-Style)

Use this when: you're capturing inbound interest from ads, a website widget, or a QR code, and need to separate serious buyers from casual browsers before involving sales.

Flow structure:

Greeting (with campaign context if available) → Interest confirmation
  → Budget question (buttons: ranges)
  → Timeline question (buttons: this month / this quarter / just researching)
  → Contact detail capture
  → Branch by score:
      High score → notify sales rep + hand off
      Low/mid score → enter nurture sequence

Sample script:

Bot: Thanks for your interest in [Product]! Quick questions so we can point you to the right person. What's your rough budget range? [Under $500/mo] [$500–2000/mo] [Over $2000/mo]

Bot: And what's your timeline to get started? [Ready now] [This quarter] [Just researching]

Key nodes: Question nodes with buttons, Decision/branching node, API node (CRM push + sales notification), Workflow/delay node (for the nurture branch).

Customization tip: keep this to 3–4 questions maximum. A qualification flow that feels like a full application form loses people before it captures anything useful.

Template 3: Appointment or Service Booking Flow

Use this when: you run any business where customers book a slot — clinics, salons, consultants, repair services.

Flow structure:

Greeting → Service type (list menu)
  → Preferred date/time (or "show next available")
  → Confirm slot → Booking confirmation
  → [Automated] Reminder 24h before
  → [Automated] Reminder morning-of

Sample script:

Bot: What would you like to book? [Haircut] [Color] [Consultation]

Bot: Here are the next available slots for a Haircut: [Tomorrow, 2:00 PM] [Tomorrow, 4:30 PM] [Thursday, 11:00 AM]

Bot: You're booked for tomorrow at 2:00 PM. We'll send a reminder the day before. See you then!

Key nodes: List menu, API node (calendar/booking system check), Confirmation message, scheduled Workflow (reminders tied to the actual appointment time, not a fixed daily blast).

Customization tip: always build in a reschedule/cancel path from the reminder message itself — "Reply RESCHEDULE" or a button — rather than forcing the customer to start a new conversation to change plans.

Template 4: E-Commerce Browse & Order Flow

Use this when: you want customers to browse and buy directly inside WhatsApp, especially for post-ad or post-inquiry purchases.

Flow structure:

Greeting → Catalog display (carousel or list)
  → Product selection → Quantity/variant choice
  → Add to cart → "Anything else?" loop
  → Checkout → Payment link
  → Order confirmation

Sample script:

Bot: Here's what's trending right now 👇 [Product carousel: 3–4 items with images and prices]

Bot (after selection): Great choice! What size would you like? [S] [M] [L] [XL]

Bot: Added to your cart. Want to keep browsing, or check out now? [Keep Browsing] [Checkout]

Key nodes: Catalog/carousel node, Question node (variant selection), Cart-state tracking, API node (payment link generation), Confirmation message.

Customization tip: the "keep browsing vs. checkout" fork should appear after every single add-to-cart action — customers regularly want to add one more thing, and forcing checkout immediately loses that upsell moment.

Template 5: Onboarding & Welcome Flow

Use this when: someone just signed up, enrolled, or made their first purchase, and needs a smooth introduction to what happens next.

Flow structure:

Trigger: new signup/enrollment/purchase event
  → Welcome message
  → Key info delivery (schedule, access details, next steps)
  → "Any questions?" check-in
  → Optional: add to relevant group (batch, community, cohort)

Sample script:

Bot: Welcome to [Academy], Priya! 🎉 You're enrolled in the Saturday Batch starting this weekend. Here's what to expect: [schedule link] · [what to bring] · [your coach's contact]

Bot: Any questions before your first session? [I have a question] [All good, thanks!]

Key nodes: Trigger/webhook (fired from an external signup event), sequential Message nodes, Question node (open check-in), Group-add action (if relevant).

Customization tip: trigger this immediately off the actual signup/purchase event, not a scheduled batch job — the value of onboarding drops fast if it arrives hours after someone already expected it.

Template 6: Abandoned Cart Recovery Flow

Use this when: you run e-commerce and want to recover carts left behind at checkout.

Flow structure:

Trigger: cart abandoned for X hours
  → Reminder message with product image
  → Optional incentive (discount, free shipping)
  → Direct checkout link
  → [If no response] second, softer nudge after 24h

Sample script:

Bot: Hey! You left this in your cart 👇 [product image] Complete your order in the next hour and get free shipping. [Complete My Order]

Bot (24h later, if unresponsive): Still thinking it over? Your cart's saved whenever you're ready. [Checkout Link]

Key nodes: Trigger (cart-abandonment webhook from your store), delay/Workflow node, Message node with product image, second delayed follow-up branch.

Customization tip: test the timing of the first message — too soon feels intrusive, too late loses the intent. Most stores find something between 1–4 hours works better than an immediate or next-day send.

Template 7: Feedback & Review Collection Flow

Use this when: you want to capture reviews or feedback right after a service, delivery, or support interaction, while the experience is still fresh.

Flow structure:

Trigger: order delivered / service completed / ticket resolved
  → Short delay (1–2 hours)
  → Rating request (quick scale)
  → Branch by rating:
      High → request public review (with direct link)
      Low → route to support for recovery, don't ask for public review

Sample script:

Bot: How was your experience with us today? [😞] [😐] [🙂] [😍]

Bot (if positive): So glad to hear it! Mind leaving us a quick review? [Review Link] Bot (if negative): Sorry to hear that — we'd like to make it right. Connecting you with our team now.

Key nodes: Trigger (completion event), delay node, Question node (rating scale), Decision/branching node, Human Transfer node (for the recovery branch).

Customization tip: never route a low rating straight to a public review request — branch it to a recovery conversation instead. Asking for a public review right after negative feedback is one of the most common review-flow mistakes.

Putting These Together

Most businesses don't run just one of these — a typical setup might use Template 2 (lead gen) to capture interest, Template 3 (booking) to convert it into an appointment, Template 5 (onboarding) once they're a customer, and Template 7 (feedback) once the service is delivered. Each flow is deliberately modular so it can plug into the next one, triggered by the event that naturally follows.

Bringing It Together

None of these templates need to be built from scratch — copy the structure, adapt the specific questions and branches to your business, and keep the design rules at the top of this article (short messages, visible human handoff, accounting for drop-off) consistent across every flow you build. Start with whichever template matches your highest-volume repetitive conversation today, and expand from there once it's running smoothly.

If you're building these out, Chakra's chatbot builder gives you the node types referenced throughout this guide — Question, Decision, API, AI, and Human Transfer — to assemble any of these flows without needing to code them from scratch.