WhatsApp broadcast lists versus groups: which to use when

A broadcast list and a group solve different problems, and a business choosing between them by convenience rather than by intent usually picks wrong.

A broadcast list sends the same message to many recipients, but each person receives it as an individual chat with the business. They cannot see who else received it, and their reply comes back privately. From the recipient's side it is indistinguishable from a message sent only to them.

A group is a shared room. Everyone can see everyone else's messages, phone numbers are visible to other members depending on settings, and any reply goes to all of them. It creates a conversation among the members rather than a set of parallel conversations with the business.

That difference in privacy and social dynamics is the whole basis for choosing. A message that is really about the recipient's own order, appointment or account belongs in a broadcast, because it concerns them alone. A message intended to build something collective — a community, a class, a residents' discussion — belongs in a group, because the value comes from members hearing each other.

The mistake with real consequences is using a group to send announcements to customers who have no reason to talk to one another.

Broadcast lists carry a constraint that surprises almost everyone: a recipient only receives the broadcast if they have the business's number saved in their contacts. If they have not, the message does not reach them.

This quietly undermines the feature for most business purposes. A business assembling a list of two hundred customers, sending an announcement and seeing it delivered to a fraction of them has not encountered a bug. Customers rarely save a business's number unless they have a reason to, and no amount of care in composing the message overcomes it.

It also makes broadcast reach unmeasurable in a useful way. A business cannot tell from the sending side who failed the saved-contact test, so a broadcast that reached half its audience looks much like one that reached all of it. Decisions made on the assumption that a list represents reach will be wrong by an amount nobody can quantify.

There is also a cap on how many recipients a single broadcast list can hold, which has been a few hundred rather than thousands. Between the ceiling and the saved-contact requirement, broadcast lists are best understood as a tool for a modest number of engaged customers who already have the business in their phone — a regulars list, not a marketing channel.

Groups work when the members genuinely benefit from hearing each other. A class cohort coordinating around a schedule, a residents' association, a hobby community around a shop, a cohort of participants in a programme: in each case the conversation among members is the point, and the business is a participant rather than a broadcaster.

They are poor at announcements. Adding customers to a group so they can receive updates exposes their phone numbers to strangers, invites replies that everyone else has to read, and hands the business's messaging channel to whoever chooses to post in it. The complaint that a business "added me to a group without asking" is common precisely because it is a real intrusion — and the available response, leaving, takes the customer out of reach entirely.

Groups also have a moderation cost that scales with size. Someone has to remove off-topic content, handle disputes, and manage members. A group that is not moderated becomes an unpleasant place, and an unpleasant place associated with the business is worse than no group.

And unlike a private conversation, a group cannot be used to discuss anything specific to one customer. Order details, payment matters and personal information do not belong in a shared room, which rules out most of what a business actually needs to say to individuals.

This is the distinction that causes the most confusion, and it matters because the two live in different products. Broadcast lists and groups are features of the WhatsApp application, including the WhatsApp Business app. Sending through the WhatsApp Business Platform — approved templates, categories, per-message billing, quality ratings and messaging limits — is a different mechanism entirely.

Platform sending has no saved-contact requirement, so a template reaches a recipient regardless of whether they have the number stored. It scales far beyond a broadcast list's ceiling. In exchange it imposes structure: templates need approval, marketing needs consent, delivered messages are billed, and recipient reaction feeds a quality rating that governs how many people can be reached.

Neither is a loophole for the other. A business cannot avoid consent obligations by using broadcast lists instead of templates — policy on unsolicited messaging applies to a business's conduct on WhatsApp generally, and recipients can block and report from either. What broadcast lists avoid is not the obligation but the infrastructure, and they trade away reliable reach to do it.

So the practical reading is: broadcast lists and groups suit small numbers and existing relationships, at no messaging cost and with no approval process. Platform sending suits anything that needs to reach people reliably and at scale, at the price of structure and per-message charges.

A few questions settle most cases. Is the content specific to the individual, or genuinely shared? Individual content rules out a group immediately, regardless of convenience.

Do the recipients benefit from hearing each other, or would they find each other's messages an intrusion? If the honest answer is the latter, a group will generate complaints and departures, no matter how well it starts.

Does reach need to be reliable? If it matters that the message actually arrives — a closure notice, a change of timing, anything with a consequence for not knowing — the saved-contact requirement makes a broadcast list unsuitable, and platform templates are the correct instrument.

How many people are involved? A few dozen regulars who already have the number saved is a broadcast list's natural territory. Thousands of customers is not, and pretending otherwise produces a message that reached an unknown fraction of them.

One shape that works well is combining them honestly: platform templates for the messages that must arrive, and a small group or broadcast list for a genuinely engaged core who opted into it. What fails is using a group as a cheap substitute for a channel that needs to be reliable, and then treating the resulting complaints as a customer problem rather than a design one.

Where a group is genuinely the right choice, a few decisions made at the start prevent most of the trouble. Ask before adding anyone. An invitation link that people choose to use is materially different from being added without warning, and the difference shows up in how members behave afterwards.

State what the group is for in its description, and say what it is not for. A group whose purpose is unstated drifts toward whatever its most frequent poster wants it to be.

Decide who can post. Where the platform allows restricting posting to administrators, that is often the right setting for a group that is primarily informational — though it is worth being honest that such a group is a broadcast wearing a group's clothing, and a broadcast list or template may serve better.

Decide who moderates and what the rules are before you need them, because the first dispute is a poor moment to invent a policy. And give people an easy way out. A member who wants to leave and cannot find how will mute the group, which looks like membership and functions like absence — leaving the business with a number that flatters its reach and tells it nothing.