The 7 automations every D2C brand should run on WhatsApp
The seven flows worth building first, in the order that usually makes sense, with the trade-off in each one.
HeloFlow team · 19 March 2026 · 9 min read
Most D2C brands switch WhatsApp on and immediately try to build everything. Six weeks later there are fourteen half-finished flows, nobody is sure which ones are live, and the channel has become another thing to maintain.
This playbook is the opposite approach: seven automations, in the order we would build them, each one earning its place before the next goes live. Every one of them is something your customers already expect from a business they have bought from.
A note on honesty: we are not going to quote conversion percentages at you. The numbers vary enormously by category, price point and list quality, and any figure we published would be someone else's, not yours. Build these, measure your own, and compare against your email baseline.
1. Order confirmation
What it is. The moment an order is placed, the customer gets a confirmation in WhatsApp with the order number, what they bought and when it should arrive.
Why it goes first. It is a utility template, so it is easy to get approved. It is genuinely useful, so nobody complains. And it is the message that gets your number into the customer's thread list, which every later automation depends on.
The trade-off. If you also send a confirmation email, some customers get two messages. Most brands find that acceptable for the one transactional message people actually want; if you disagree, pick one channel and commit.
2. Shipping and delivery updates
What it is. Packed, shipped, out for delivery, delivered. Triggered from your store or courier events rather than typed by a person.
Why it comes second. It is the single biggest deflector of "where is my order?" messages, which is the largest support category for nearly every D2C brand.
The trade-off. Four messages per order is too many for low-value items. Most brands settle on two — shipped and out for delivery — and let the tracking link carry the rest.
3. Abandoned cart recovery
What it is. Someone adds to cart, does not check out, and gets one message with the item still in it and a way to finish.
Why it comes third. This is the first automation that makes money rather than saving support time, and it works on WhatsApp partly because the message gets seen.
How to build it well. Send one message, not a sequence. Wait long enough that the person has genuinely stopped rather than gone to make tea — an hour is a reasonable starting point. Include the actual product, not a generic reminder. Do not lead with a discount: you will train customers to abandon carts deliberately, and you will discount people who were going to buy anyway.
The trade-off. This is a marketing template, so it needs opt-in and a harder approval. It is worth the extra work, but it is not a same-afternoon job like the first two.
4. COD confirmation
What it is. For cash-on-delivery orders, a message asking the customer to confirm before you dispatch.
Why it matters in India specifically. Return-to-origin on unconfirmed COD orders is a real and expensive problem. A one-tap confirmation before the parcel leaves your warehouse is the cheapest intervention available.
A useful addition. Offer a prepaid option in the same message with a small incentive. Some customers will switch, and a prepaid order is worth more to you than a confirmed COD one.
The trade-off. You are adding a step before dispatch, so your flow needs a sensible fallback: if there is no reply within a set time, either dispatch anyway or call. Decide which, and make the automation do it rather than leaving parcels in limbo.
5. Review and user-generated content requests
What it is. A few days after delivery, ask how it went.
Why it works better here than in email. Replying takes one tap, and a photo is trivial to send from the app the message arrived in. The same request by email asks the customer to open a browser and log in.
How to build it well. Ask a single question with buttons rather than a link to a review form. Route low ratings to a person instead of a public review page — that is not review-gating, it is dealing with an unhappy customer properly before asking them to publish anything.
The trade-off. Timing is product-dependent. Three days is right for clothing, wrong for a mattress, useless for supplements someone has not opened. Set it per category rather than globally.
6. Replenishment and reorder nudges
What it is. For consumables, a message timed to when the customer would plausibly be running out, with a one-tap reorder.
Why it comes here. It only works once you have enough order history to estimate the cycle, and it needs the first five automations to have earned enough goodwill that the message reads as helpful.
How to build it well. Base the timing on the pack size, not a flat 30 days. Make reordering a single tap of the exact previous order. Suppress it for anyone who has already reordered.
The trade-off. Get the timing wrong and this is the automation most likely to feel like nagging. Start conservative, err late rather than early.
7. Broadcast campaigns for launches and sales
What it is. The actual marketing broadcast — a new collection, a sale, a restock.
Why it goes last. It is the one people want to build first, and it is the one that damages your number if the other six have not established that your messages are worth receiving. Broadcasting to a list that has never had a useful message from you produces blocks, and blocks lower your quality rating, which lowers your messaging limits.
How to build it well. Segment properly: people who bought this category, people who opened the last one, people who have not bought in six months. Cap the frequency and stick to it. Include an opt-out in every marketing broadcast and honour it immediately.
The trade-off. This is where the discipline costs you something. A brand that broadcasts weekly to everyone will get more clicks this month and a damaged number by quarter end.
Building them in order
The sequence matters more than any individual flow. The first two are utility templates that are easy to approve and impossible to resent. They get your number established and your quality rating healthy. Three through six are progressively more commercial and progressively more dependent on the goodwill the first two built. The seventh only works on the foundation of all of them.
If you take one thing from this playbook: a WhatsApp number that customers are glad to have in their thread list is an asset, and you build it in exactly this order.
Want help mapping these to your store? Book a demo and bring your order flow — that is the conversation we are best at.
