How to set up a WhatsApp shared inbox for your team

A WhatsApp shared inbox is one workspace where your whole team can see, assign, and answer messages from a business WhatsApp number, without sharing a single phone. Instead of one person holding the device, every teammate logs in separately and works the same conversations from a browser.

The point is visibility and ownership. Messages land in one place the team can see, each conversation has a clear owner, and nothing depends on whose phone happens to be unlocked. That is the difference between a shared inbox and the workaround most small teams start with.

This guide walks through what a WhatsApp shared inbox actually gives you, how to set one up, how roles and multiple numbers work, the messaging rules to keep in mind, and what it costs. It is written for teams of roughly three to twenty people who have outgrown personal WhatsApp.

Personal WhatsApp breaks down for teams because the app was built for one person, not a group sharing a number. It works at first, then it does not.

Most small businesses start the same way: one number, one phone, one person handling everything. When the team grows past two or three people, the cracks show. Messages sit unread on someone's device. Two agents reply to the same customer and give different answers. A teammate picks up a thread halfway through with no idea what was promised.

The deeper problem is ownership. The WhatsApp Business app, even with the Linked Devices feature, ties the number to a single account that everyone shares. There are no separate agent logins and no record of who replied. So when a rep leaves, the chat history and the customer relationships can walk out the door on their personal phone. And when the one person who knows the answer is on vacation, the queue stalls.

A shared inbox gives your team three things personal WhatsApp cannot: separate logins, conversation ownership, and shared context. Together they remove the guesswork about who is answering what.

Every team member gets their own account, so you can finally see that Ana handled the morning messages and Bruno picked up the afternoon. Conversations can be assigned to a specific agent, which stops two people from replying to the same thread. Private notes stay attached to the customer, so the next teammate to touch a conversation starts with context instead of from scratch.

For a manager, the payoff is visibility without micromanaging. You can see queue health, who owns what, and where conversations are getting stuck, all without reading over anyone's shoulder. The conversations belong to the workspace, not a person and not a device.

Setting up a WhatsApp shared inbox takes about an hour and follows three steps: connect your number, invite your team, and set roles. There is no consultant, no integration project, and no sales call before you can see the product.

First, connect a WhatsApp number to the workspace. This runs on the WhatsApp Business Platform, and the tool walks you through linking the number so the team can send and receive from it.

Second, invite your team members and give each one access. On Clapvo's Gold plan you can invite up to five people on a single connection. Third, set each person's role so agents can reply, managers can see metrics, and admins control settings. Once that is done, your team is working the same inbox from their own browsers.

The seven-day free trial does not ask for a credit card, so you can move the number over and test the full workflow before you commit. Most teams send their first message from the workspace within the hour.

Roles decide who can do what, and getting them right early keeps the workspace clean as the team grows. A shared inbox is only calm when permissions match how people actually work.

The common setup is three levels. Agents see and reply to conversations and use shared templates and quick replies. Managers get the same plus visibility into metrics and queue health. Admins control connections, billing, and settings.

The reason this matters is that broad permissions are the thing teams regret. If everyone can change every setting, something breaks and nobody knows who did it. Role based permissions let you give people exactly the access their job needs and nothing more, so the founder is no longer the only person trusted with the controls.

You can connect more than one WhatsApp number to a single shared inbox, which is useful when different numbers serve different jobs. A sales number, a support number, and a regional number can all live in the same workspace.

Conversations from each number stay separated, so a support thread never gets confused with a sales lead, but your team can cover all of them without switching apps or phones. For a small team running two or three numbers, that consolidation is often the moment the workspace pays for itself.

Multiple numbers also unlock sender rotation for campaigns. Sending a large broadcast from one number is the fastest way to get it throttled, so spreading the sends across connected numbers (Clapvo calls this Random connection message sending) keeps each number closer to normal sending behavior. With only one connection there is nothing to rotate, so this matters most as you scale.

The 24-hour window is the period after a customer messages you during which your team can reply with free-form text. Knowing how it works keeps your shared inbox both fast and compliant.

While the window is open, your team answers naturally, no templates required. This covers almost all day-to-day support, because the customer started the conversation and you are simply replying. Once 24 hours pass with no new message from them, the window closes, and reaching them again requires a pre-approved message template.

A good habit is to resolve the issue or set expectations before the window closes, so you are not forced into a template just to send one more line. Keeping approved templates in the same workspace as the inbox makes that handoff smooth, because the whole team draws from the same vetted set.

Once your team is working from a shared inbox, track first-response time, resolution, and ownership, because those three tell you whether you are actually helping. Raw message volume only tells you how busy you are.

First-response time shows whether customers are getting a quick human reply. Resolution, even tracked loosely as whether a conversation reached an answer, shows whether issues close or just drift. Ownership, measured as the share of conversations with a clear assigned agent, shows whether your queue is managed or chaotic.

You will also start to see patterns you could not see before: which hours get the most messages, how long first replies take, which agents close conversations fastest. Those numbers give you something concrete to improve against, week over week.

A WhatsApp shared inbox does not have to cost more as your team grows, because the smart pricing model charges per number, not per person. Most tools charge per agent, so the bill climbs every time you hire.

Clapvo prices per WhatsApp connection instead. The Gold plan is $15 a month, or R$89, and includes one connection plus five team members, with annual billing at $149 a year. If you outgrow five people or one number, extra users and connections are available as add-ons. The unit of value is the number your customers message, not the headcount answering it.

For a small support or sales team, that model is the practical reason to move. A growing team on a per-seat tool pays more every quarter just for adding the people it hired to handle the volume.

Your team needs a WhatsApp shared inbox the moment ownership becomes a guessing game. The trigger points are familiar: a founder who has become the bottleneck for every reply, a queue where messages sit unread because nobody is sure whose job they are, or a rep who left and took the leads on a personal phone.

If you are still two people trading one phone, personal WhatsApp is fine for now. If you are three or more, and any of those situations sounds like your week, it is time to move the number off personal devices and into a workspace the whole team shares. That move, keeping the conversation with the team instead of the phone, is the entire point.