What a WhatsApp shared inbox actually needs to do
Most tools give you a list of chats. The ones teams keep using give you assignment, an AI that knows when to stop, and the contact record beside the thread.
Almost every WhatsApp business tool ships the same core: a list of chats on the left, a thread in the middle. That part is easy and everyone has it. The tools teams are still using a year later differ somewhere else entirely.
1. Assignment has to be the handover
The single most common design mistake is treating "the bot is handling it" as a mode you toggle. It creates a state machine nobody can see: is this chat in bot mode? Did someone turn it off? Who owns it now?
The version that survives contact with a real team is simpler: an unassigned chat is a bot chat. Assigning it to a person takes the bot out. There is no mode, no toggle, and no chat that is somehow being handled by both. It also means the agent's view is trivially correct — they see what is assigned to them, so unassigned bot traffic is invisible to them by construction rather than by a filter someone has to maintain.
2. "Unreplied" must be a filter, not a report
The question a supervisor asks forty times a day is "what has nobody answered?" If that requires exporting to a spreadsheet, it will be asked four times a day instead, and the answer will be wrong.
It belongs in the filter chain next to everything else: all, sent, failed, replied, unreplied — then channel, assignee and status. Facets on the conversation itself, not saved searches with a lifecycle of their own.
3. The contact record has to be on the same screen
A thread tells you what was typed. It does not tell you that this customer has called twice this month, that a colleague left a note saying they prefer email, or that there is an open task about their renewal.
Without that, every handover starts with "let me just check something" and ends with the customer repeating themselves. With it, whoever picks up is already caught up. This is the difference between a shared inbox and a group chat.
4. One bot, many channels — so never list by bot
Teams that grow past one channel discover this quickly: the same assistant should answer WhatsApp, the website widget and Instagram, because it is the same business with the same answers. Once that is true, a "conversations by bot" list is a lie — it either duplicates the inbox or contradicts it.
Keep one conversation list. Mark bot-handled chats with a badge. Let the bot be a property of the conversation, not a place you go.
5. Templates, flows and the QR are WhatsApp's problem alone
WhatsApp is the only channel with message templates that need approval, with flows, with payment settings and with a wa.me QR code. Every other channel would look absurd carrying those controls.
Resist the symmetry instinct. In Convarza AI, WhatsApp gets one extra card that no other type gets, and Instagram and Facebook get no credential fields at all because they are single sign-on only. A form that can never be filled in is worse than a missing form.
6. Somebody has to be told when a template is rejected
Template rejection is the classic silent failure: your campaign stops working and nobody finds out until a customer complains. It belongs in the same notification vocabulary as bot handovers, overdue tasks and disconnected channels — and workspace-level events like these should be hidden from agents, who cannot act on them anyway.
The short version
If you are evaluating tools, ignore the chat list. Ask instead: how do I hand a conversation from AI to a human, what do I see when I do, how do I find what nobody answered, and who gets told when something breaks. Those four answers will tell you whether your team is still using it in a year.