A WhatsApp group is one conversation with many participants, up to 1,024 people, where everyone (or only admins) can write. A community is an umbrella that bundles related groups and has an announcement group, where only admins post to every member.
Differences in practice
| group | community | |
|---|---|---|
| what it is for | one conversation | organizing several conversations for one audience |
| who talks | everyone, or admins only | announcements by admins only; each group keeps its own rules |
| number visibility | participants see each other in the group | members of the announcement group do not see each other's numbers |
| typical use | one client, one project, one team | a school, a building, a company with several teams |
For client work
The usual setup at agencies and software studios is one group per client: the client, the account owner and whoever does the work. A community makes sense when you have many clients and want to send the same notice to all of them (planned maintenance, for example) without exposing one client to another.
In WACrew each client group becomes a conversation in the inbox, with a queue by waiting time, notes and contract; see organizing client groups on WhatsApp.
Common mistake
Creating a community for a single client. It turns into bureaucracy: the client has to find the right group inside it. Another one is putting all clients in one "support" group, which exposes them to each other and tangles the questions.
Questions
Can automation read a community's groups? Over the WhatsApp Web protocol, yes: each group in a community is a regular group to the integration.
Can I turn a group into a community? You can add existing groups to a community.
In Portuguese: grupo vs comunidade.



