WhatsApp Reminder Message: How to Automate One

A reminder reacts to something that happened. A scheduled message goes out at a time you picked. That difference decides which tool you reach for: if the moment depends on the customer, you want a reminder; if it depends on the calendar, you want a scheduled send.

In a shop, most useful reminders are the second kind of thing dressed up as the first: a shipping update, a subscription charge three days out, a consumable that is due to run out, a review request once the parcel has landed. None of those have a fixed date. They have a customer-specific date, which is why they have to be automated rather than diarised.

That is exactly how the Delay block behaves. Each contact waits the same duration, but their clock starts when they reach the block. Somebody who buys on Tuesday and somebody who buys on Friday both wait three days, and each moves on three days after their own arrival. There is no batch and no shared send window, so several customers sit at different points of the same reminder at the same time.

A reminder needs one block that selects, one that waits and one that sends. Build them in that order.

1. Pick the trigger in the Starting point. Five events are on offer: Contact purchase and Abandoned checkout come from Shopify, Smart activation and Webhook come from Keaz, and Chat-in fires when the customer writes to you first. The trigger is the only required field, and it decides which filters are even meaningful.
2. Narrow who enters, if you need to. Labels and filters cover contact type, opt-in level, order count and order value, product name, category, type and tag, customer country, and email and SMS consent. Every condition has to be true at the same time, so a long list is a narrow reminder rather than a thorough one.
3. Set the wait. The Delay block has two fields, a number and a unit of minutes, hours or days. That pair covers a fifteen-minute gap and a four-month gap equally well, and you can chain several Delays to build a sequence that spaces itself.
4. Write the message, attach a discount code in the Starting point if you want the revenue attributed to this reminder rather than to your shop in general, and activate the Flow.

A long reminder is invisible while it works, because nothing sends. The Delay block prints Clients currently waiting on the canvas for that reason: a rising count means the reminder is running, and a flat zero on a Flow that should be filling up is the first thing to check when a flow does not seem to be firing.

Start with the reminders where the customer is already waiting for news, because those need no persuading. The pre-written Keaz flow templates ship with the timings below already set, so treat them as a starting position rather than a blank canvas.

• Shipping status — sent the moment the order ships, with the tracking link. The message everyone opens.
• Subscription renewal — three days before the next charge, with skip, swap and pause. It prevents a refund ticket rather than chasing a sale.
• Abandoned cart — fifteen minutes after the checkout was left, while the decision is still warm.
• Re-order — timed to the product's own consumption cycle, so a coffee subscription and a face serum get different waits.
• Review request — seven days after fulfilment, once the customer has actually used the thing.
• Winback — 120 days without an order. One Delay block, not a note in someone's calendar.

Two of these are reminders about an order and four are reminders about a habit. The habit ones compound, which is why they repay the setup time: turning one order into three works through how far apart to space them. If you want the arithmetic for your own catalogue before you build anything, the Forecast runs it on your customer count and vertical.

Every template you send outside an open conversation is sorted by Meta into one of three categories: marketing, utility or authentication. Reminders live on the line between the first two, and which side they land on is a pricing decision, not a wording preference.

To count as utility, Meta's guidelines require a template to clear two bars at once: it has to be non-promotional, and it has to be either specific to the customer or genuinely essential to them. Meta's own utility examples include a parcel update with a tracking number and a payment reminder naming the date and the card on file. Its marketing examples include "you left items in your cart" and a subscription notice that adds a discount — and the guidelines state that retargeting is marketing even when the customer asked for it (Meta, WhatsApp Business Platform template categorization guidelines, retrieved 2026-09-03).

The practical consequence is narrow and expensive. Mixed content counts as marketing, so a shipping reminder with a promo code bolted on is a marketing template. For German numbers, Meta's rate card prices utility templates well below marketing ones (Meta pricing documentation, retrieved 2026-09-02). The discount code you add to a parcel update therefore changes the unit cost of every one of those messages, forever, and reminders are the highest-volume thing you will ever send.

What a reminder costs also depends on whether it lands inside or outside an open conversation window, and that part of the rate card changes on 1 October 2026. What changes on 1 October has the detail, and it is worth reading before you plan a reminder programme around today's numbers.

• Attaching an offer to a utility reminder. The parcel update was cheap; the parcel update with 10% off is a marketing template. If you want to sell, send a second message rather than editing the first.
• Assuming "they asked for it" makes it utility. It does not. Retargeting stays marketing in Meta's guidelines even when the customer requested it, and a cart reminder is retargeting.
• Not planning for recategorisation. Meta re-checks live templates and can move a utility template to marketing with one day's notice, instantly if the account has already been warned about miscategorisation, with 60 days to appeal. Businesses that keep filing marketing as utility face escalating restrictions, up to every utility template on the account being recategorised (Meta template categorization guidelines, retrieved 2026-09-03).
• Stacking filters until nobody qualifies. Labels and filters are combined with AND, not OR. Add one condition at a time and watch the entry count.
• Setting a delay longer than the offer. Before a long wait, ask two questions: will the customer remember the order, and will the discount code still be valid?
• Reading silence as failure. A 120-day reminder sends nothing for four months. Check Clients currently waiting before rebuilding anything.
• Reminding people who never opted in. A reminder is still a marketing message under German law when it carries an offer. Opt-in has to be explicit, documented and revocable, and the Starting point's opt-in-level filter is where you enforce it — see collecting opt-ins the compliant way.

This is a summary rather than legal advice — have your own counsel review your opt-in wording.