%20(1).avif){kind=small}
.png)
WhatsApp Shared Inbox vs Team Inbox: What Botpress & Voiceflow Teams Actually Need
Search "WhatsApp shared inbox" or "WhatsApp team inbox" and you'll find both terms used almost interchangeably across different tools' marketing pages — which makes it genuinely confusing to figure out what you actually need, especially if you're layering this on top of an existing Botpress or Voiceflow chatbot.
Here's the plain-language version: they describe the same underlying capability, just from two different angles. "Shared inbox" emphasizes that multiple people can access one WhatsApp number. "Team inbox" emphasizes that a team is working collaboratively out of it — assigning conversations, tracking who replied to what, avoiding duplicate responses. In practice, when you're evaluating tools, you're looking for the same feature set either way.
What a WhatsApp Shared/Team Inbox Actually Needs to Do
If you're comparing options, the feature list that actually matters looks like this:
- One WhatsApp number, multiple agents — no more juggling a single phone between team members
- Conversation assignment — a clear owner for each chat, so nothing gets answered twice or missed entirely
- Shared conversation history — any agent picking up a chat can see everything that's already been said
- Status tracking — open, pending, resolved — so the team has visibility into what still needs attention
- Notifications and routing — new messages reach the right person without someone having to manually check constantly
Any tool marketed as either a "shared inbox" or "team inbox" for WhatsApp should cover this list. If it doesn't, the label is doing more marketing than describing actual functionality.
Where This Gets More Complicated: Adding a Chatbot
This is the part most shared inbox tools weren't originally built for. If you're running a Botpress WhatsApp or Voiceflow WhatsApp bot, the inbox isn't just handling human-to-human conversations — it also needs to handle the moment a conversation moves from bot to human.
That's a different problem than a standard shared inbox solves. A generic WhatsApp inbox tool assumes every conversation starts with a human agent. But when a chatbot is the first point of contact, the inbox needs to:
- Receive an escalated conversation from the bot with full context intact (not just "new message, good luck")
- Show the agent what the bot already tried, and why it escalated
- Let the bot resume automation later in the same thread if appropriate, rather than treating the handoff as a one-way door
This is the exact gap between a plain shared/team inbox and a proper human handoff (HITL) setup. Botpress human handoff and Voiceflow human handoff specifically refer to this bot-to-human transition — and it's worth treating as a distinct requirement from "can multiple people use one WhatsApp number," even though the two often get bundled into the same feature description.
A Simple Way to Evaluate What You Need
Ask two separate questions, not one:
- Do multiple people need to work from one WhatsApp number? If yes, you need a shared/team inbox at minimum.
- Does a chatbot handle the first part of the conversation before a human might need to step in? If yes, you need that inbox to also support proper handoff — context, escalation reason, and resumption — not just multi-agent access.
Most teams evaluating tools focus only on question one, then discover months later that question two was the actual gap causing frustrated customers and confused agents.
Where HitlChat Fits
HitlChat is built to answer both questions at once for teams running Botpress or Voiceflow bots: a full shared WhatsApp team inbox for your human agents, connected natively to bot-to-human handoff so conversations move seamlessly between automation and your team. Whether your bot lives in Botpress or Voiceflow, the inbox and the handoff logic are designed to work together rather than as two separate tools bolted together after the fact.
