WhatsApp broadcasts have open rates that make email look ancient. In our own sends we routinely see 80-95% of messages opened, often within minutes, against the 20-30% you fight for in a good email program. That is exactly why broadcasts are dangerous: the same reach that drives conversions also makes WhatsApp ruthless about spam. Get the mechanics wrong and you do not merely underperform โ you tank your number's quality rating, get your daily limit throttled, and in the worst case lose the number entirely.
We run broadcast campaigns in our testing lab across the WhatsApp Business Platform, sending through multiple Business Solution Providers (BSPs) to compare approval behaviour, deliverability and the speed at which a number's quality slips when you push it. This is the playbook that survives contact with WhatsApp's enforcement. None of it is theory โ every rule below is something we have watched bite a real number.
First, get the definition straight
There are two completely different things people call a "WhatsApp broadcast", and confusing them wastes weeks.
- The consumer app's Broadcast Lists. Limited to your own saved contacts, capped at a few hundred recipients, and only delivered to people who already have your number saved in their phone. Fine for a yoga teacher messaging 40 regulars; useless at any real scale and impossible to automate.
- The WhatsApp Business Platform (the API). True bulk messaging through a BSP, sent as pre-approved message templates. This is what every serious campaign uses, and everything below is about this path.
If you are reading "broadcast campaign that converts," you mean the API path. The rest of this guide assumes it.
How we evaluate broadcast setups
Before the playbook, a quick note on methodology so you can weigh our claims. When we test a broadcast stack we score it on the things that actually decide whether a campaign converts or gets a number restricted:
- Opt-in hygiene โ can the tool record source, timestamp and consent text per contact?
- Template lifecycle โ how fast templates get approved, and whether the tool surfaces rejection reasons and category changes.
- Quality-rating visibility โ does it expose the green/yellow/red rating and messaging tier, or do you find out you are throttled only when sends fail?
- Segmentation and throttling โ can you ramp volume and target tight segments, or is it one-blast-fits-all?
- Reply handling โ once a recipient replies, does the same tool let you actually have the conversation inside the 24-hour window?
We send identical campaigns to matched, consenting test segments and watch the numbers over a 30-day window. The chart below summarises how the broadcast-capable categories we test stack up on those axes.
The takeaway: the cheap unofficial "blaster" tools that promise bulk WhatsApp without the API are the trap quadrant. They cut the corners โ opt-in, quality monitoring, template compliance โ that exist specifically to keep your number alive.
Step 1: Get real opt-in (this is non-negotiable)
WhatsApp requires explicit opt-in before you message anyone. Not implied, not "they bought from us once," not "they are an email subscriber." The user must have actively agreed to receive WhatsApp messages from your business, and you should record when, where and how they opted in. WhatsApp's own Business Messaging Policy makes this the foundation, and BSPs increasingly ask you to evidence it.
Good opt-in sources we have seen perform:
- A checkbox at checkout that is unchecked by default and explicitly says WhatsApp, not a generic "marketing" toggle.
- A click-to-WhatsApp ad where the user initiated the chat themselves.
- A keyword opt-in ("text JOIN to...") with a clear description of what they will receive and how often.
- A QR code or web widget where the user types the first message.
Bad ideas that get you reported: scraping numbers, importing a cold purchased list, or assuming email subscribers want WhatsApp. The report-to-block rate on cold lists is brutal โ in our tests, blocks on a poorly-consented segment ran an order of magnitude above a clean one โ and WhatsApp weights user blocks heavily in your rating. If you are building qualification flows on top of opt-in, our guide to qualifying leads automatically in DMs covers how to do it without burning consent.
Step 2: Build templates that get approved
You cannot send free-form marketing to a cold contact. Outside the 24-hour customer service window, every message must be a pre-approved template. Templates come in categories โ broadly marketing, utility, and authentication โ and the category affects both approval strictness and pricing under WhatsApp's conversation-based pricing model.
To get approved fast and stay approved:
- Be specific and transparent. "Hi {{1}}, your order {{2}} shipped and arrives {{3}}" sails through. "Hey!! ๐ค BIG news inside ๐" gets flagged.
- Use variables correctly and don't stuff them. Templates with floating, context-free variables ("{{1}} {{2}} {{3}}") get rejected because reviewers can't verify what they expand to.
- Match the category to the content. Sending a promo under a utility template to dodge marketing pricing is a fast way to get the template re-categorised and your account penalised. WhatsApp now auto-categorises and will silently reclassify a mislabelled template.
- Avoid making promises about WhatsApp itself, excessive emoji, all-caps, or URL shorteners that look like phishing.
Approval usually lands within minutes to a day. Keep two or three approved variants live at all times so a single rejection never blocks a launch. If you are deciding whether to lean on rigid templates or a more conversational AI layer once the reply comes in, our breakdown of a flow builder vs an AI agent for DMs is worth a read before you commit your stack.
Step 3: Respect the 24-hour window
This is the single most misunderstood rule on the platform. Once a user messages you, you have a 24-hour customer service window in which you can send free-form, non-template replies. Outside that window, you are back to templates only.
This shapes campaign design more than anything else. A good broadcast template's real job is often to restart a conversation โ to earn a reply that re-opens the 24-hour window so you can then talk naturally, send media, and actually sell. We design the first template around a single clear question or CTA that makes replying easy, not around cramming the whole offer into one approved block.
Step 4: Protect your quality rating
Every WhatsApp number carries a quality rating (green / yellow / red) and a messaging tier that caps how many unique users you can message in a rolling 24 hours. Blocks and "report spam" taps drag the rating down; sustained low quality drops your tier or restricts the number outright. The tiers escalate as you build a healthy track record:
| Messaging tier | Unique recipients / 24h | How you reach it |
|---|---|---|
| Unverified / new | ~250 | Default for a fresh number |
| Tier 1 | 1,000 | Verified business, quality holds |
| Tier 2 | 10,000 | Sustained volume + green/yellow quality |
| Tier 3 | 100,000 | Proven scale with healthy engagement |
| Tier 4 | Unlimited | Top tier, granted on continued good standing |
You climb tiers automatically by sending healthy volume at good quality; you fall when quality craters. The two things that most reliably wreck a rating in our tests are irrelevance and frequency. Here is how to keep the number green:
- Warm up. Never blast your full list from a brand-new number on day one. Ramp volume gradually so WhatsApp sees genuine engagement before scale. We model a conservative ramp below.
- Segment. Send relevant offers to relevant people. Irrelevance is the number one cause of blocks, full stop.
- Make opting out easy. Honour "STOP" and offer it explicitly. A clean unsubscribe beats a block every time, and it is blocks that hurt your rating.
- Watch the dashboard. If quality slips to yellow, slow down and audit your last few sends immediately โ do not wait for red.
The reckless line is not hypothetical. Push a cold number from 50 to several thousand sends overnight and WhatsApp's anti-spam systems read it exactly the way they are designed to โ as a spammer โ and clamp the number before you ever reach scale.
Step 5: Timing and cadence
| Factor | Guideline |
|---|---|
| Send time | Match the recipient's local working/waking hours; avoid late night and very early morning |
| Frequency | Err low โ weekly or event-driven beats daily blasting |
| Segmentation | Many smaller, relevant segments over one giant list |
| First send | Warm-up batch, then scale once quality holds green for several days |
| Re-engagement | Space out wins; a reply re-opens the free-form window, so build for replies |
Cadence is where most campaigns quietly die. WhatsApp is an intimate channel that lives next to messages from people's family and friends; recipients tolerate far fewer messages here than they would in email. One genuinely useful message a week consistently outperforms five promos that train people to mute, then block, then report you. If your real goal is a faster two-way conversation rather than one-way blasting, our notes on reducing response time in a social inbox and on multichannel inbox tools for small teams cover the handling side.
Step 6: Measure what actually matters
Open rate is vanity on WhatsApp โ almost everything gets opened, so it tells you nothing. Track instead:
- Reply rate โ did the template restart a conversation and re-open the 24-hour window?
- Click-through on any link or CTA button.
- Block/report rate โ your single most important early-warning system.
- Conversion attributed to the send, end to end.
If block rate climbs while reply rate falls, your targeting or frequency is wrong, and no amount of copy polish will save it. Fix the segment before you scale spend. WhatsApp does not broadcast in a vacuum either โ most programs we run pair it with SMS marketing automation for fallback reach and a website lead-capture chatbot feeding the opt-in list.
Choosing the tool to send through
You will send through a BSP either way; the question is what sits on top of it. The honest comparison comes down to how much campaign tooling, segmentation and reply handling you want versus how much you are willing to pay and learn. We map the broad categories below โ these are categories, not exact prices, because WhatsApp's per-conversation fees stack on top of any platform subscription and vary by country.
| Approach | Official API | Template tooling | Segmentation | Built-in inbox | Keeps number safe |
|---|---|---|---|---|---|
| โ Marketing-first platform | โ | โ | โ | โ | โ |
| Official BSP console | โ | โ | ~Basic | ~ | โ |
| CRM with WA add-on | โ | ~ | โ | โ | โ |
| Unofficial blaster | โ | โ | โ | โ | โ |
Two well-known marketing-first platforms worth evaluating directly are Wati and respond.io โ both sit on the official API, both handle templates, segmentation and a shared inbox. We have written full hands-on breakdowns in our Wati review and respond.io review, plus a head-to-head Wati vs respond.io for buyers stuck between the two. If your sending is e-commerce-driven, the Shopify-native angle is its own decision โ see Shopify WhatsApp marketing apps.
Whatever you pick, the rule is the same: use the official WhatsApp Business Platform. Unofficial "unlimited bulk" tools that automate the consumer app are the fastest way we know to get a number permanently banned, and they take your contact list down with it.
The short version
WhatsApp broadcasts convert because the channel is personal and permission-based. Your entire job is to protect both of those properties at once. Collect genuine opt-in and record it. Send approved templates that match their category. Respect the 24-hour window and design templates to earn a reply. Warm up the number on a gradual ramp, segment hard, keep cadence low, and watch your block rate like a hawk. Do that and you get email-crushing results from a channel people actually read. Skip it and you will spend more time appealing restrictions than selling โ and eventually you will be appealing a ban you cannot undo.