Most businesses use WhatsApp the same way they use SMS — one message at a time, manually, whenever someone remembers to send it. That works until you have more than 50 customers. After that, it becomes a bottleneck.
Automation flows change this. A flow is a sequence of messages that triggers automatically based on a customer action, a time condition, or an event in your business systems. Once set up, they run without anyone touching them.
Table of Contents
- What is a WhatsApp automation flow?
- Flows by business goal
- The 12 essential flows
- Flow trigger types and how to use them
- Common mistakes that kill performance
- Setting up flows in Kliovo
- Frequently Asked Questions
What is a WhatsApp automation flow?
A WhatsApp automation flow is a pre-built message sequence that triggers based on a defined event. Unlike a simple auto-reply (one trigger, one response), a flow can:
- Send multiple messages over time with delays
- Branch based on customer replies or actions
- Pull real-time data from your store or CRM
- Escalate to a human agent at any point
- Stop when a customer performs an action (e.g., confirms an order)
Flows are the backbone of any serious WhatsApp operation. They handle the predictable, repetitive parts of customer communication so your team can focus on conversations that genuinely require human judgment.
Flows by business goal
| Business Goal | Recommended Flows |
|---|---|
| Reduce COD return-to-origin | Order confirmation, Pre-dispatch reminder, Delivery day alert |
| Increase revenue | Abandoned cart recovery, Re-engagement, Post-purchase upsell |
| Reduce support load | Order tracking, FAQ bot, Complaint auto-acknowledgment |
| Build loyalty | Post-delivery follow-up, Review request, VIP broadcast |
| Operational efficiency | Appointment reminder, Lead qualification |
The 12 essential flows
1. COD Order Confirmation
Trigger: New COD order placed
Goal: Confirm customer intent before dispatching
Message within 60 seconds of order placement:
"Hi [Name], we received your order for [Product] (Rs. [Amount]) to be delivered to [Address]. Reply YES to confirm or CHANGE to update details."
If no reply after 2 hours, send a follow-up. If no reply after 4 hours, flag for manual review. This single flow reduces return-to-origin rates by 40–50% for most stores.
2. Order Dispatch Notification
Trigger: Order status changes to "Dispatched"
Goal: Set delivery expectations and reduce "where is my order" calls
"Your [Product] has been dispatched with [Courier]. CN: [Tracking No.]. Expected delivery: [Date]. Track here: [Link]. Have Rs. [Amount] ready."
This flow eliminates a category of inbound support queries entirely.
3. Delivery Day Alert
Trigger: Shipment status = "Out for delivery" (via courier API)
Goal: Reduce failed delivery attempts
"Your order is out for delivery today. The rider will call before arriving. Please have Rs. [Amount] ready. Reply RESCHEDULE if today doesn't work."
4. Failed Delivery Recovery
Trigger: Courier marks delivery as "Attempted — recipient unavailable"
Goal: Recover the order before it's returned
"We tried delivering your order today but couldn't reach you. Reply with a preferred date and we'll rearrange. Or reply CANCEL if you no longer want it."
Connects to courier API to reschedule attempts directly. Turns RTOs into recovered deliveries.
5. Abandoned Cart Recovery
Trigger: Customer adds items to cart but doesn't complete purchase (WooCommerce/Shopify webhook)
Goal: Recover lost sales
Message 1 (1 hour after abandonment):
"Hi [Name], you left something in your cart — [Product(s)]. Still interested? Complete your order here: [Link]"
Message 2 (24 hours later, if no purchase):
"Your cart is still waiting. We'll hold it for 48 more hours. [Link]"
Message 3 (48 hours later, with incentive):
"Last chance for your [Product]. Here's 10% off if you order in the next 24 hours: [Code]"
Average recovery rate for a 3-message sequence: 8–15% of abandoned carts.
6. Post-Purchase Follow-Up
Trigger: Order delivered (courier confirms)
Goal: Build relationship, surface issues before they escalate
Sent 24–48 hours after delivery:
"Hi [Name], we hope your [Product] arrived in great condition. Did everything look good? Reply YES or let us know if there's an issue."
Customers who feel cared for post-delivery are 3x more likely to reorder.
7. Review Request
Trigger: 48 hours after delivery confirmed
Goal: Generate authentic reviews and social proof
"Hi [Name], how was your experience with [Product]? If you're happy, it would mean a lot if you left us a quick review: [Link]. Takes 30 seconds."
8. Re-engagement Campaign
Trigger: Customer hasn't ordered in X days (configurable: 30, 60, 90 days)
Goal: Win back lapsed customers
"Hi [Name], it's been a while. We've added [New Products/Collection] since your last order. Here's 15% off to come back: [Code]. Valid for 5 days."
9. Appointment Reminder (service businesses)
Trigger: 24 hours before a scheduled appointment
Goal: Reduce no-shows
"Reminder: Your [Service] appointment is tomorrow at [Time] at [Location]. Reply CONFIRM to keep it or RESCHEDULE if you need to change."
A second reminder 2 hours before the appointment further reduces no-shows.
10. Inbound FAQ Bot
Trigger: Customer sends a keyword or message
Goal: Handle routine queries without agent involvement
Common triggers and responses to automate:
| Customer Message | Auto-Response Type |
|---|---|
| "price" / "rate" / "kitna hai" | Product catalog or price list |
| "delivery" / "shipping" / "kb milega" | Delivery policy + timeframes |
| "return" / "wapas" | Return policy |
| "track" / "order status" | Order tracking link |
| "contact" / "number" | Business contact details |
| "timings" / "hours" | Operating hours |
11. Lead Qualification Flow
Trigger: New contact messages for the first time
Goal: Qualify the lead before routing to sales
"Hi! Thanks for reaching out to [Business]. To help you better, are you looking for: (1) Personal use (2) Business/bulk order (3) Something else?"
Branch based on reply:
- Option 1 → consumer catalog flow
- Option 2 → B2B inquiry routing to sales agent
- Option 3 → open question, route to agent
12. VIP Customer Recognition
Trigger: Customer crosses an order count or lifetime value threshold
Goal: Reward loyal customers and increase lifetime value
"Hi [Name], you're one of our top customers — thank you. As a VIP member, you now get priority support and early access to new arrivals. Here's something exclusive for you: [Offer]."
Flow trigger types and how to use them
| Trigger Type | How It Works | Best Used For |
|---|---|---|
| Keyword | Customer sends a specific word or phrase | FAQ responses, menu navigation |
| Order event | Webhook from store (placed, confirmed, shipped) | COD confirmation, dispatch notification |
| Courier event | Courier API status change | Delivery alerts, failed delivery recovery |
| Time-based delay | X hours/days after a previous action | Follow-ups, re-engagement |
| Segment entry | Customer meets a filter (inactive, high value) | Re-engagement, VIP recognition |
| Form submission | Customer fills a WhatsApp form | Lead capture, feedback collection |
| Button tap | Customer taps a quick-reply button | Branching menus, confirmation flows |
| AI escalation | AI can't handle a message confidently | Human handoff trigger |
Common mistakes that kill performance
Sending too many messages. More than 4–5 messages per order cycle leads to customers blocking your number. Keep sequences tight.
Generic templates. "Your order has been confirmed" gets ignored. "Hi Ayesha, your Blue Lawn Suit (Unstitched, Size M) is confirmed for delivery to DHA Phase 5" gets read.
No escalation path. Every automated flow needs a human fallback. If a customer replies with something the flow can't handle, they should reach a real agent — not hit a dead end.
Wrong timing. The initial order confirmation should fire within 60 seconds. Delivery alerts should go out in the morning (7–9am), not at 11pm when they'll be ignored.
Not including the COD amount. Pakistani customers need to mentally prepare the cash. Every delivery-related message should include the exact amount.
Setting up flows in Kliovo
Kliovo's visual flow builder lets you build all 12 of these flows without writing code:
- Choose a trigger — keyword, order event, time delay, courier status
- Add message blocks — drag in WhatsApp template messages or free-form messages
- Add conditions — branch based on customer reply, order value, city, or any stored contact field
- Set delays — schedule follow-ups at exact intervals
- Add escalation points — define which conditions route to a human agent
- Publish and test — test with your own number before going live
Pre-built flow templates for COD confirmation, cart recovery, and delivery sequences are included. Most businesses have their first five flows live within a day of onboarding.
Frequently Asked Questions
Q: Do automation flows require pre-approved templates?
Business-initiated messages (where your business sends first) must use Meta-approved templates. Replies within an open 24-hour service conversation can be free-form. Kliovo submits templates on your behalf as part of onboarding.
Q: Can a customer opt out of automated flows?
Yes — and they should be able to. Any customer who replies "STOP" or similar should be removed from automated sequences. This is both a Meta policy requirement and good practice for protecting your sender reputation.
Q: What happens if the automation flow and a live agent respond at the same time?
Kliovo's system pauses automation when a conversation is assigned to a human agent. When the agent closes or unassigns the conversation, automation can resume. No double-messaging.
Q: Can flows pull live data from my WooCommerce or Shopify store?
Yes — Kliovo's store integrations connect in real time. Order number, product name, delivery address, COD amount, and courier tracking link are all pulled dynamically into template messages.
Q: How do I know if my flows are working?
The Kliovo analytics dashboard shows flow performance: messages sent, delivery rate, read rate, reply rate, and conversion rate (for sales-focused flows). You can see which flows are performing and which need adjustment.
Q: Can one flow trigger another flow?
Yes — you can chain flows. For example, when a customer completes the COD confirmation flow, it can automatically trigger the dispatch notification flow when the courier webhook fires.
Q: What's the maximum number of flows I can have active?
There's no hard cap in Kliovo. In practice, most businesses run 8–15 active flows. Beyond that, overlapping triggers can create complex interactions that are hard to troubleshoot.