Vishal Singhal 
A WhatsApp blast message is one approved template message sent to many people who opted in to hear from you, through the official WhatsApp Business Platform (the API). To send one, you need a number on the API, an approved marketing or utility template, a segment of opted-in contacts, and a send that fits your messaging limit. Meta charges per delivered template, and some messages can still fail because of per-user limits Meta applies across all businesses.
Last updated: 6 November 2026. Platform rules below were checked against Meta’s current documentation.
People also call this WhatsApp blasting or a WhatsApp broadcast campaign. This guide covers the official way to do it. It does not cover browser extensions, “blaster” apps or tools that promise sending without blocks: WhatsApp’s Business Messaging Policy says it can limit or remove access for businesses messaging people at scale in an unauthorized manner. For a wider walkthrough of large sends in India, see our guide to sending bulk WhatsApp messages in India.
What a WhatsApp blast message is
On the API, a blast is a business-initiated message. WhatsApp’s policy says that outside the 24-hour customer service window you can only send approved message templates, so every blast is a template: a fixed message with variables (name, order, offer), optional media and buttons, approved by Meta in a category. Promotions and announcements are marketing templates. Order, booking and account updates the person expects are utility templates.
The audience has to be opted in. Meta’s opt-in guidance asks businesses to state clearly that the person is opting in to messages, name the business they will hear from, and follow applicable law. A spreadsheet of numbers from an old event or a purchased list is not opt-in.
What changes at scale is everything around the message: who gets it, how many go out per day, who answers the replies, and what happens to the people Meta does not deliver to. That last part is where most teams get surprised.
How to send a WhatsApp blast message: step by step
- Put your number on the WhatsApp Business Platform. Blasts run through the API, usually via a provider. If you are still setting this up, follow our WhatsApp Business API setup guide first.
- Check your messaging limit. Meta caps how many unique people you can message outside a customer service window in a moving 24-hour period. New business portfolios start at 250, and verifying the business is one path to 2,000. The limit is shared by every number in the portfolio, so adding a second number does not add capacity. Our post on the WhatsApp message limit per day covers how it rises.
- Build the audience from consent, not from the contact list. Start with people who opted in to this kind of message, then remove opt-outs, recent complainers and anyone who just bought what you are about to promote. Our guides to WhatsApp opt-in automation and WhatsApp suppression lists go deeper.
- Write and submit the template. One message, one action, the business name up front and an easy way to stop marketing messages. Pick the category that matches the real purpose, not the one you hope is charged less. Template personalization covers variables that break when data is missing.
- Test on real phones. Send to a few internal numbers. Check every variable, link, button and image, and that replies land in the inbox your team watches. A WhatsApp campaign QA checklist helps here.
- Send to your most engaged segment first. Early feedback decides how Meta treats the rest of the send (see the next section), so the first recipients should be the people most likely to read and reply.
- Watch failures and replies, then widen. Look at failed statuses by error code, opt-outs and replies before releasing the next segment.
Why part of a blast fails even when you did everything right
Most guides stop at “get opt-in and an approved template”. Then the campaign report shows a block of failed messages to people who did opt in. Two Meta mechanisms cause most of this, and neither is a ban.
Per-user marketing limits. Meta may limit how many marketing templates a person receives from any business in a given period, based on that person’s recent marketing read rate and how much they already get. It counts messages from all businesses combined, not just yours. When it blocks your message, the webhook reports a failed status with error 131049, and Meta asks you to wait at least 24 hours before resending. Resending straight away to the same people repeats the failure.
Template pacing. For marketing templates, Meta sends normally up to a threshold, then holds the rest while early recipients react. Good feedback releases the held messages. If feedback pushes the template to low quality, Meta pauses it and drops every held message with error 132015. A blast that opens with your least engaged contacts can lose its own second half.
The practical change: treat 131049 failures as an audience for another channel, not a retry list. If the offer matters, send those people the email version the same day, and keep them out of the next WhatsApp send for at least a day. And order the send by engagement, recent buyers and recent repliers first, so pacing works for you. Our post on WhatsApp frequency capping covers how often to message the same person.
| What stops a blast message | Set by | What you see | What to do |
|---|---|---|---|
| Messaging limit | Meta, per business portfolio | Sends beyond the limit don’t go out that day | Split the audience across days or raise the limit |
| Per-user marketing limit | Meta, per recipient, across all businesses | Failed status, error 131049 | Wait 24 hours or switch that person to email |
| Template pacing | Meta, per marketing template | Held messages; if quality drops, error 132015 | Send to engaged contacts first; fix the template |
| Blocks and reports | Recipients | Quality rating falls; sending capacity can be limited | Tighten the audience and the promise at opt-in |
What a WhatsApp blast costs
Meta charges per delivered template message. The rate depends on the template category and the recipient’s country calling code, and Meta publishes the current rates on its WhatsApp pricing page. A person who reaches you from a Click to WhatsApp ad opens a free entry point window that can stay open for up to 7 days, during which Meta does not charge for messages to them. Replies inside the 24-hour customer service window are service messages, and each number gets 1,000 free service messages a month.
Providers bill in different ways. Some charge one all-in rate and pay Meta themselves; others, CampaignHQ included, have you pay Meta directly and bill their plan separately. Whichever model your provider uses, budget on delivered messages, and remember that a failed 131049 message is not a delivered one. For India specifics, see WhatsApp Business API pricing in India.
What to measure after a blast
| Layer | What to track | What it tells you |
|---|---|---|
| Delivery | Sent, delivered, read, failed by error code | Whether Meta delivered it, and why not when it didn’t |
| Conversation | Replies, support requests, opt-outs | Whether the message was welcome and what work it created |
| Traffic | Clicks, landing-page sessions | Whether people took the next step |
| Business result | Orders, bookings, renewals, registrations | Whether the campaign did its job |
| Quality | Blocks, reports, template quality and status | Whether the next blast will reach as many people |
Tag every send with a campaign ID that follows the contact through replies, clicks and purchases. Without that, a blast looks good on reads and nobody can say whether it sold anything.
Where CampaignHQ fits
This is CampaignHQ’s blog, so here is how our product handles it. CampaignHQ runs WhatsApp broadcast campaigns on the official WhatsApp Business API, built by a Meta Business Partner, with email and SMS on the same contact database.
- Template creation with Meta approval tracking, and personalization from contact attributes.
- Segments with include and exclude rules, and suppression of recently contacted people.
- Images, video, documents and carousel templates, with scheduling.
- Sent, delivered, read and clicked in one view.
- Large sends paced to your Meta messaging limit: CampaignHQ reads the limit, sends up to it on day one and schedules the rest, and emails you when Meta changes the limit or your quality rating.
- Replies land in a shared team inbox, and journeys can follow up by email or SMS.
Frequently asked questions
What is a WhatsApp blast message?
It is one approved template message sent to many opted-in contacts through the WhatsApp Business Platform. Outside the 24-hour customer service window, WhatsApp only allows approved templates, so every blast message is a template.
How do I blast a WhatsApp message to many contacts?
Get your number on the WhatsApp Business API through a provider, get a marketing or utility template approved, build a segment of people who opted in, test it on real phones, then send in batches that fit your messaging limit, most engaged contacts first.
Is a WhatsApp blaster app safe to use?
Tools that send through a personal or Business app account, rotate numbers or promise sending “without block” work against WhatsApp’s policy, which lets WhatsApp limit or remove access for unauthorized messaging at scale. The official API with opted-in contacts is the route that holds up.
How many people can I send a WhatsApp blast to?
As many as your messaging limit allows in a moving 24-hour period. New business portfolios start at 250 unique people outside customer service windows, and the limit rises to 2,000 and beyond as you verify the business and keep quality high. Larger lists go out across several days.
Why did some of my WhatsApp blast messages fail?
Error 131049 means Meta held back a marketing template because that person already gets many marketing messages or rarely reads them. Wait at least 24 hours before resending, or reach them by email. Error 132015 means the template was paused for low quality and held messages were dropped.
Official sources
- Meta for Developers: Get opt-in for WhatsApp
- WhatsApp Business Messaging Policy
- Meta for Developers: Messaging limits
- Meta for Developers: Per-user marketing template message limits
- Meta for Developers: Template pacing
- Meta for Developers: Pricing on the WhatsApp Business Platform
Written by CampaignHQ Team
