What breaks when your staff WhatsApp group hits 20 people
Almost every small food and beverage team starts on WhatsApp, and for a while it is the right answer. It is free, everybody already has it, and there is nothing to teach.
Then the team grows, and four specific things break. They break in the same order every time.
1. Work follows people home
A staff group on a personal phone has no off switch. Somebody posts at 11pm about tomorrow's delivery and twenty phones light up, including the six people who are not working tomorrow.
What usually happens next is that people mute the group. Which solves their problem and creates yours, because now the announcement that actually matters is sitting unread in a muted thread.
2. Nothing is findable
Everything lives in one stream, in the order it happened. The cleaning rota, a photo of a broken tap, someone's shift swap, and the new procedure for cash are all interleaved.
Two weeks later, "what did we decide about cash" is a scroll, not a search. And because rules and chatter look identical, the answer you find might be the one that was superseded a month ago.
3. You cannot tell who has read anything
WhatsApp shows you that a message was delivered. It does not tell you that your closing team knows about the new procedure.
For most messages that is fine. For the ones that matter, food safety changes, a policy update, a shift change, you are relying on people to volunteer that they saw it. Some will. The ones who did not see it will not tell you, because they do not know.
4. Leaving is messy
When somebody leaves, they stay in the group until an admin remembers. Until then they can read everything, including the discussion about replacing them.
The reverse is worse. Their phone still holds the entire history: photos of the premises, supplier details, staff numbers, whatever was shared over two years. There is no way to take that back, and if you handle employee data in British Columbia or anywhere with similar privacy law, that history was never really yours to leave on a personal device.
The pattern
None of these are WhatsApp being bad software. They are a consumer chat app being used as an operational system, which it was never meant to be. It has no concept of a shift, a role, a store, or a record.
The fix is not a stricter group policy. Three-line rules about what may be posted where get ignored within a fortnight, because they add work to something that was chosen for being effortless.
What a work tool has to do differently
- Separate stores and roles. A Richmond closing question should not notify the Vancouver morning team.
- Respect off-shift. Non-urgent messages should wait until somebody is back on. Urgent ones should still get through.
- Keep procedures out of the stream. Rules belong in a handbook that can be searched, not in a scroll.
- Show read status where it matters. For announcements, not for everything.
- End cleanly. When somebody leaves, access ends, and the history stays with the business.
When to move
The trigger is usually one of two things. Either you have more than one location, at which point a single group becomes noise for most of the people in it. Or something went wrong and nobody could establish who knew what, which is the expensive way to learn the same lesson.
If neither has happened yet, WhatsApp is genuinely fine. Just do not mistake it working at eight people for it working at twenty five.
Butters gives each store its own channels, respects off-shift status, and keeps procedures in a searchable handbook rather than a chat scroll. See how it works.