Sending the same update to 50 customers one chat at a time is a task nobody has time for, and it is also completely unnecessary. WhatsApp Broadcast delivers one message to many contacts simultaneously. Each recipient experiences it as a private, individual chat rather than a group thread everyone can see.
This guide covers exactly how to send a WhatsApp broadcast on Android, iOS, and the Business App. It also covers what changes on the Business API, how to avoid account restrictions, and terms businesses often confuse with broadcast.
What Is WhatsApp Broadcast?
WhatsApp Broadcast sends a single message to multiple contacts at once, with each recipient receiving it as a standalone private chat. No recipient sees who else is on the list, and any reply goes back to you privately rather than into a shared thread. This is the core feature that makes broadcast fundamentally different from a group chat, where every member sees every message and every reply.
For a small business with a handful of loyal customers, this distinction might seem academic. But the moment a contact list grows past a few dozen people, that distinction stops being academic. A private, personal-feeling message and a visible group announcement start to create a real difference in how customers experience the business. Individually valued versus one name on a list nobody bothered to separate out.
The mechanism works the same way on the standard WhatsApp app and the WhatsApp Business app, with one hard constraint. Recipients must have your number saved in their address book, or the message never arrives, silently, with no error notification on your end. For the fuller comparison between broadcast and other one-to-many options on WhatsApp, see our guide to WhatsApp broadcast vs group messaging. Our dedicated guide to broadcasting WhatsApp messages step by step covers the same setup process with additional detail for teams managing multiple lists.
How to Send a WhatsApp Broadcast on Android
The steps below work on both the standard WhatsApp app and the WhatsApp Business app for Android.
1. Open the Three-Dot Menu
From the Chats tab, tap the three vertical dots in the top-right corner of the screen.
2. Select New Broadcast
Choose New Broadcast from the dropdown menu that appears. This opens your full contact list.
3. Select Your Recipients
Choose up to 256 contacts to include. Only contacts who have saved your number will actually receive the message once it sends.
4. Confirm and Create the List
Tap the confirmation checkmark. The broadcast list is created and appears in your Chats screen. It is typically marked with a broadcast icon so it is easy to distinguish from a regular chat or group.
5. Write and Send Your Message
Type your message as you would in any normal chat, attach images or documents if needed, and tap send. The message delivers to every recipient on the list as an individual, private chat.
How to Send a WhatsApp Broadcast on iOS
The iPhone flow follows the same logic with slightly different menu labels.
1. Open Broadcast Lists
From the Chats page, tap Broadcast Lists in the top-left corner.
2. Create a New List
Tap New List, then select the contacts you want to include, up to 256 per list, following the same saved-number requirement as Android.
3. Compose and Send
Type your message, add any media if relevant, and tap Send. The message goes out to every recipient as a separate private chat, exactly as it does on Android.
What Changes on the WhatsApp Business API
Sending broadcast through the free app works for small, engaged contact lists, but it hits real limits quickly once a business grows past that scale.
1. No 256-Contact Ceiling
The WhatsApp Business API removes the per-list contact cap entirely. Sending volume instead scales through a tiered daily limit. It starts at 1,000 unique recipients per day and rises to unlimited at the highest tier, based on account quality.
2. No Saved-Number Requirement
Recipients do not need to have your business number saved for a broadcast to deliver through the API, provided they have given documented opt-in consent. This alone removes the single biggest source of silent, unexplained delivery failure on the free app.
3. Scheduling, Personalization, and Delivery Analytics
The API supports scheduled sends, dynamic message variables for personalization, and per-recipient delivery, read, and click data. None of this exists on the free app at any list size. Our guide to how to get WhatsApp Business API covers the requirements and application process for businesses ready to make that move. For businesses wanting a specific send time rather than immediate delivery, our guide to scheduling WhatsApp messages covers how that works.
How to Send a WhatsApp Broadcast Through the Business API
Once access to the Business API is set up through a BSP such as Qiscus, sending an actual broadcast follows a different process. More structured than the native app’s three-tap flow. Here is what that looks like in practice through the Qiscus platform.
1. Prepare Your Message Template
Every broadcast sent through the API needs a pre-approved template. Log in to your dashboard, navigate to Outbound Messages, then select WhatsApp Broadcast Template. If an approved template already exists, select it. If not, create a new one with a name, category, language, header, body, footer, and any buttons, then submit it for Meta’s review.
2. Build Your Audience Segment
Go to Outbound Messages and choose whether to broadcast to a saved customer list or a customer group. Apply filters to segment by purchase history, location, engagement level, or customer tag if relevant. Only contacts with documented opt-in are eligible for delivery, and the platform enforces this automatically rather than leaving it to manual checking.
3. Configure the Broadcast
Select your approved template, then set the delivery time and timezone. For businesses with audiences spread across regions, timezone-adjusted delivery ensures the message lands at the right local time for each segment. Not all at once regardless of time zone.
4. Review and Schedule
Check the audience count, template preview, and delivery settings before confirming. Once scheduled, the platform delivers the broadcast server-side at the specified time. No device needs to stay online, and no team member needs to be available at the moment it sends.
5. Monitor Delivery and Engagement
After the broadcast goes out, check the Analytics section for sent, delivered, and read counts. Any failed deliveries show up here too, along with the reason for each failure. This is the step that closes the loop the native app never offers. A single send becomes a data point that improves the next campaign.
Is Sending a WhatsApp Broadcast Free?
Cost depends entirely on which platform is sending the broadcast.
1. The Free App Costs Nothing to Use
Broadcasting through the standard WhatsApp app or the WhatsApp Business app carries no charge from Meta. This applies regardless of how many broadcast lists you create or how often you send.
2. The Business API Carries Per-Message Charges
Once a business moves to the API, Meta applies per-message pricing based on category and destination country. The Business Solution Provider handling platform access typically adds a separate fee. Our guide to WhatsApp marketing strategy covers how to plan campaign spend around this cost structure.
3. Free Does Not Mean Unlimited
Even on the free app, sending too frequently or to too many non-opted-in contacts risks a temporary or permanent restriction. That carries a much higher cost than any API fee in lost account access and lost customer relationships.
Sending WhatsApp Broadcasts Without Getting Blocked
WhatsApp actively monitors broadcast behavior for patterns that resemble spam, and a handful of practices consistently protect an account from restriction.
1. Only Message Contacts Who Expect to Hear From You
Sending to purchased, scraped, or cold contact lists triggers reports and blocks quickly. A broadcast list built from customers who have already interacted with the business performs better and carries far less risk.
2. Space Out Sends Rather Than Blasting Repeatedly
Sending the same or similar message to multiple lists in rapid succession looks statistically identical to spam behavior, regardless of intent. Spacing sends out, and varying content across different segments, protects the account’s standing.
3. Respect the Native App’s Practical Limits
Based on existing research, Meta has been rolling out a separate monthly frequency limit on broadcast sends for free app accounts. This is beyond the 256-contact cap. This limit is still being tested and expanded gradually rather than applied uniformly. Treat it as an active constraint to watch, not a fixed number to plan around indefinitely.
4. Move to the API Before Volume Becomes a Problem
Businesses that wait until an account restriction forces the move to the API lose messaging capability during the transition. Moving proactively, once a contact list has clearly outgrown what the free app can handle, avoids that disruption entirely.
Sending to Multiple People Without Using Broadcast
Some businesses reach for manual workarounds before discovering broadcast exists. Understanding why these alternatives fall short clarifies why broadcast is worth the small setup effort.
1. Forwarding a Message to Multiple Chats
Forwarding lets you send the same message to several existing chats one at a time, tapping through each conversation individually. Recipients see a Forwarded label on the message, which reads as less personal than a direct broadcast. The process does not scale past a handful of contacts before it becomes as slow as typing each message fresh.
2. Copying and Pasting Text Into Each Chat
Manually copying text and pasting it into one chat after another avoids the Forwarded label but introduces its own risk. Typos, missed recipients, and the sheer time cost make this the least efficient option of the three. It is useful only for a true handful of contacts on a rare occasion.
3. Why Both Fall Short of Broadcast
Neither forwarding nor copy-paste offers any way to track who received the message. Both require the same manual repetition broadcast was specifically built to eliminate. For any list beyond five or six contacts, setting up an actual broadcast list takes less total time than either workaround. It also gives each recipient a clean message rather than a visibly forwarded one.
WhatsApp Broadcast vs Other Channels
Broadcast is one of several ways to message multiple people on WhatsApp, and businesses often confuse it with terms that describe something different.
| Method | How It Works | Contact Limit | Personalization |
| Broadcast, native app | Private message to each recipient on a list | 256 per list | None |
| Broadcast via Business API | Private message to each recipient, sent through the API | Tiered, from 1,000 per day up | Yes, dynamic variables |
| Forwarding a message | Manually forward one message to multiple chats individually | No formal limit, but manual | None, and recipients see it is a forward |
| Copy and paste | Manually copy text into each chat | No formal limit, but slow and error-prone | Manual only |
| WhatsApp Group | Shared chat where every member sees every message | Up to 1,024 members | None, shared context |
Forwarding and copy-paste are the two workarounds businesses reach for when they do not yet understand broadcast exists. Both are dramatically less efficient than even the free app’s broadcast feature. The term WhatsApp Blast is often used interchangeably with broadcast sent through the API specifically, though it is not an official Meta term. It describes the same underlying mechanism, personalized, high-volume messaging through the Business API, rather than a separate product.
WhatsApp Channels are worth mentioning as a sixth option, even though the table above focuses on true one-to-many messaging alternatives. A Channel is a public, follow-able profile where only the admin posts, with no reply option and an unlimited follower count. It solves a genuinely different problem than broadcast, building public reach and brand presence rather than delivering a personalized message to a known, opted-in list. Businesses trying to decide between the two should ask whether the content needs a reply to be useful. If it does, broadcast is the right tool. If it does not, and the goal is reach at zero cost, a Channel fits better.
Choosing the right method ultimately comes down to three questions worth asking before sending anything. First, does the recipient expect or need the ability to reply. Second, how many people need to receive the message, and will that number grow meaningfully over time. Third, does the content need to look personalized, or is an identical message across the whole list acceptable. A small, stable, engaged contact list with no need for replies might genuinely be served well by the free app’s broadcast feature indefinitely. A list that is growing, needs personalization, or generates enough replies to require tracking has already outgrown what the free app was built to handle.
Common Mistakes That Weaken Broadcast Performance
Beyond the account restriction risks already covered, a handful of avoidable errors quietly reduce how well a broadcast actually performs even when it delivers successfully.
1. Sending Identical Content to an Entire List Regardless of Relevance
A broadcast to loyal repeat customers and a broadcast to first-time leads rarely need the same message. Segmenting the list, even into two or three groups based on purchase history, produces noticeably better response rates than one generic message sent to everyone.
2. Ignoring Replies That Come Back
Broadcast recipients on the native app can and do reply. Those replies land in a normal one-on-one chat that is easy to lose track of without active monitoring. A reply left unanswered for days undoes much of the goodwill a well-timed broadcast built in the first place.
3. Sending at a Time That Ignores the Audience’s Schedule
A broadcast sent at 2am local time waits in an inbox until the recipient wakes up. By then, a time-sensitive offer may have lost its relevance. Based on existing research, evening hours and lunch breaks tend to produce stronger engagement than very early morning or late-night sends for most consumer audiences.
4. Treating Every Message as Promotional
A broadcast list used exclusively for sales pushes trains recipients to ignore messages from that number over time. Mixing in genuinely useful, non-promotional content, order updates, helpful tips, seasonal reminders, keeps the list responsive to the promotional messages when they do arrive.
How Qiscus Helps You Send WhatsApp Broadcasts at Scale
Qiscus is an official WhatsApp Business Solution Provider that removes the native app’s constraints on broadcast entirely.
1. Broadcast Beyond the 256-Contact Cap
WhatsApp Broadcast through Qiscus runs on the Business API. There is no per-list ceiling and no saved-number requirement, and opt-in and template compliance are handled automatically.
2. Segmented, Personalized Campaigns
Contact segmentation and dynamic message variables let a broadcast to thousands of contacts feel as targeted as one sent to a handful. No identical generic text regardless of who receives it.
3. Delivery Data the Free App Never Provides
Every broadcast sent through Qiscus reports delivery rate, read rate, and click data per campaign. That gives a business the performance visibility the native app has never offered at any list size.
Citranet increased conversation traffic 3x after moving to WhatsApp Business API through Qiscus. That result depended on removing exactly the contact and frequency ceilings this guide has covered, not working around them with risky manual workarounds.
Send Once, Reach Many, Without the Manual Work
WhatsApp Broadcast turns a task that would take an hour of individual messages into a single send. Understanding the mechanism, the saved-number requirement, and the 256-contact cap prevents most of the frustration businesses run into on their first attempt.
The free app is a genuinely good starting point for a small, engaged contact list. The moment that list outgrows 256 contacts, or needs scheduling, personalization, or delivery data, the Business API is the correct next step. Not a workaround to avoid.
That decision does not need to happen all at once either. Many businesses run the free app’s broadcast feature for their smallest, most stable segment. They move their largest or fastest-growing list to the API first, then migrate the rest once the initial setup has proven out. Treating the move as gradual and deliberate, rather than an all-or-nothing switch, tends to produce a smoother transition than businesses expect going in.
Explore official WhatsApp Business API access built for the broadcast volume the free app was never designed to handle at scale.
Frequently Asked Questions
The questions below cover what businesses ask most often when sending their first WhatsApp broadcast.
Yes, on the standard WhatsApp app and the WhatsApp Business app. If a recipient has not saved your number, the broadcast message does not deliver, with no error notification shown. The WhatsApp Business API removes this requirement, delivering to opted-in contacts regardless of whether they have saved the number.
Yes, on the free app, regardless of list size or how often you send. Costs only apply once a business moves to the WhatsApp Business API. That carries Meta’s per-message charges plus a platform fee from the Business Solution Provider.
Forwarding the same message individually or copying and pasting text into each conversation are the two manual workarounds. Both are slow, error-prone, and show recipients the message was forwarded. The practical solution for genuinely large audiences is the WhatsApp Business API, which removes the 256-contact limit entirely.
Blast is not an official Meta term. It is the phrase many vendors and businesses use to describe broadcast messaging sent through the WhatsApp Business API specifically. This is different from the native app’s broadcast list feature. Both describe the same underlying one-to-many private messaging mechanism, just at different scales and through different infrastructure.
The most common cause is that those contacts have not saved your phone number in their address book. On the native app, a broadcast only delivers to recipients who have you saved as a contact. The message is silently dropped for anyone who has not, with no error shown.
