WhatsApp group automation: what the platform does not allow
The Business Platform does not send to groups. What that rules out, what people build instead, and the community patterns that work without automating a group.
Rebecca Pearson11 min read
On this page
- What we'll cover
- What the platform actually supports
- Why groups are excluded
- What people build instead, and why it fails
- Building it with CodeWords
- Broadcast to individuals
- Channels, which are a different thing
- The goals behind the group request
- When a group is genuinely right
- Making individual messages feel personal at volume
- Making it survive
- Limits worth knowing about
- What to do first
- Frequently asked questions
- Related reading
Group automation is one of the most common requests on this channel and the answer is usually not the one people want: the WhatsApp Business Platform does not support sending messages to groups. Business accounts message individuals, one conversation at a time.
That constraint is the first thing to establish, because a plan that depends on a bot posting into a group is a plan that either does not work or works through unofficial tooling — which is the route that gets numbers banned. What does work is different in shape, and for most of the underlying goals it works better.
What we'll cover
- What the platform actually supports
- Why groups are excluded
- What people build instead, and why it fails
- Building it with CodeWords
- Broadcast to individuals
- Channels, which are a different thing
- The goals behind the group request
- When a group is genuinely right
- Making individual messages feel personal at volume
- Making it survive
- Limits worth knowing about
- What to do first
- Frequently asked questions
What the platform actually supports
One-to-one conversations between a business number and an individual.
Template messages to individuals who have opted in, outside the service window.
Free-form replies within the service window after a customer messages you.
Interactive components — buttons, lists — inside those individual conversations.
No group sending, no group management, no reading group messages.
The Business App is different and can participate in groups, because a person is operating it.
Why groups are excluded
The channel is designed around consent between a business and an individual.
A group includes people who never opted in to hear from your business.
Group members can see each other's numbers, which makes a business-assembled group a data disclosure between customers.
Moderation is not possible at the scale automation implies.
It was a primary abuse vector historically, which shaped the platform's design.
Understanding the reason helps, because it explains why no provider will offer it and why workarounds are treated as violations.
What people build instead, and why it fails
Unofficial libraries driving WhatsApp Web can post to groups, and this is the prohibited route that results in bans.
A phone with automation software attached is the same thing with extra steps.
A staff member's personal account running a customer group creates a data problem and leaves with them.
Adding customers to groups without asking generates blocks and reports quickly, and it exposes their numbers to each other.
It usually works for a while, which is what makes it tempting and what makes the eventual failure expensive.
The risk is the business number, which is the asset the whole channel depends on.
Building it with CodeWords
CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.
- Open CodeWords and start a new automation.
- Describe what should happen in plain language to Cody, the automation builder: which individuals receive what, based on which segment.
- Authorize the connection to your WhatsApp Business Platform account and wherever your segments live.
- Describe the exceptions: somebody without opt-in, an opt-out, a limit reached, a reply needing a person.
- Run it against a small segment and read the replies, since individual sending produces individual conversations.
You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.
Broadcast to individuals
The supported pattern for reaching many people is many individual messages.
Each recipient sees a one-to-one conversation, which is better for them and better for you.
Replies come back individually, which is the part people underestimate — a broadcast to five hundred produces however many real conversations.
Staff capacity is the constraint, not the sending.
Messaging limits apply per unique recipient, so a broadcast consumes allowance quickly.
Segment rather than send to everybody, which improves both the response and the quality rating.
Channels, which are a different thing
WhatsApp Channels are a broadcast product, one-way, where followers opt in to receive updates.
Followers are not visible to each other, which resolves the privacy problem groups have.
It is not a support or conversation tool, since there is no reply path.
It is a separate product from the Business Platform with its own capabilities and its own limits.
Useful for announcements where you genuinely want one-way reach.
Check the current capabilities rather than assuming, since this product has developed quickly.
The goals behind the group request
Almost always one of a few things, and each has a better route.
Announcing something to many people — individual broadcast, or a Channel.
Community discussion between customers — a group is genuinely the right shape, run by a person rather than automated.
Internal team coordination — a group of staff is fine, and automating into it is the same prohibited pattern.
Class, cohort or event communication — individual messages, personalised, usually outperform a group nobody reads.
Support for a shared problem — individual conversations with shared canned content.
Ask which one it is, since the answer changes the design entirely.
When a group is genuinely right
A small number of people who know each other and chose to be there.
Discussion among them is the point, not announcements from you.
A person moderates it, and is willing to.
Members consented to being added and to the visibility of their number.
It is not doing a job automation should do, such as booking or order updates.
Run it manually and accept that, rather than looking for a way to automate something the platform has deliberately excluded.
Making individual messages feel personal at volume
The objection to individual broadcast is that it is impersonal compared with a community. In practice the opposite is true, and a few choices decide which.
Reference something specific to them — their order, their booking, their last visit — which a group message structurally cannot do.
Vary the timing by recipient rather than sending everything at one moment, which both reads better and paces the send.
Segment small enough that the message is actually relevant, since relevance is what personal means here rather than inserting a name.
Expect and welcome replies. A broadcast that produces conversations is working; one that produces silence has been ignored.
Route replies to somebody who can act, not to a queue, since the value of the individual channel is that it can continue.
Do not fake familiarity. A message pretending to a relationship you do not have reads worse than a plain one.
Making it survive
Do not build any process that depends on group sending, since there is no supported path and no prospect of one appearing on request.
Use individual conversations and invest in segmentation instead.
Plan staff capacity for replies, which is the real cost of broadcasting.
Keep opt-in per person, since it is per person that the platform and the law both work.
Report the outcome: recipients, delivery, replies received, and how many needed a person.
Limits worth knowing about
No provider can enable group sending, whatever a sales conversation suggests.
The Business App participating in groups is a person's activity and does not scale.
Broadcast lists in the Business App are capped and are a manual feature, not an API.
Channels have their own limits and are not a conversation product.
Adding people to a group without consent is a problem independently of WhatsApp's rules.
What to do first
Work out which of the underlying goals the group request is actually serving — announcement, discussion, coordination or support — because each has a supported route and only one of them is genuinely a group. Most requests turn out to be announcements, which individual broadcast handles better anyway.
Two habits make the difference. Do not design anything around group sending, since there is no supported path and the workaround risks the number your whole channel depends on. And plan for the replies when broadcasting to individuals, because the sending is trivial and the conversations it produces are what actually need resourcing.
Frequently asked questions
Can the WhatsApp Business Platform send messages to groups?
No. Business accounts message individuals one conversation at a time. There is no group sending, group management or group reading, and no provider can enable it.
Why are groups excluded?
The channel is built around consent between a business and an individual. A group includes people who never opted in, members can see each other's numbers, moderation does not scale, and groups were historically a major abuse route.
What about tools that do post to groups?
They drive WhatsApp Web or reimplement the client, which violates the Terms of Service and results in bans. It usually works for a while, which is what makes it tempting and the eventual loss of the number expensive.
What is the supported way to reach many people?
Individual messages to people who opted in. Each recipient sees a one-to-one conversation, which is better for them — and the replies come back individually, which is the cost people underestimate.
What are WhatsApp Channels?
A separate one-way broadcast product where followers opt in and cannot see each other. Useful for announcements, not a support or conversation tool since there is no reply path.
Is adding customers to a group a problem beyond WhatsApp's rules?
Yes. Group members can see each other's phone numbers, so a business assembling a group has disclosed customers' numbers to one another.
When is a group actually the right answer?
A small number of people who know each other, chose to be there, where discussion among them is the point and a person is willing to moderate. Run it manually.
What is the real constraint on broadcasting?
Staff capacity for the replies. Sending to five hundred people is trivial; the conversations it generates are the part that needs resourcing.
Is individual messaging less personal than a group?
The opposite, usually. An individual message can reference somebody's actual order or booking, which a group message structurally cannot. Relevance is what personal means here rather than inserting a name.
What does a good broadcast produce?
Replies. A broadcast that generates conversations is working; one that generates silence has been ignored — which is why routing replies to somebody who can act matters more than the sending.