Group, Broadcast List, or Channel: What Should Your Company Use in Each Case

Broadcast list: the limitation nobody warns about

The broadcast list solves the exposure problem — each person receives an individual message and doesn’t see the others. However, it has a condition that undermines most campaigns: the message only reaches those who have your number saved in their contacts.

In practice, this means a list with 500 contacts may deliver to 120. Worse, you don’t know how many actually received it. The company thinks it communicated but simply did not.

There are two other relevant limits: the maximum size per list and the fact that frequent sending from a common number increases the chance of blocking due to reports — the mechanism detailed in why WhatsApp bans business numbers.

The account that shows the real reach

Base of 1,400 customers, end-of-month campaign.

Four times more people reached, with delivery, read, and response tracking per contact. The difference isn’t in the message: it’s in the channel chosen to deliver it.

Channel: what it’s really for

The channel is one-way communication for those who opted to follow. This makes it useful in three situations:

• Operational notices — special hours, address changes, maintenance alerts.
• Recurring content that builds an audience without requiring a response.
• Launches and news for an already engaged base.

What it doesn’t do: generate conversation, qualify interested parties, or record who is who. Channel is media, not customer service. Companies trying to sell via channel find that interested people can’t respond there — and the path to conversation is lost.

Group for the team: where it really works

The most productive use of groups in companies is internal, and even then it requires rules:

• One group per purpose, not a general group for everything. Separate operation, urgency, and social.
• Agreed hours. Work messages at 23h become expected replies at 23h.
• No important decisions only in the group. What needs to be remembered later disappears in the history after two days.
• Never share customer data in team groups, especially sensitive data — unnecessary exposure is exactly what LGPD requires companies to avoid.

Internal groups work for quick coordination and fail as a record system. When information needs to survive beyond a week, it belongs in the CRM, not the group.

When groups make sense and how to moderate them

There are legitimate cases for groups with customers: course classes, subscriber communities, specific projects, projects with multiple people involved. In these scenarios, four rules prevent degradation:

• Purpose written in the description and repeated at creation. Groups without explicit purpose become catch-all groups within a week.
• Restrict who can send messages when the goal is informative. Setting to admins only turns the group into a bulletin board without losing the list.
• Appoint a moderator with authority to redirect individual topics to private conversation. "I’ll message you privately to resolve this" needs to be said immediately, not later.
• Set an end date. Classes finished, projects delivered, completed projects — groups with defined deadlines avoid zombie contact lists no one dares to delete.

And one rule that always applies: nothing involving value, personal data, or individual participant situations goes into the group. This type of information goes to private conversation, without exception, regardless of momentary convenience.

The foundation that supports any sending

All formats discussed here depend on the same thing: a base built with permission. Without this, reach falls, reports rise, and the number is at risk.

Four natural moments to ask for this permission without causing friction:

• At the close of sale, asking if you can notify about news and offers.
• At delivery or service completion, when satisfaction is at its highest.
• On the website form, with explicit checkbox and clear text about what will be sent.
• In content campaigns, where the person requests something valuable and authorizes future contact.

Always record date, origin, and what was authorized. Besides being what the law expects, this record allows responding to complaints and separates the base that can receive sending from the one that can only be replied to. A base of 400 contacts with permission is worth more than one of 4,000 without — the first generates responses, the second generates blocks.

What to record about each contact

Regardless of the chosen format, four pieces of information must exist per contact for the sending to be defensible and useful: who they are, when they authorized, by which means they authorized, and what they authorized to receive. Without these fields, the company can’t respond to complaints nor separate who can receive campaigns from those who only wrote once.

It’s also worth keeping the opt-out path always visible. A line at the end of the message informing how to stop receiving reduces reports significantly — and reports, not unsubscribes, are what compromise the number. Customers who can easily leave rarely resort to the block button, and the base shrinks while gaining quality.

Frequency: how many messages per month without fatigue

The most common mistake after structuring the channel is overusing it. There’s no universal number, but three references help:

• Promotional communication: two to four times per month is the ceiling for most businesses. Above that, unsubscribes and reports rise quickly.
• Service communication — confirmation, reminder, delivery notice — doesn’t count here. It’s expected and well received at any frequency because it solves a customer problem.
• Useful content can be more frequent, as long as it’s genuinely useful. The test is simple: if the message only serves the company, it’s promotion by another name.

It’s worth monitoring two signals with each sending: block rate and response rate. Rising blocks warn of reputation problems with the number; falling responses indicate the message has become noise. Both appear before any platform penalty — and serve precisely to correct course while there’s still time.

How to choose with one question

One decision solves almost all cases: do you want people to talk among themselves?

• Yes — group, with moderation and clear purpose.
• No, but I want them to reply to me — individual sending via API, with opt-in and approved template. Broadcast list only if the base has your number saved.
• No, just notify — channel.

Most companies want the second option but use the first because it’s easiest to set up. The result is always similar: exposed base, disorganized conversation, and no data on who’s really interested. Structuring individual sending takes more work initially and is the only way to scale without burning the number or reputation — a topic covered in detail in mass sending on WhatsApp.