When to run this checklist
Run it before a marketing text, WhatsApp, push or in-app message is sent to a segment, and before a messaging step is switched on inside an automated flow. Run it again whenever the message's wording, audience, template or link changes, because each of those can quietly break a line that passed last time: a new segment can pull in people who gave a number for something else, a new template has to be approved, and a new link has to be tested.
The lifecycle or CRM marketer who owns the send runs the list, with the app team for push and in-app messages, and with whoever handles legal or compliance review for promotional templates in a new market.
Neighbouring lists take the other channels and stages. An email send goes through the email campaign QA checklist; a whole automated journey, including its email steps, entry and exit rules, goes through the email automation flow launch checklist, and this list covers the messaging steps inside it. The programme around the sends, from permission prompts to the monthly review, is run by the app marketing operations playbook. When a person asks to stop by any route other than the opt-out keyword or settings screen, the marketing opt-out request SOP handles it.
Before you start
- The segment or flow definition, with the consent field it reads for this channel.
- The consent records: the channel, the wording shown, the date and the source of each opt-in.
- The notification topics and how each sending tool enforces them.
- The message text or template, with its category and approval status where the channel needs one.
- The channel's frequency cap and priority order, and the email calendar for the same audience.
- The deep link or landing URL, its route table entry and the campaign naming convention.
- Test devices on each platform, including one with notification previews hidden.
- The holdout design, if the message will be judged on what it changed.
The checklist
The groups follow the order of the decision to send: may this person receive this message, can they stop it and see who sent it, is it the right time and the right volume, does the message say the right thing and lead to the right place, and has a person looked at it on a phone. A line that does not apply to the channel in front of you is marked not applicable, not skipped.
Consent and preferences
Opt-out and sender
Timing and frequency
Message and link
Preview and sign-off
Where each check is explained
The widget keeps the lines short so they can be ticked; the reasoning lives in the guides. Each check links to the page that explains it.
| Check | Explained in |
|---|---|
| Consent given for this channel, not borrowed from email | Consent and opt-out in the SMS and WhatsApp guide |
| Message type matches what the person agreed to | Consent and opt-out in the SMS and WhatsApp guide |
| Topic preferences honoured in the sending tool | Setting up notification preferences by topic |
| Transactional or promotional decided before capping | Setting up notification preferences by topic |
| Opt-out keyword works and is confirmed | Consent and opt-out in the SMS and WhatsApp guide |
| Opt-out suppresses the person from every flow | Consent and opt-out in the SMS and WhatsApp guide |
| Sender identified in every text and WhatsApp message | Consent and opt-out in the SMS and WhatsApp guide |
| Approved template for business-initiated WhatsApp messages | Templates and approvals in the SMS and WhatsApp guide |
| Promotions sent in local daytime hours | Timing, frequency and quiet hours |
| One frequency cap across the channel | Timing, frequency and quiet hours |
| Contact budget shared with email | Retention through SMS and messaging |
| Push timing rules checked before scheduling | Writing push notifications |
| Leads with what changed and names the thing | Writing push notifications |
| Offers labelled as offers | Writing push notifications |
| Deep link opened on each platform and lands as promised | Testing app deep links before a campaign |
| Links tagged by the campaign convention | UTM and naming conventions for analytics |
| In-app messages capped with push in one priority order | Designing in-app messages |
| Previewed on real devices and lock screens | Writing push notifications |
| Sign-off for promotional templates in a new market | Templates and approvals in the SMS and WhatsApp guide |
| Holdout kept where the effect will be judged | Push notifications and in-app messaging |
If an item fails
The consent and opt-out groups are the hard stops. The SMS and WhatsApp guide reads the ICO's direct marketing guidance as requiring consent that is specific, Meta's WhatsApp documentation as requiring an opt-in before business-initiated messages, and the CTIA principles as expecting opt-out keywords to work and be acknowledged. On that reading, a segment that includes anyone who gave a number for delivery updates, or who agreed to email only, is not sent until those people are removed. A stop keyword that does not work on the sending number, or an opt-out flag that only one workflow reads, stops every send from that number until it is fixed, because the next message would go to someone who has already said no. That is general direction from the guide, not legal advice; each market's legal review sets the rules there.
On push, the writing tutorial notes that Apple's App Store Review Guidelines say push must not be used for marketing unless the person has opted in to receive it. A promotional push aimed at everyone with notifications switched on fails the topic line and waits until the audience is limited to people who chose promotional messages. A missing WhatsApp template approval is also a stop: the message cannot be sent outside the customer service window without one, and there is no workaround worth taking.
Timing lines are fixed before scheduling rather than noted. Quiet hoursThe hours when promotional texts, WhatsApp messages and push notifications are held for the recipient's daytime, set by law in places and courtesy elsewhere. are set by each market's legal review and by courtesy where the law is silent, so a send held for the morning loses little, while a promotion at night loses the person. If the frequency cap is set per workflow rather than for the channel, or the email calendar already contacts the same people for the same reason, drop or merge the duplicate; the comparison of SMS and push explains why one message should not go out on both.
In the message group, a deep linkA link that opens a specific screen inside a mobile app rather than its home screen. that opens the home screen or a browser is the line most often found failing, and it fails silently: the campaign still reports taps. Fix the route and re-test on each platform before sending. The link's row in the route tableThe app's map from each deep link path to the screen it opens, including what happens for logged-out users, missing items and renamed screens. says which screen the tap should open, so it is the reference for that re-test. Wording that buries the change can usually be fixed in minutes with the inverted pyramid, conclusion first. Untagged links can ship with a note only if the platform's own reporting will be used instead, and the gap is recorded.
A message nobody has previewed on a phone does not go. A missing holdout is not a reason to stop a one-off send, but it is for a recurring message or a new flow step, because without one there is no way to tell whether the message changed anything; tap rates worked out with the CTR calculator describe attention, not effect. When people are already switching notifications off, the troubleshooting page on users turning off notifications locates the cause before more messages are added.
A coffee chain checks its app and text messages (illustrative)
A new-drink push and a loyalty text before a weekend launch
Toquavel Coffee, an invented coffee chain with 26 cafés and an ordering app, plans two messages for a Saturday drink launch: a push to app users and a text to loyalty members offering double points on the new drink. The CRM marketer runs the list on Wednesday with the app developer. The text fails the first consent line: the segment of 18,400 numbers was built from every loyalty account with a phone number, but 5,100 of those numbers were given only for order-ready updates at collection. The marketer rebuilds the segment from the marketing consent field for SMS, leaving 13,300 people, and the text gains the café brand as sender and a reply-STOP line that is tested on the sending number. The push fails the deep link line: on both platforms the tap opens the home screen rather than the new drink's page, because the route was added to the app's latest release and older versions do not know it. The developer adds a fallback to the menu screen for older versions, and both are re-tested on four phones, one with previews hidden, where the title "New: oat honey latte is on the menu" still reads in full. The push is limited to the promotions topic, scheduled for 10am local time, and counted against the shared cap, which pushes a lower-priority survey message to the following week. A random 10% of eligible app users are held out, and both messages go out on Saturday morning.
Common mistakes
- Consent borrowed from another channel. An email opt-in, or a number given for delivery updates, is not agreement to marketing texts.
- An opt-out that one flow obeys. The person replies stop to one message and keeps receiving the others; the suppression listA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints. has to reach every flow.
- Caps set per workflow. Each flow looks restrained and the phone is not.
- Promotions in a service wrapper. An offer written like an account update breaks trust and blurs what the person agreed to.
- Testing the link on one phone. The link works on the writer's device and opens a browser everywhere else.
- No preview where people read it. The title that looked fine in the sending tool is cut off on a lock screen.
- The same message on every channel. Text, push and email all carry the same reminder, and the person hears it three times.
- Judging the send on taps. Without a holdout, a message that changed nothing looks like a success.
The checklists library holds the lists that sit beside this one, from email campaign QA to the launch of an automated flow.
