🤖 Automations & Chatbots

How many WhatsApp automations should a store actually run?

The store that automates everything ends up muted, losing the order updates along with the offers.

A frequency budget is a deliberate cap on how many messages one customer receives from you across all your flows in a given period. Most stores do not have one, which is how a single customer ends up receiving an order confirmation, a shipping update, a review request and a cart reminder inside one week.

The failure that follows is worse than it looks. A customer who mutes or blocks you does not lose only your marketing — they lose the delivery notification too, and you lose the channel entirely for that person.

Start with five flows, not fifteen

For a store under roughly 500 orders a month, this set covers the ground:

FlowMessages per customerCategoryCost
Stop the bot when a human replies0Free
After-hours reply0–1 per visitServiceFree
Order confirmation with buttons1 per orderUtilityCharged once, then free
Shipping and tracking1 per orderUtilityFree inside the window
"Where is my order?"Only when askedServiceFree

Four of the five cost nothing to run, because they happen inside an open conversation window — which Meta's pricing documentation confirms has been free and unlimited for service conversations since 1 November 2024.

Then add carefully

Each addition should have to justify itself against a specific number: how many extra messages does this put in front of one person?

The arithmetic that should worry you

A customer who orders twice a month from a store running everything above receives, in a month: 2 order confirmations, 2 shipping updates, 2 review requests, possibly 2 cart reminders, and however many campaigns you sent. That is comfortably into double figures for someone who simply likes your products.

Now consider that Meta's per-user marketing cap is shared across all businesses and tightens for recipients who appear unreceptive — with no published number. You are not budgeting against your own sends. You are budgeting against everyone's.

Three rules that keep it sane

  1. One marketing message per customer per week, maximum. Set it as a per-contact frequency cap under Broadcasts → Opt-outs so it is enforced rather than remembered.
  2. Never let two flows fire for the same event. Two order-placed automations mean two confirmations. Before publishing, check what already triggers on that event.
  3. Prefer one flow with branches to three flows with conditions. Three separate keyword automations for returns, refunds and exchanges can all match one message. One flow with three branches cannot.

The collision to check for. A customer abandons a checkout, then completes the order twenty minutes later. If your cart reminder is on a one-hour delay and nothing stops it, they get a "you left something behind" message about an order they already placed. Use a Has the Customer Replied? branch, or target the reminder at people who did not convert.

Prefer utility over marketing wherever possible

This is the strategic version of the frequency argument. Utility messages are free inside the window, exempt from per-user marketing caps, deliverable to US numbers, and welcomed rather than tolerated. Marketing is charged, capped, regionally blocked and resented.

So the highest-return move is usually not adding a marketing flow — it is making an existing utility flow earn a reply, which opens the window and lets you say anything for free. That argument is developed in the 24-hour window.

How to tell you have gone too far

The first and third are leading indicators; by the time you are seeing 131049 you have been over-sending for a while.

An honest default

If you want a rule of thumb rather than a framework: run every utility flow you can, and one marketing flow at a time. Utility messages buy goodwill and cost nothing. Marketing spends both. A store that gets this ratio right can automate almost all its customer communication and still be welcome in the chat.

Frequently asked questions

How many WhatsApp automations should a small store run?

Four or five is plenty under about 500 orders a month, and four of them should be utility or service flows that cost nothing. Add marketing flows one at a time.

How often can I message a customer on WhatsApp?

Meta publishes no per-user number, and its cap is adaptive and shared across all businesses. A practical self-imposed limit is one marketing message per customer per week, enforced with a per-contact frequency cap.

What happens if two automations trigger on the same event?

Both run, and the customer gets two messages. Check what already triggers on an event before publishing a second flow for it.

How do I know I am over-messaging?

Quality rating moving off green, rising opt-outs, falling reply rates on transactional messages, and error 131049 on campaigns. The first three are leading indicators.