WhatsApp Broadcast Message Templates for Marketing Campaigns
EXCERPT: Copy-ready WhatsApp broadcast templates for promotions, restocks, and abandoned carts — written to get approved fast and keep your quality rating healthy.
WhatsApp broadcast templates need Meta approval before you can send them, and poorly written ones get rejected or, worse, approved but ignored. These templates are structured to pass approval quickly and actually earn a reply or click. Below are the three core ecommerce templates, then the rules that decide whether they get approved, opened, and answered.
Template 1: Promotion / discount
"Hi {{name}}, {{discount}}% off {{category}} until {{end_date}}. Shop now: {{link}}. Reply STOP to opt out."
Keep the offer specific (a number, not "big savings") and always include an opt-out line — Meta requires a clear way to unsubscribe from marketing templates.
Template 2: Back-in-stock alert
"Hi {{name}}, {{product}} is back in stock! Grab yours before it sells out again: {{link}}."
Restock alerts route to customers who already showed intent, so they typically outperform cold promotions on click-through — segment your list to only those who requested or viewed the item.
Template 3: Abandoned cart recovery
"Hi {{name}}, you left {{item}} in your cart. Complete your order in the next {{hours}} hours and get free shipping: {{link}}."
A small, time-boxed incentive (free shipping, not always a discount) tends to convert better than a bare reminder, without training buyers to expect a discount every time they abandon a cart.
Why do WhatsApp marketing templates get rejected?
WhatsApp marketing templates get rejected for two broad reasons: category problems and formatting problems. Every template is submitted under a category — marketing, utility, or authentication — and Meta's reviewers check that the content matches it. A "utility" template that actually pitches a discount gets rejected or reclassified as marketing, which changes how it's billed and reviewed. Formatting rejections come from the placeholders themselves: variables must be sequential ({{1}}, {{2}}, {{3}} with nothing skipped), can't sit at the very start or end of the message body without surrounding text, and can't make up so much of the template that reviewers can't tell what the message says. Templates that are mostly variables read as an attempt to smuggle arbitrary content past review, and reviewers treat them that way. The caveat: approval is automated first and human second, so a borderline template may pass today and get flagged later once real sends generate reports.
Beyond category and placeholders, the recurring triggers are spam-styled copy (all caps, stacked emojis, urgency spam words), missing opt-out language, and vague or misleading claims. If a rejection seems opaque, simplify: one offer, one link, one call-to-action, plain sentence case, opt-out at the end. Resubmitting a cleaned-up version is usually faster than appealing.
Which personalization variables actually lift reply rate?
Not all placeholders pull equal weight. The variables that lift replies and clicks are the ones that prove the message is about this customer, not a blast:
- {{name}} — table stakes. It stops the message reading like spam, but on its own it no longer signals real personalization.
- {{product}} / {{item}} — the strongest lever above. Naming the exact product someone viewed, requested, or abandoned is what makes Templates 2 and 3 outperform generic promotions.
- {{end_date}} / {{hours}} — a concrete, truthful deadline. Real scarcity ("until Thursday") beats vague urgency ("limited time"), and is less likely to trip review.
- A numeric {{discount}} — a specific number is checkable; "huge savings" is neither.
- Order or category context — referencing what someone actually bought or browsed signals a relationship, not a purchased list.
The rule of thumb: every variable should answer "why is this message for me, now?" If your platform supports custom attributes, pipe in behavioral data (last product viewed, last order category) rather than just contact fields — the marketing and broadcasting tools we track differ mainly in how much of this data they let you inject.
Opt-out handling is a requirement, not a courtesy
Meta requires marketing templates to give recipients a clear way to stop receiving messages. Practically, that means:
- Include the opt-out line in the template itself ("Reply STOP to opt out"), as in Template 1.
- Actually process the reply — a STOP keyword no automation catches is a compliance gap and a block magnet. Wire it to your suppression list, or use a platform from our best WhatsApp automation tools roundup that handles it natively.
- Suppress immediately and permanently. Sending "one last campaign" to someone who opted out is the fastest route to blocks and reports.
- Treat blocks as opt-outs too, and remove them from every segment.
A visible opt-out also helps deliverability: recipients who know they can leave with one reply are less likely to hit "block" — and blocks hurt your number far more than unsubscribes do.
How often should you broadcast without hurting your quality rating?
There is no single safe frequency — the honest answer is that your sending limit is a feedback loop, not a fixed quota. WhatsApp assigns each business number a quality rating driven by recipient behavior: blocks, reports, and silence push it down; replies and clicks hold it up. When the rating drops, Meta can throttle your messaging tier, cutting how many unique customers you can reach in 24 hours. The mechanism means frequency capping is self-enforced risk management: each additional campaign to the same audience raises the odds that marginal recipients block you, and one bad blast can shrink the ceiling for every future send. A practical cap for most ecommerce lists is one marketing broadcast per contact per week, tightened or loosened based on your own block and reply data. The caveat: transactional and utility messages (order updates, COD confirmations) sit outside this budget — customers rarely resent messages about their own orders.
Platforms differ in how much protection they give you here — some enforce per-contact frequency caps and quiet hours automatically, others leave it to you. Our best WhatsApp broadcast tools guide covers which handle throttling and suppression well.
Timing and segmentation: send less, to fewer people
The counterintuitive discipline of WhatsApp marketing is that smaller sends perform better:
- Segment by intent, not demographics. Template 2 to people who asked for a restock alert will always beat Template 1 to your whole list. Recency of interaction is the strongest signal you have.
- Respect local hours. A promotion at 11 pm reads as intrusive in a way email doesn't. For GCC audiences, avoid prayer times and note that weekends (Friday–Saturday in most Gulf markets) differ from Western defaults.
- Stagger large sends. One burst concentrates any negative reaction into a single window — exactly what quality-rating algorithms watch for. Spread big campaigns over hours or days.
- Exclude recent purchasers from promotions. Nothing invites a block like a discount code sent to someone who paid full price yesterday.
Real segmentation and per-contact frequency control effectively require the WhatsApp Business API — the app's broadcast lists cap out fast and offer no analytics. Our API vs App comparison walks through the cutoff point.
How to A/B test broadcast copy
Because templates are pre-approved, A/B testing on WhatsApp means testing between approved templates, not editing copy on the fly:
- Submit two variants of the same template — for example, Template 3 with free shipping versus a variant leading with the deadline. Each needs separate approval.
- Split one segment randomly (most broadcast platforms can do this; otherwise split the list yourself).
- Send both variants in the same time window so timing doesn't contaminate the result.
- Compare on replies and clicks, not delivery — and watch blocks per variant: a version that wins clicks but draws more blocks is costing you future reach.
- Retire the loser, then test the next element — incentive, deadline, opening line, or CTA phrasing — one at a time. Testing several things at once on typical list sizes just produces noise.
Turning templates into follow-up sequences
A short, capped sequence converts the fence-sitters a single broadcast misses. Build sequences from the templates above:
Restock sequence (from Template 2):
- Day 0 — the restock alert as written: "Hi {{name}}, {{product}} is back in stock! Grab yours before it sells out again: {{link}}."
- Day 2, non-clickers only — a reminder variant: "Hi {{name}}, {{product}} is still available, but stock is moving. Reserve yours: {{link}}."
- Day 4, still no click — last chance, then stop: "Hi {{name}}, last units of {{product}} — after this we can't promise availability: {{link}}. Reply STOP to opt out."
Cart sequence (from Template 3): the time-boxed free-shipping message, then one final nudge as the window closes — never a third. Anyone who ignored two cart messages has decided.
Three rules keep sequences safe: each step targets only people who didn't act on the previous one, every step's template is separately approved, and the sequence ends — no perpetual drips. If you sell cash-on-delivery, the same logic applies to confirmation flows; see our COD confirmation message templates.
Getting templates approved fast
- Avoid excessive emojis, all-caps, or urgency spam words — these trigger manual review.
- Always include a clear opt-out instruction for marketing templates.
- Use variables ({{name}}, {{link}}) rather than hardcoding — Meta reviews the template structure, not each personalized send.
- Keep one clear call-to-action per template rather than stacking multiple asks.
- Submit under the correct category (marketing, not utility) — miscategorization is a common silent rejection cause.
- Keep placeholders sequential and surrounded by static text, so reviewers can read what the message says.
Protecting your quality rating
Every broadcast affects your number's quality rating — low engagement (blocks, reports, no replies) can throttle how many messages you're allowed to send next. Segment tightly, only message people who opted in, and space out campaigns rather than sending everything at once. For the platforms that handle this well, see our best WhatsApp broadcast tools guide.
Frequently Asked Questions
Do WhatsApp broadcast templates need Meta approval?
Yes. Any template message sent outside the 24-hour customer service window — which includes essentially all marketing broadcasts — must be submitted and approved by Meta before use. Approval is usually fast if the template avoids spam-like language, is submitted under the correct category, and includes an opt-out. Each variant you want to A/B test needs its own approval.
What makes a WhatsApp broadcast template get rejected?
Excessive emojis or all-caps, missing opt-out instructions on marketing content, vague or misleading claims, and templates with multiple unrelated calls-to-action are common rejection reasons. So are formatting issues: non-sequential placeholders, variables at the very start or end of the message, or templates that are mostly variables with little fixed text. Keep templates specific, single-purpose, and compliant, and resubmit a simplified version rather than appealing.
How do I avoid hurting my WhatsApp quality rating with broadcasts?
Only send to opted-in contacts, segment by relevance rather than blasting your full list, honor unsubscribes and blocks immediately, and avoid sending multiple campaigns in quick succession. Quality rating is driven by recipient engagement — blocks and reports in particular — not just delivery volume, so a smaller, better-targeted send protects your messaging tier better than a big blast.
Can I edit an approved WhatsApp template?
No — approved templates are locked. To change the copy, submit a new template (or a new version, where your platform supports versioning) and wait for approval. This is why A/B testing on WhatsApp means pre-approving multiple variants up front rather than tweaking copy mid-campaign.
How many messages should a follow-up sequence contain?
Two to three at most, and each step should only go to contacts who didn't act on the previous message. A restock flow of alert, reminder, and last-chance is the practical ceiling; cart recovery should stop at two. Longer drips on WhatsApp read as harassment, drive blocks, and damage the quality rating that governs your sending limits.