Agencies end up with one WhatsApp group per client: the client, the account manager, a developer or two, sometimes the client's own team. Thirty groups later, nobody knows which ones have a question without an answer. A WhatsApp inbox for agencies has to solve that first, before any AI: who is waiting, since when, and who on the team should answer.
WACrew is an open-source, self-hosted inbox that does this on top of your existing number.
What changes for the agency
One queue for every client group. Groups and direct messages land in one list, sorted by who has waited longest. A chat counts as waiting when the last word is from the client and nobody from the account answered after it. Closed loops like "ok, thanks" do not count.
Team access per chat. Create logins in the panel and choose which chats each person sees. The account manager sees their clients; the developer sees the project group. Every message sent from the panel is stamped with who sent it.
Context per client. Notes, tags, contract state and delivered features live next to the conversation, and a dashboard shows which clients are more active than their contract.
AI that sounds like the agency. Drafts follow the voice of the account owner, measured from real messages, and pass a review that blocks robotic tells before anything goes out. Each chat can be confirm (default) or auto.
Developers answer from their editor. The WhatsApp MCP server gives Claude Code, Codex, Cursor or Antigravity the same queue, so the developer fixing a bug can read the client's screenshot and reply without switching apps. See How to connect WhatsApp to Claude Code with MCP.
Install
git clone https://github.com/sumioshi/wacrew && cd wacrew
PANEL_USER=admin PANEL_PASS=change-me docker compose up -d
Link the agency number at /config, then create the team logins in /equipe. If the agency uses two numbers, run one collector per number; one MCP server can serve both through the conta parameter.
Honest limits
- One number per collector. It is built around the number your clients already know, not a pool of shared numbers.
- Unofficial connection. It links as a device through Baileys, which suits groups with existing clients and does not suit bulk sending.
- Self-hosted. You run the server and keep the backups. In exchange, the client conversations never leave your infrastructure, apart from the AI calls you configure.
FAQ
Can several people use the same WhatsApp number? Yes, through the panel. Each person logs in with their own account and only sees the chats you grant. More in WhatsApp for multiple users on one number.
Does it work with WhatsApp groups, not just direct messages? Yes. Groups are the main use case, including mentions, replies and voice notes inside the group.
How does the team know a client is waiting? The queue shows it, with the time since the client's last message, and the panel can alert in real time.
Is there a monthly fee? No. The code is Apache 2.0. You pay for the server and for the AI provider, if you use AI features.



