If your clients are anywhere outside the US, the project already lives on WhatsApp. They moved years ago. WhatsApp Business is Meta's acknowledgment of that — and for agencies it's both necessary and nowhere near sufficient.
What it gives you
- A business identity — verified name, profile, hours. Clients see a company, not a personal number.
- Multi-person access — the API tier (via a provider) lets a team share the number instead of one PM's phone becoming the company switchboard.
- Structure — labels, quick replies, catalogs. Fine for a shop; thin for projects.
Where it stops
WhatsApp Business was designed for commerce: order questions in, tracking numbers out. Project work breaks its model immediately, because the messages aren't transactions — they're requests, approvals and scope changes that need to end up on a board, in a ticket, against a budget. WhatsApp gives you none of that:
- No connection between a message and a task in Jira/Asana/Trello
- No memory of what was agreed — scope lives in a PDF WhatsApp has never met
- No sense of who should answer, so everything defaults to whoever's online
- No approval layer — every reply is as official as your most junior person's thumbs
The missing layer
What agencies actually need on top: every chat attached to a project, status questions answered from the board, new asks checked against scope, and sensitive replies held for human approval. That's the layer Gavril provides — WhatsApp stays the channel your client loves; the project management happens invisibly behind it.
← All posts