WhatsApp Business automation: consent and message templates

WhatsApp Business automation appeals to many SMBs because the channel is already there: your customers use it, they reply quickly, and a WhatsApp Business bot can absorb part of the repetitive workload. But this channel is governed by precise rules on consent, the service window and approved templates. This decision guide helps you choose what to automate, when, and at what cost, without making legal compliance promises on your behalf.

Why consent shapes your entire project

On WhatsApp, you are not on your own turf: you are writing into people's personal channel. The Meta policy, which you must verify, requires that you have obtained the person's consent before sending messages, and that you make it easy for them to stop. This is not a copywriting detail: it is the condition that determines whether your automation is a relationship or spam.

Concretely, consent is collected when the person gives you their phone number: a contact form, a separate checkbox for WhatsApp, an exchange in your shop. It must be specific to the channel. A customer who left their email for an invoice has not consented to receive commercial follow-ups on WhatsApp. If you automate without making that distinction, you are building on sand: recipient reports can lead to a restriction on your number, and a blocked number wipes out the whole automation effort.

Opting out must be as easy as opting in. Provide a stop keyword your bot recognises (for example "STOP"), processed immediately, and mention this option in your first messages. A poorly handled opt-out is the most common warning sign before enforcement.

The 24-hour service window: the rule that changes your architecture

The WhatsApp Business Platform works with a 24-hour service window: when a customer sends you a message, that action reopens a window during which you can reply freely, including with ordinary automated messages. After that delay, you can only write to them using templates approved by Meta, under declared categories.

This rule has a direct architectural consequence: your automation must distinguish two regimes. Replies within the window (acknowledgements, questions, follow-up in an exchange) belong to a classic conversational flow. Out-of-window sends (appointment reminders, availability notifications, follow-ups) require templates submitted for approval, with content matching the declared category. If you design your WhatsApp Business bot without this separation, you will discover the problem when the first message is rejected.

Also check compliance, permission and channel opt-out in the WhatsApp Business policy before fixing your scenarios: these rules evolve, and what was acceptable last year may no longer be.

Marketing versus utility: two logics, two levels of rigour

Not all messages are equal. A utility message answers an expectation the person has: order confirmation, appointment reminder, information they asked for. A marketing message starts the approach: promotion, new offer, commercial follow-up. The policy and template categories distinguish these uses, and so should you.

For marketing, the consent bar is higher and recipient tolerance lower. A commercial follow-up sent out-of-window to someone who has not replied in weeks is the riskiest scenario on the whole channel: a template with uncertain acceptance, a disengaged recipient, a high blocking risk. If you automate that case, limit it, pace it, and monitor reports.

For utility messages, the question is different: the person expects the message. That is where WhatsApp Business automation delivers the best effort-to-benefit ratio, because it replaces a manual task (calling, sending an SMS, chasing) with an automatic send into a channel that is already open.

Pricing: per delivered message, by category and market

WhatsApp Business Platform pricing works per delivered message, with a price that depends on the message category and the market (the recipient's country). Not all messages are chargeable: replies within an open service window do not fall under the same regime as out-of-window templates. The old per-conversation pricing model is no longer the reference to use.

Before costing a project, check the official platform pricing for your actual markets and the relevant categories. One often-overlooked point: the price depends on the recipient's country, not yours. For example, an SMB working between Paris and Dakar will not pay the same price for a template delivered in each market; time zones also affect your scheduling, since a message scheduled at 10am in Paris does not arrive at the same local time depending on the date (on 20/10/2026, 10am in Paris corresponds to 8am in Dakar, while on 03/11/2026, 10am in Paris corresponds to 9am in Dakar, because of the clock change). Schedule your automated sends in the recipient's local time to avoid night-time notifications, which are bad for both experience and report rates.

Decision table: what to route through the bot

Situation	24h window open?	Message type	Recommended automation
The customer writes, an acknowledgement is needed	Yes	Ordinary message	Immediate automatic reply, then human routing if needed
Frequent question about a product	Yes	Ordinary message	Bot answer, with an accessible human handover
Appointment confirmation requested	Yes	Ordinary message	Automatic confirmation within the exchange
Appointment reminder the day before	No	Utility template	Approved template, sent in the recipient's local time
Order-ready notification	No	Utility template	Approved template triggered by your internal tool
Follow-up on a quote with no reply	No	Marketing template	Limit it: explicit consent, controlled pacing, report monitoring
Reactivating a customer inactive for months	No	Marketing template	Not advised without recent, clear consent

This table is not a universal rule: it is a sorting grid. The underlying principle is simple — the further a message drifts from an explicit expectation of the recipient, the stronger the consent must be and the more the send needs justifying.

Appointment confirmation versus commercial follow-up: two cases not to confuse

Take the most favourable case: appointment confirmation. The customer booked a slot and expects a confirmation. Your automation sends a utility template the day before, in local time, with a simple option to confirm or reschedule. Consent was collected for the channel at booking time, the message is expected, and the pricing tier is the utility one. This is the best starting point for a first automation.

The reverse case: the commercial follow-up. A prospect received a quote three weeks ago and has not replied. Sending a marketing template "as a reminder" assumes explicit commercial consent, a template approved in the right category, and tolerance for the risk of being reported. It is not forbidden, but it is the scenario where automation yields the least and costs the most in risk. Our design recommendation: automate the utility side first, treat commercial follow-up as a manual or tightly controlled case, and measure before extending.

Minimising the data you pass to the bot

A WhatsApp Business bot does not need to know everything. Data minimisation is a data protection principle recalled by the CNIL and, above all, a design principle: the less personal data your automation handles, the smaller your risk surface.

In practice:

• Pass the bot only the fields the scenario needs: for an appointment reminder, the first name, date, time and a rescheduling link are enough.
• Avoid injecting sensitive data into templates: a short order number is more appropriate than a full address.
• Define a retention period for exchanges in your automation tool, and purge what no longer has a use.
• Log the consent itself: who consented, when, for which channel. It is your only defence if a send is disputed.

These points are design recommendations, not legal obligations or proof of compliance: for legal aspects, have your set-up reviewed by a qualified professional.

A seven-step implementation procedure

1. Map the messages you already send manually and classify them utility/marketing, inside/outside the 24h window.
2. Check your existing consents: identify contacts who explicitly accepted WhatsApp and those for whom you have nothing.
3. Prepare the number connection: the technical preparation of the number and its attachment to the platform is a step in its own right, detailed in our guide on creating a WhatsApp chatbot and preparing the number connection. Note that a simple QR code does not prove an official connection to the Business Platform.
4. Draft and submit your first templates: start with two or three utility templates, in the right categories, rather than a full catalogue.
5. Configure channel opt-out: a stop keyword processed immediately, a mention in the first message, effective exclusion from subsequent sends.
6. Schedule sends in the recipient's local time and check the applicable pricing by category and market.
7. Measure and adjust: reply rate, report rate, cost per delivered message. A rising report rate is the signal to slow down, not to send more.

Main commented example: a workshop automating its reminders

Take a hypothetical case, unrelated to any real client. A car repair shop uses WhatsApp to confirm appointments. Today, an employee sends the next day's reminders by hand every evening: about 20 messages, often forgotten on busy days.

The target automation: when an appointment is created in the workshop's calendar, a utility template is scheduled for 5pm the day before, in the customer's local time. The template contains the first name, date, time and two quick replies ("Confirm" / "Reschedule"). If the customer replies, the service window opens and the bot confirms or proposes a slot; if they ask for something else, the exchange is routed to a human. Consent was collected at booking time, with a separate checkbox for WhatsApp.

What makes this scenario work: the message is expected, the content is minimal, the opt-out is clear, and the cost per delivered message is that of a utility template in the relevant market. The same workshop considered adding a follow-up on unsigned quotes; after analysis, it chose to keep that manual, because the volume is low and the reporting risk is significant. That is exactly the kind of trade-off this guide invites you to make: automate what is expected, tightly control what is imposed.

Limits, common mistakes and what to do

Three mistakes come up regularly. The first: assuming a contact in your CRM equals WhatsApp consent. A stored number is not a permission. The second: designing scenarios that assume the 24h window will always be open, then discovering that night-time sends or long delays close it. The third: neglecting human handover. A bot that cannot pass the baton turns a simple question into frustration; our guide on the WhatsApp Business bot with menus, fields and human handover covers this point.

Another limit to know: per-delivered-message pricing varies by category and market, and Meta may change its rules. Do not build a business case on a frozen price; allow a margin and a periodic review. To go further on organising inbound requests, our article on WhatsApp AI agents to organise customer requests complements this guide, and our analysis of automated support costs helps you cost the whole picture. Finally, if your automation sits within a broader set-up, the question of agent permissions remains the same: our AI agent permissions checklist applies to the WhatsApp channel too.

If you would like to define a WhatsApp automation mission suited to your SMB, you can describe your need on Edeverse's offers page.

Frequently asked questions

Can you automate marketing messages on WhatsApp Business?

Yes, under strict conditions: the recipient's explicit commercial consent, a template approved in the marketing category, and acceptance of the reporting risk. It is the least recommended scenario to start with, because recipient tolerance is at its lowest there.

What happens if a customer does not reply for more than 24 hours?

The service window closes. You can then only send approved templates, in the category matching your message. Ordinary automated replies no longer go through until the customer writes to you again.

Does consent have to be written, or can it be verbal?

The WhatsApp policy requires clear permission for the channel, but the exact form depends on your context and your own obligations. Operationally, the safest option is a dated, channel-specific record, for instance a separate checkbox on a form. For legal validity, consult a professional.

Are all automated messages chargeable?

No. WhatsApp Business Platform pricing applies to delivered messages according to their category and the recipient's market, and not all messages fall under the same regime: exchanges within an open service window are not billed like out-of-window templates. Check the official prices for your markets.

Can a WhatsApp Business bot run without approved templates?

Yes, as long as it only replies to customer messages within an open service window. As soon as the bot must initiate contact — a reminder, a notification, a follow-up — an approved template becomes necessary. That is the distinction to build into your automation design from the start.