WhatsApp automation for online stores: what it can and can't do

A WhatsApp automation is a flow you draw once — a trigger, some conditions, and the messages or actions that follow — which then runs on every matching conversation without anyone on your team touching it. It is not an AI that improvises. It is a set of steps you specify, executed exactly as drawn.

That distinction matters, because most content in this space sells a fantasy of a robot that runs your shop. What actually pays is narrower and more boring: a handful of flows that remove repeated typing, catch orders before they turn into losses, and get a human involved at the right moment. This page maps what is real, including the parts that don't exist.

The five flows worth building first

If you run an online store and you have never automated anything on WhatsApp, build these in this order. The order is deliberate — each one either saves money immediately or makes the next one cheaper.

1. Stop the bot when a human replies. Ten seconds of setup. If your team answers a chat while an automation is still waiting for an answer to a question it asked, the customer's next message gets swallowed as that answer. One step fixes it permanently.
2. Order confirmation with buttons. In cash-on-delivery markets this is the highest-value flow in existence, because it catches an unconfirmable order before you pay to ship it. Everywhere else it still earns its keep, because the customer's tap opens a free 24-hour channel.
3. "Where is my order?" The single most repeated question in ecommerce support. Answering it automatically buys back more of your day than anything else on this list.
4. After-hours reply. Customers message at 11pm. A message that says when you reopen prevents the follow-up message at 11:20pm asking if anyone is there.
5. Abandoned checkout recovery. Last, not first — because it is marketing, which means it costs money per message, is subject to per-user limits, and cannot be delivered to US numbers at all.

Notice that four of the five are utility, not marketing. That is not an accident. Utility messages are free inside an open conversation window, unlimited, and deliverable everywhere. Marketing is charged, capped and geographically restricted. Build the free ones first.

What a flow is made of

Every automation is the same four kinds of step, chained together on a canvas.

A useful flow is usually six to fifteen steps. If yours is forty, it is probably two flows wearing a trenchcoat.

What automation genuinely cannot do

This is the section most vendors leave out. Being clear about it saves you building a flow that quietly does nothing.

• Nothing watches your stock levels. There is no "back in stock" trigger, because no stock event is delivered. A waitlist flow can capture who wants what, but you send the "it's back" message yourself as a broadcast. See back-in-stock alerts for the honest version.
• There are no date-based audience filters on lifetime behaviour. You cannot build a segment meaning "hasn't ordered in 60 days" from order history, because no lifetime-order attribute exists. You can get there by having an automation stamp a date onto a contact field each time they order, which is what winning back lapsed customers describes.
• There is no per-contact scheduling. A flow cannot say "message this person on the 14th of next month". It can wait a fixed number of minutes from now, which is a different thing.
• Tracked links give you a click count, not a click-through rate. You cannot segment or re-target on who clicked.
• The AI does not know your stock or your prices unless you put them somewhere it can read. Grounding it is covered in AI answers from your own website.

Which store events can start a flow

If you run Shopify, exactly seven events reach the automation builder. There is no eighth, whatever a competitor's marketing page implies.

One honest caveat on order delivered: it only arrives if your carrier reports delivery back to Shopify, and many do not. Test it with a real order before you build anything that depends on it.

What it costs to run

The single biggest complaint merchants make about WhatsApp automation is a bill that arrived far larger than the plan they signed up for. The cause is almost always the same: there are two bills, not one. Your platform charges a subscription, and Meta charges per delivered template message, directly to you.

Since 1 July 2025 Meta charges per message rather than per conversation, and the rules are set out on its pricing page. The part worth internalising:

• Anything you send inside an open 24-hour conversation window is free.
• Utility templates are free inside that window, charged outside it.
• Marketing templates are charged, always.
• Someone who arrived from a Click-to-WhatsApp ad gives you a 72-hour free window, not 24.

So the cheapest possible automation strategy is not "send fewer messages" — it is "get the customer to tap something early, then say everything else for free". That is the whole argument of the 24-hour window article, and it is the highest-leverage idea on this site.

How many automations should a store actually run?

Fewer than you think. Every marketing message you send competes for the same finite patience, and Meta's per-user marketing limits tighten for recipients who ignore or block messages — a cap that applies across all businesses, not just yours, and for which Meta publishes no specific number.

A store doing under 500 orders a month is well served by four or five flows. The failure mode is not too little automation; it is a customer who gets an order confirmation, a shipping update, a review request and a cart reminder in the same week and mutes you — taking the transactional messages down with the marketing ones.

There is a second ceiling worth knowing before you scale sends. Your account sits in a messaging limit tier that caps how many unique customers you may start conversations with in a rolling 24 hours. New business portfolios start at 250, and the tiers run 250 → 2,000 → 10,000 → 100,000 → unlimited. Meta's messaging limits documentation sets out how you move up: verify your business, or deliver 2,000 messages to unique users outside customer service windows within a 30-day moving period using high-quality templates. Above 2,000 the limit rises one level within 6 hours if you use at least half your current limit within 7 days and quality stays high.

This matters for planning a launch. A store that verifies its business before its first big campaign starts eight times higher than one that does not, and the verification takes days rather than minutes.

Where humans still have to be

Every flow needs an exit to a person, and the flows that annoy customers are the ones without one. Three places to always wire it:

1. The "not found" branch of any lookup.
2. The "unanswered" branch of any AI step.
3. A "talk to a person" option on any menu you show.

Handover mechanics are covered in handing a chat from bot to human.

Start here

If you want the shortest path to something working today, read how to build your first WhatsApp automation, which walks one flow end to end without assuming you have built anything before. If you would rather understand the pieces first, every automation step, explained is the reference.