WhatsApp bulk messaging is permitted, profitable, and widely misunderstood. The confusion is worth clearing up, because the tools most businesses reach for first are the ones that get the number banned.
Meta does not object to scale. It objects to unsolicited messages and to software it has not authorised. Those are different problems with different solutions, and conflating them is why so many businesses lose a WhatsApp number they had built a customer base on.
Key Takeaways
- Two official routes exist: Business App broadcast lists and the Business Platform API.
- Broadcast lists cap at 256 contacts who must have saved your number.
- Business-initiated messages require opt-in and a Meta-approved template.
- Pricing moved to per delivered message on 1 July 2025, with no free marketing tier.
- Third-party bulk senders and browser extensions are the fastest route to a ban.
The Two Routes That Are Actually Allowed
Everything else is a variation on one of these or a violation.
Broadcast lists in the WhatsApp Business App. Free, and limited in ways that matter. A list holds up to 256 contacts, and recipients only receive the message if they have saved your number in their phone. That second condition eliminates most cold outreach by design. There is no scheduling, no automation and no campaign reporting. For a bakery messaging regulars about fresh stock, it is entirely adequate.
The WhatsApp Business Platform. The official API, built for scale, and the only compliant route past a few hundred recipients. Business-initiated messages must use templates submitted to Meta and approved in one of three categories: marketing, utility or authentication. Recipients must have opted in. Once a customer messages you, a 24-hour customer service window opens in which you can reply freely without templates.
The template approval step is the part businesses resent and the part that makes the channel work. It is why WhatsApp inboxes have not become the promotional wasteland that email became.
Why Third-Party Bulk Senders Fail
Browser extensions, modified WhatsApp clients and desktop bulk-sender software all work the same way: they automate a personal or Business App account rather than connecting through the API. That is unauthorised automation, and detection is not difficult, because the sending pattern does not resemble a human using a phone.
The consequences arrive faster than with most platforms. Spam reports and blocks from recipients feed directly into enforcement, and a number can be restricted or permanently banned within a short window. There is no meaningful appeal route, because the tool operated outside the system that would otherwise document your compliance.
Worth being blunt about the marketing claim attached to these tools. Software cannot make unsolicited bulk messaging compliant, because the compliance question is about consent and authorisation, not about the interface used to send. A tool that promises both scale and compliance without an API connection and an opt-in record is promising something it does not control.
Opt-In Is the Whole Game
A phone number in your CRM is not permission. This is the single most expensive misunderstanding in the category.
Meta requires an affirmative action from the customer before you initiate contact: a ticked box, a submitted form, a keyword, a QR scan, or the customer messaging you first. Pre-checked boxes and consent buried in bundled terms do not qualify. Since November 2024 Meta’s platform policy has accepted a general marketing opt-in that does not name WhatsApp specifically, which loosened the rule considerably.
Platform policy and data protection law are separate rulebooks, and satisfying one does not satisfy the other. Under UK PECR, marketing by electronic mail to a corporate body does not require prior consent, but the ICO’s business-to-business guidance treats sole traders and many partnerships as individual subscribers who do require consent or a valid soft opt-in. UK and EU GDPR apply on top wherever the recipient is identifiable, and consent there must be specific and informed, which generally means naming WhatsApp as a channel in your privacy notice.
Keep the evidence rather than the assurance. The same principle governs any consent-dependent channel, as it does with real-time call routing and consent records: when a complaint arrives, what matters is what you can produce.
What It Actually Costs
The claim that WhatsApp bulk messaging is cheaper than other channels needs updating, because the billing model changed.
On 1 July 2025, Meta replaced conversation-based pricing with per-message pricing. Under the old model, a 24-hour conversation window carried one charge regardless of how many templates you sent inside it. Now each delivered template message is billed individually.
The current pricing documentation sets out the categories. Marketing templates are charged on every delivery, with no free allowance and no volume discount. Utility templates are free when sent inside an open customer service window and charged outside it. Authentication templates are charged per delivery. Service messages, meaning free-form replies inside the 24-hour window a customer opened, are free.
Two consequences follow. Broadcasting a promotion to fifty thousand contacts is a fifty-thousand-message charge at the marketing rate, which is a real budget line rather than a rounding error. And correctly categorising transactional messages as utility rather than marketing is worth auditing, because the rates differ substantially and misclassified order confirmations quietly cost multiples of what they should.
Quality Rating Decides How Far You Scale
The mechanism most bulk-messaging advice omits entirely. Meta assigns a quality rating based on recipient feedback, principally blocks and reports, and that rating governs your messaging limits.
Send relevant messages to people who asked for them and limits rise. Send frequent promotional templates to a purchased list and blocks accumulate, the rating drops, limits contract, and eventually the number is restricted. The system is self-correcting in a way that punishes volume for its own sake, which is why the strategy of maximising send count is structurally wrong on this channel.
Segmentation is not a nicety here. It is the mechanism that protects the asset. Sending to unengaged contacts at fixed intervals looks like automated behaviour even when the content is legitimate, and the same discipline applies as in any other outbound programme built on collected contact data.
Reading the Metrics Honestly
Vendor material for this category routinely promises open rates and real-time analytics. WhatsApp reports sent, delivered and read receipts, plus template performance and quality signals through the Business Platform. That is genuinely useful and it is not the same as email open tracking, which works by a different mechanism entirely.
Read receipts also depend on the recipient having them enabled, so a read rate is a floor rather than a measurement. Treat replies and conversions as the real signal, since those are unambiguous and they are what the channel is actually good at.
Conclusion
WhatsApp rewards businesses that treat it as a permission channel and removes the ones that treat it as a broadcast channel. The rules are published, the routes are documented, and the pricing is on a public rate card.
Collect opt-in you can evidence, connect through the Business Platform if you need scale, categorise templates correctly, and watch the quality rating rather than the send count. The tools promising to skip those steps are not offering a shortcut. They are offering to spend an asset you cannot easily rebuild.
Read Next
- Facebook Engagement in 2026: What Meta Rewards and What It Quietly Demotes
- How to Avoid a TikTok Ban: What Actually Triggers Enforcement
- Personal Branding on Social Media: What Actually Builds Authority
