WhatsApp Automation Flows That Actually Convert (With Real Templates)
Broadcasting to your whole list on a schedule is the wrong model for WhatsApp. Automation flows are the right one: messages that fire on a trigger — the welcome after opt-in, the shipped update when an order leaves your warehouse, the review ask five days after delivery. Each is a reply-able conversation, not a one-way blast, so it gets answered. Run them on The Tech Pad, built on the official WhatsApp Cloud API with no per-message markup — you pay Meta's rate and nothing on top. Start free at thetechpad.com/wa with no credit card; the first month is free on paid plans. Here are the six flows that earn their keep.
Why Flows Convert
A broadcast asks thousands of people to care about the same thing at once. A flow talks to one person about something they just did — placed an order, left a cart, got a delivery. WhatsApp messages post open rates around 98 percent versus roughly 20 percent for email; a message that asks something gets a median reply in under 90 seconds. People answer messages about their own orders.
Flows also prevent support tickets: the "where's my order?" question disappears when the update arrives first. One mechanic matters: beyond the 24-hour window since a customer's last reply, WhatsApp only lets businesses start conversations with pre-approved templates.
Flow 1: Welcome and Opt-In Confirmation
Trigger: a new opt-in — checkout consent, the chat widget, or a keyword like START — or the first order. Delay: immediately. Goal: confirm the signup, set expectations, prove two-way chat.
The first message does the compliance work: restate what they signed up for and show how to leave. STOP matters — marketing messages require an opt-out path.
Hi {{1}} — thanks for order #{{2}}! You're all set: we'll message you when it ships and keep promotions rare. Questions? Reply here — a real person answers. Want fewer messages? Reply STOP anytime.
{{1}} is the first name, {{2}} the order number. No purchase yet? Swap {{2}} for what they requested — a guide or code — so the confirmation proves you listened.
Flow 2: Order Lifecycle Updates (Placed, Shipped, Delivered)
Trigger: the order status changes. Delay: at each event — confirmed, shipped, delivered. Goal: replace "where's my order?" tickets with proactive updates.
This is the support-ticket killer: confirmed when payment clears, shipped with the delivery date, delivered closing the loop — three short messages that replace dozens of daily inbound questions, each a thread the customer can reply to.
Hi {{1}} — order #{{2}} has shipped! We'll message you when it's out for delivery. Need to change the address? Reply here and we'll sort it.
Send only the events that apply — a "confirmed" ping on a two-day shipment is noise. For the questions it still misses, an [AI "where is my order" auto-answer](/blog/ai-answer-where-is-my-order-whatsapp/) catches stragglers.
Flow 3: Abandoned-Cart Recovery (6, 24, 72 Hours)
Trigger: checkout started, no order placed. Delay: 6 hours, then 24, then 72. Goal: recover the sale while intent is warm, with a link back to checkout.
Recovery over WhatsApp converts at 15–30 percent versus 2–5 percent for email follow-ups, and timing is why: at six hours the decision is fresh, at 72 a final nudge closes the sale or proves it won't. Keep it to three messages.
Hi {{1}} — you left the {{2}} in your cart, so we saved it for you. Tap below to pick up where you left off. Questions? Reply here — a real person will help you decide.
{{1}} is the first name, {{2}} the product name. Keep the first message helpful; save the discount for the 24-hour one. [Prebuilt cart recovery templates](/blog/whatsapp-abandoned-cart-recovery-templates/) cover the sequence.
Flow 4: COD Confirmation Before Dispatch
Trigger: a cash-on-delivery order is placed. Delay: within the hour, always before dispatch. Goal: a one-tap confirm so you only ship orders the customer expects.
Some COD orders are fake — wrong numbers, pranks, impulse regrets — and each one you ship costs freight both ways. Confirming before dispatch cuts fake orders and return-to-origin shipments: the people behind those orders never tap confirm.
Hi {{1}} — quick check on order #{{2}}: it's cash on delivery, so confirm before we dispatch. Tap "Confirm my order" and it ships today. Didn't place it? Tap "Cancel" and we'll stop it.
Make Confirm and Cancel the only actions and never ship on silence — set a cutoff for human follow-up. Full setup: our [COD confirmation guide](/blog/cod-confirmation-whatsapp-cut-rto-fake-orders/).
Flow 5: Win-Back for Lapsed Buyers
Trigger: a past buyer with no new order in 60+ days. Delay: 60 days after the last order, capped at one or two per quarter. Goal: bring a known buyer back with a personal, value-first message.
This is where stores get greedy — monthly blasts until the list is numb. Do the opposite: segment by what they bought, send rarely, drop anyone who ignored your last two messages. Caps protect reply rates and sender reputation.
Hi {{1}} — it's been a while since you ordered the {{2}}, and we've restocked some things you'd probably like. Tap below to take a look. Prefer not to hear from us? Reply STOP.
Win-back is MARKETING, so it needs opt-out language and Meta approval — budget a few days. The {{2}} reference is what separates it from spam.
Flow 6: Review Request Five Days After Delivery
Trigger: the order is marked delivered. Delay: five days after delivery. Goal: turn a delivered order into a review, with an escape hatch attached.
Reviews respond 3–5x better to a WhatsApp ask than to email — the message opens, and the ask is one thumb-tap with the product photo attached. Five days after delivery is the sweet spot. Pair the ask with a "Need help" button so a bad experience lands as a conversation, not a public one-star review.
Hi {{1}} — your {{2}} arrived a few days ago. How is it treating you? Tap "Leave a review" — it takes ten seconds. Not right? Tap "Need help" and we'll fix it first.
{{1}} is the first name, {{2}} the product name. Route "Leave a review" to your Google listing and "Need help" to your team — the [review request templates](/blog/whatsapp-review-request-templates/) post covers fields and routing.
The Six Flows at a Glance
| Flow | Trigger | Delay | Goal |
|---|---|---|---|
| Welcome / opt-in confirmation | New opt-in or first order | Immediate | Confirm consent, set expectations, prove two-way chat |
| Order lifecycle updates | Order status changes | At each event: placed, shipped, delivered | Replace "where's my order?" tickets proactively |
| Abandoned-cart recovery | Checkout started, no order | 6h → 24h → 72h | Recover the sale with a link back to checkout |
| COD confirmation | COD order placed | Within the hour, before dispatch | One-tap confirm; cut fake orders and return-to-origin shipments |
| Win-back for lapsed buyers | No order in 60+ days | 60+ days after last order, capped | Bring a known buyer back with a personal offer |
| Review request | Order marked delivered | 5 days after delivery | Turn a delivered order into social proof |
Human Handoff: When a Flow Should Stop
A flow should never be a dead end: every template above needs an escape hatch — a "Need help" or Cancel button — because some requests shouldn't run on autopilot. Refunds, damage complaints, chargeback threats — anything large or emotional needs a human.
Reply-able design pays off twice: when a customer answers a flow message, the 24-hour window opens and your team responds in the same thread — no new template. Run flows beside a shared team inbox so both share one history; [The Tech Pad's shared inbox](/features/inbox/) shows flow history, order details, and taps side by side.
Building the Flows
Setup is the same for all six, in four steps:
- Connect your store or import contacts. The free Shopify and WooCommerce connectors push orders and cart events into the flow engine so messages fire on real data; imported contacts need recorded opt-in.
- Write and submit templates in the Templates Hub. Submit each under its Meta category: UTILITY for service messages — order updates, shipping, COD confirmation, review asks — approving in minutes to hours; MARKETING for win-back and promotions, needing opt-out language and more time.
- Map triggers and delays. Create a flow rule per event: trigger, template, delay. Start with the short ones — welcome immediately, COD confirm within the hour — then add longer sequences once stable.
- Watch delivery analytics. Track delivered rates, replies, and quick-reply taps per flow: falling replies means stale copy; rising blocks or complaints hurts sender quality. Meta charges per business-initiated message, so unread flows cost you twice.
Running WooCommerce? Our store-specific walkthrough maps these flows onto order statuses in the connector plugin.
Start With One Flow This Week
Don't launch all six at once. Pick the one that fixes your most expensive problem — for most stores that's COD confirmation or order lifecycle updates — and ship it this week: create your free account at thetechpad.com/wa, connect the store, submit your first template. To scale, [campaigns](/features/campaigns/) handles one-off broadcasts while flow rules keep triggered messages running, and every reply lands in the shared inbox with order context. No per-message markup, no credit card to start — just flows that convert.