Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

CRM & Marketing Automation › Automation Workflows

SMS and WhatsApp Automation

How to automate SMS and WhatsApp messaging: consent and opt-out rules, message templates and approvals, suitable use cases, and timing and frequency.
Guideintermediate13 min readUpdated

Where messaging fits

Messaging is the most intrusive owned channel a marketer has. Email waits in an inbox; a text or a WhatsApp message lights up a phone, and people treat the channel as personal. That gives it a role email cannot play — reaching someone in the minutes that matter — and it sets a cost on misuse that email does not carry: a block, a spam report or a complaint to a regulator.

The right mental model is that messaging is for moments, not for content. An order is on its way, a booking is tomorrow, a cart was left with a discount about to expire, a reply is needed to proceed. In each case the person benefits from being interrupted. A newsletter, a product announcement or a nurture step does not meet that bar and belongs in email, where the lifecycle marketing guide places most retention communication.

Within the automation stack, messaging is an action a workflow can take, with its own consent condition at the gate. It is not a separate programme with its own list. The same CRM record, the same suppression rules and the same frequency governance apply, and the workflows hub shows where the messaging action sits among the others.

Three documents set the rules this guide follows. Meta's WhatsApp Business Platform documentation describes what a business must do to message people on WhatsApp. The CTIA's messaging principles and best practices describe how the US messaging industry expects senders to obtain consent and handle opt-outs. The UK Information Commissioner's Office direct marketing guidance explains how UK law applies to electronic marketing messages, a category its guidance says includes text messages and other electronic messages. Other jurisdictions have their own rules; these three are cited because they are published, specific and widely used as a baseline.

RequirementWhatsApp Business Platform (Meta)CTIA principles (US industry)ICO direct marketing guidance (UK)
Consent before messagingOpt-in required before business-initiated messages; the opt-in must make clear the person is agreeing to receive messages from the named business on WhatsAppConsent expected before marketing messages, with the level of consent rising from conversational to informational to promotional contentConsent generally required for marketing to individuals by electronic mail, with a documented "soft opt-in" exception for existing customers under stated conditions
What the opt-in must sayThe business name and that messages will arrive over WhatsAppProgramme description, expected message frequency, that message and data rates may apply, and how to opt out and get helpClear, specific and informed, with a positive action by the person; records of when and how consent was given
Opt-outHonour requests to stop and make opting out straightforward; blocks and reports affect the account's quality rating and messaging limitsSupport STOP and similar keywords, acknowledge the opt-out, and stop sendingEvery message must identify the sender and give a simple way to opt out; stop once the person objects
Sender identificationAn approved display name and business profileClear sender identification; registered numbers and codes rather than disguised sourcesSender identity must not be concealed; contact details must be provided
Content restrictionsBusiness messaging policies and template categories govern what may be sentUnlawful content prohibited; restricted categories require age and consent safeguardsContent must match what the person consented to

Two practical consequences follow. First, consent is per channel. A person who gave an email address on a form has not agreed to texts, and a phone number collected for delivery updates is not a marketing opt-in; the ICO guidance is explicit that consent must be specific, and the list building and consent guide covers the same principle for email. Record the channel, the wording shown, the date and the source for every opt-in, because the day a complaint arrives is the day that record matters.

Second, opt-out must be universal and automatic. The STOP keyword and its common variants must work on every sending number, confirmation of the opt-out should be sent as the CTIA principles describe, and the resulting flag must suppress the person from every workflow that could message them, not just the one they replied to. A workflow that reads consent at entry and never again will keep sending to someone who opted out mid-sequence. Before each text or WhatsApp send, the mobile message send QA checklist checks consent, opt-out, templates and timing in one pass.

Templates and approvals

WhatsApp separates two kinds of message. When a person writes to the business, Meta's documentation describes a customer service window during which the business can reply with free-form messages. Outside that window, anything the business initiates must use a message template that Meta has reviewed and approved in advance. Templates are declared in a category — Meta's documentation lists marketing, utility and authentication among them — and the category affects how the template is reviewed, how messages are charged and what content is acceptable. Meta documents how template messages are charged by category on its pricing pages; the figures change and are not reproduced here.

The approval process shapes how automated flows are built. Every business-initiated step is a template with fixed text and named placeholders, so the copy is written once and approved before the workflow can use it. Placeholders are for the person's name, order number, date and similar details, not for swapping in a different message; Meta's template guidelines say a template can be rejected when its placeholders could be used to send content that differs from what was approved, and approved templates can be paused when their quality rating falls. Meta ties that rating to user feedback such as blocks and reports. A marketing flow therefore needs a template library managed like any other asset: versioned, with the category recorded, the approval date noted and a fallback when a template is paused.

SMS has no central approval body in the same sense, but it has its own gates. In the US, the CTIA principles describe registration of the sending number or code and the programme it carries, and carriers filter traffic that looks unregistered or non-compliant. Elsewhere, sender-ID registration rules vary by country. The practical discipline is the same as for WhatsApp: a small set of approved message texts, each tied to a use case and a consent level, rather than free-form copy composed inside each workflow.

Approval inside the organisation matters as much as approval by the platform. Because a message cannot be unsent and reaches people instantly, a messaging template deserves the same change control the governance guide sets out for workflows, with legal or compliance sign-off for anything promotional in a new market.

Use cases that suit messaging

The test for a messaging use case is whether the person would rather know now than later. Where the answer is clearly yes, messaging earns its interruption; where it is no, the same content belongs in email.

Transactional and service messages pass the test easily: order confirmations, dispatch and delivery updates, appointment reminders and reschedule links, booking confirmations, payment failures, account security codes. These are typically utility or authentication templates on WhatsApp and informational messages in the CTIA's terms, and they are the foundation of a messaging programme because they establish the channel as useful before anything promotional arrives.

Time-bound commercial moments can pass it: an abandoned cart with a reservation about to lapse, a price drop on a saved item, a limited-availability restock, a renewal due in days. The abandoned cart flows guide designs the email version; the messaging step is a single, well-timed addition for people who opted in, not a parallel sequence.

Two-way service passes it when a reply is needed: confirming a delivery slot, answering a pre-sale question, collecting a document, rebooking. WhatsApp's conversational model suits this; SMS can do it with keyword replies.

What fails the test: newsletters, content promotion, general nurture steps, surveys that could wait, and anything sent because the channel exists rather than because the moment demands it. Each of these raises opt-outs and blocks, and on WhatsApp those feed the quality rating that governs the whole account.

A useful discipline is to write, for each messaging use case, the sentence the person would say if asked why they got the message. "Because my parcel is arriving" and "because my cart expires tonight" are answers; "because they wanted me to read a blog post" is not. For app push, the same sentence is the first step in the tutorial on writing push notifications, which builds the wording from that trigger outwards.

Timing, frequency and quiet hours

Messaging timing is stricter than email timing for the same reason the channel is effective: the message arrives now. Three rules cover most cases.

Send in the recipient's local time. A workflow that fires on an event will fire at all hours; a delivery update at any hour is tolerable, a promotion at night is not. Store the person's time zone, or infer it from the country code and address, and hold promotional sends until a daytime window. Quiet hours are set by law in some jurisdictions and by courtesy in others; none of the sources in this guide fixes a universal window, so the practical rule is to send promotional messages during the recipient's waking and working hours and to let the legal review for each market set the hard limits.

Cap frequency across the channel, not per workflow. The CTIA principles expect the frequency disclosed at opt-in to be honoured, and WhatsApp's quality rating responds to how people react to volume. A person in a cart flow, a renewal flow and a restock alert can receive several messages in a week from workflows that each look restrained. A channel-level cap, enforced as a condition before every promotional send, is the only reliable control. Transactional messages are usually exempt from the cap, which is one reason to classify them correctly. When customers are already complaining that they hear from the business too much across texts, email and the app, the diagnosis for customers getting too many marketing messages rebuilds one person's messages from every sending tool to find which cap or rule was missing.

Respect the moment. A message sent within minutes of the trigger is expected; the same message a day later is a surprise. Workflows that batch messaging sends into a daily run lose most of what the channel offers. If a step cannot be sent promptly and inside the daytime window, it is usually better to drop it than to send it late.

Promotional messaging also needs a stop rule beyond opt-out. People who have not replied, clicked or bought after several promotional messages should drop to transactional-only, because continued sending to an unresponsive contact is how blocks accumulate.

Two-way and conversational flows

Both channels can carry replies, and a flow that invites them has to handle them. On SMS, replies are text and the workflow usually interprets keywords: a confirmation word, a reschedule word, a question that routes to a person. On WhatsApp, Meta's documentation describes interactive message types with buttons and lists, which make the person's choices unambiguous, and a reply opens the customer service window in which free-form messages are allowed.

Design a conversational flow as a short tree with a human exit at every branch. The expected replies map to actions: confirm, cancel, choose a slot, ask for help. Anything unrecognised routes to a person, with the conversation history attached, and the automated steps pause until that person has replied. The worst conversational experience is a bot that repeats its menu at a person who has asked a real question, and the second worst is a question that nobody ever answers.

Reply handling also has a consent dimension. A STOP or equivalent reply must always be recognised ahead of any other keyword logic. A HELP reply, as the CTIA principles describe, should return the programme's identity, contact details and how to opt out. And a reply to a transactional message is not a marketing opt-in: a person confirming a delivery slot has not agreed to promotions, however convenient the thread.

Staffing is the usual failure. A two-way flow launched without agreed cover for the human branches generates unanswered conversations within days. Agree who monitors the inbox, during which hours, with what response expectation, and build the flow so that outside those hours the automated reply says when a person will respond. When the conversations start from Meta ads rather than from the business's own messages, the guide to click-to-message ads applies the same reply tree and staffing rules to a paid campaign and counts the conversations through to paying customers.

Measurement

Messaging is measured by outcomes and by the health of the channel, and the second matters as much as the first because losing the channel loses every future outcome.

Outcome metrics follow the use case. For a transactional flow, the measure is operational: deliveries confirmed, appointments kept, payments recovered. For a commercial flow, it is the conversion rate (CVR) of recipients to the action the message asked for, measured against a holdout who received the email step only, so that the messaging step is credited with what it added rather than with the whole conversion. Click-through (CTR) on message links is a diagnostic for copy and timing, not the KPI.

Channel-health metrics are the ones to watch weekly. Opt-out rate per message and per use case, blocks and reports on WhatsApp as reflected in the quality rating Meta documents, delivery failures and carrier filtering on SMS, and reply volume reaching humans. A rise in opt-outs after a particular template is the earliest signal that a use case has failed the "would they rather know now" test, and it should trigger a review before the quality rating does it for you.

Report messaging alongside email rather than separately. The question a lifecycle team needs answered is what each channel added at each moment, and that is only visible when the flows are measured as one system with shared holdouts.

Illustrative example — not a real result

Adding a WhatsApp step to a renewal flow

A subscription box company adds a WhatsApp utility template to its renewal flow for the 4,300 customers who opted in to WhatsApp at checkout. The template reads "Hi [first name], your [plan] renews on [date]. Reply 1 to keep it or 2 to change your box." and was approved in the utility category 8 days before launch. Sends are held to between 9am and 7pm in the customer's time zone, and the step is skipped for anyone who has already confirmed by email. In the first month 2,100 customers receive the message, 980 reply, 112 change their box and 61 replies are free-text questions routed to the support inbox, where the agreed cover is weekdays until 8pm. Opt-outs total 14. A 10% holdout that received only the email reminder shows a lower confirmation count in the same window, so the step is kept, and the free-text volume prompts a third button, "Ask a question", in the next template version.

When the goal is keeping customers, SMS and messaging for retention sets service-first tactics and a budget decided message by message against opt-outs and incremental margin.

Common mistakes

  • Reusing email consent for messaging. The person agreed to one channel and got another.
  • Consent checked once. The workflow reads the opt-in at entry and keeps sending after a STOP mid-sequence.
  • Templates written per workflow. Dozens of near-duplicate messages, none versioned, several paused.
  • Promotional content in a utility template. Rejected on review, or paused after reports, with the whole account's rating at stake.
  • Event-triggered sends at any hour. A cart reminder in the middle of the night.
  • Frequency judged per flow. Each workflow is restrained; the phone is not.
  • A two-way flow with nobody on the other end. Questions go unanswered and the channel's trust is spent.
  • Measuring clicks instead of channel health. The campaign looks fine until the number is filtered.

Frequently asked questions

Can email consent be reused for SMS or WhatsApp?

Treat each channel's consent as separate. The regulatory guidance cited here expects consent to be specific to what the person agreed to, and both the CTIA principles and WhatsApp's documentation describe an opt-in that names the channel and the sender. A tick box for email does not tell you the person wants messages on their phone, and sending anyway is the fastest route to blocks and complaints.

Why was a WhatsApp template rejected or paused?

Meta reviews templates against its documented policies before approval and can pause or reject them afterwards based on quality signals such as blocks and reports. Common causes are content that does not match the declared category, placeholders used to send a different message from the one approved, and marketing content sent to people who did not opt in. Read the rejection reason in the platform and fix the template rather than resubmitting variants.

Is a WhatsApp or SMS flow a replacement for email automation?

No. Messaging suits short, timely, high-value touches where the person expects them; email carries detail, long-form content and lower-stakes communication. The best flows use both, with messaging reserved for the few moments where immediacy earns the interruption, and the frequency across both channels governed together.

Terms used on this page

Where this page is used

Also related

Sources

  1. WhatsApp Business Platform documentation — Meta for Developers
  2. CTIA messaging principles and best practices — CTIA
  3. Direct marketing guidance — Information Commissioner's Office (UK)

Related