A broadcast list in the app and a campaign on the business platform are entirely different mechanisms - in limits, requirements and what counts as spam. Which fits what.
Key takeaways
- In an app broadcast, the message only reaches people who saved your number.
- An app broadcast has a recipient cap; the platform has a tiered daily limit.
- On the platform, a business-initiated message requires a pre-approved template.
- What defines spam is not the volume but how many people block or report.
A broadcast list in the WhatsApp Business app and a campaign on the business platform sound like the same thing at two sizes, and they are in fact two different mechanisms: one only reaches people who saved your number and is capped in size, and the other requires approved templates and limits set by your quality rating.
The difference, row by row
| Dimension | App broadcast list | Platform campaign |
|---|---|---|
| Who receives | Only people who saved your number | Any number you loaded |
| Ceiling | A per-list recipient cap (256 in the app) | A tiered daily limit: 250 / 2,000 / 10,000 / 100,000 / unlimited |
| Prerequisite | None | An approved template for business-initiated messages |
| Record | On the device | In the system, per message |
| Measurement | None | Delivered, read, failed |
| Cost | No direct cost | Charged per Meta's rate card |
The first row is what catches businesses out: a broadcast to a list of 200 people where only 60 saved your number reaches 60. That is not a bug - it is the definition.
Why does it matter for reaching customers?
Because it decides whether you can reach them at all. An app broadcast list is useful for an audience already in contact with you who saved your number - regular customers who asked for updates, say. It is not a tool for reaching a customer list from your system.
The business platform solves that, but it demands infrastructure: an approved number, approved templates, and a limit that grows gradually. Per Meta's documentation a new business portfolio starts at 250 unique recipients in a rolling day, and the next tier opens through business verification, partner-led verification, or delivering 2,000 messages to unique recipients within 30 days on high-quality templates.
What actually counts as spam here
Not the volume. What decides it is how people respond: blocks, reports, and no engagement. Meta measures that as a quality rating on the number, and a low rating affects your ability to keep sending.
From that comes the single most important practical rule: better to send to people expecting it than to everyone. A campaign to 500 customers who bought in the past year is far safer than one to 5,000 numbers collected over five years - even when both fit inside the daily limit.
What to do before a campaign
- Clean the list - invalid numbers and anyone who asked to be removed.
- Confirm the template is approved in the language you will send.
- Check how much of the daily quota is free, so the campaign does not stop midway.
- Send to a small group and watch responses before expanding.
- Be ready to answer - a campaign generates replies, and that is the whole point.
Point 5 gets forgotten and is critical: a message sent to a thousand people with nobody answering the replies does more harm than good, because it produces exactly the silence that makes people block.
What only the platform can do
- Send to a list from your system, without requiring the customer to have saved your number.
- Know what happened to each message - delivered, read, failed and why.
- Keep history on the customer record rather than on a rep's device.
- Connect to processes - order confirmation, reminder, review request.
- Let several people work one conversation without handing over a phone.
The third is the difference felt most over time, and it is detailed in WhatsApp inside a CRM.
When the app is still enough
Not every business needs the platform. The app suffices when the business is small, when most conversations are inbound rather than outbound, and when one person handles all of them. Under those conditions, moving to the platform adds overhead without solving an existing pain.
Three signs the app has run out of road: more than one person needs to answer the same customer; you need to initiate to a list from your system; and somebody has already asked "what did we write to this customer two months ago" with no way to answer. When one of those appears, the move is justified - before that it is mostly work.
What happens to the conversation after the message
This is the difference most businesses do not think about in advance. A business-initiated message opens a window in which the customer can reply and you can answer in free text. Once that window closes, initiating again requires an approved template.
The consequence: plan the campaign so replies arrive during hours when somebody can answer. A campaign going out on a Friday afternoon generates replies exactly when nobody is available, and by Sunday some windows have closed - meaning the people who were actually interested now need another template instead of an ordinary conversation.
Planning a send to a large list
When the list exceeds the daily quota, the question is not whether to split but how. Three practical decisions: who goes first - usually the most recent customers, because their response rate is highest; how many per day - with headroom under the ceiling, to leave space for operational messages; and what time of day - hours when you can answer.
What to avoid is spending the whole quota in the morning and then discovering there is no room for an appointment reminder or an order confirmation. Operational messages matter more than the campaign, and they are the ones that will fall outside the quota if you did not reserve space for them.
What happens when quality drops
The quality rating is not a punishment but a signal: it says people are blocking or reporting. The correct response is to stop, review what was sent and to whom, and fix it - not to compensate for lower volume with another send. A simple check that helps: look at the last ten conversations that got no response, and ask whether the customer expected that message at all.
Sources
Frequently asked questions
How many recipients can an app broadcast list hold?
The app caps a list at 256 contacts, and on top of that the message only reaches people who saved your number. Those two limits together are why a broadcast list is not a solution for reaching a large audience.
Can I message all my customers from my system?
On the business platform yes, subject to the portfolio's daily limit and an approved template. Remember the limit counts unique recipients per rolling day, so a large list spreads across several days - planning that belongs before the campaign, not midway.
What happens when people block?
The number's quality rating falls, which affects your ability to keep growing the limit. A few blocks are part of life; a wave of them after a campaign signals the list or the message did not fit, and it is worth stopping to check rather than sending again.
SMS or WhatsApp for a campaign?
It depends on the goal. SMS needs no approved template and reaches every handset, making it simpler for a one-off message. WhatsApp allows a real conversation afterwards, which is a large advantage when replies are expected. The full comparison is in [SMS versus WhatsApp in Israel](/blog/sms-vs-whatsapp-israel-2026).
Keep reading
Related service
WhatsApp Cloud API
Templates, a two-way inbox and reminders on the official Meta API.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.
