Shared WhatsApp inbox: stop selling from a phone
What a shared WhatsApp inbox is, how it works with several agents, and why it is the base for not losing leads when a salesperson leaves.
A shared WhatsApp inbox is a web mailbox where the whole team sees and handles conversations on the company number. It is not “pass the phone around”. It is not a cloned QR on three iPhones. It is the same model as Gmail or Intercom, applied to WhatsApp.
If your operation today is each salesperson on their own WhatsApp, this is the change that cuts lead leakage the most.
The problem the spreadsheet does not show
The spreadsheet says 80 leads this week. WhatsApp says something else:
- Three salespeople, three numbers, three calendars.
- The customer writes on Saturday to a phone that is on silent.
- On Monday nobody knows if a price was already offered.
- On holiday, the chat is orphaned.
- When someone leaves, IT cannot “recover WhatsApp”. The history walked out in a pocket.
That is not fixed with more templates on the phone. It is fixed with one number and one inbox. It is the base of any WhatsApp CRM.
How it actually works (with the API)
A shared inbox needs WhatsApp Business API. The number is registered in the cloud. Messages arrive in ManyContacts. There:
- You see the queue: new, in progress, closed.
- You assign to an agent or a team (sales, admissions, after-sales).
- You leave internal notes the customer does not see.
- You use tags (enrolment, visit, claim, cart).
- AI can take the first shift and hand you a qualified chat.
The customer writes to one place. You decide who steps in.
Shared inbox vs “WhatsApp Web on several computers”
WhatsApp Web is not multi-agent. It is the same user on another screen. If two people type, they collide. No assignment. No permissions. No audit.
A real inbox lets you:
| Situation | WhatsApp Web | Shared inbox |
|---|---|---|
| Two agents at once | Conflict | Each has their chat |
| See only “mine” | No | Yes, by assignment |
| Manager sees times | No | Yes |
| A salesperson goes on leave | You lose context | The chat continues |
| AI + human | Not native | Clear turns |
If someone sells you “shared WhatsApp” with a parallel session, you are one dead phone away from chaos.
Team rules that prevent disaster
The tool does not replace a minimum of judgement:
- One owner per chat. Everyone else watches or is mentioned. You avoid two different offers.
- First-response SLA. For example, 5 minutes in hours and AI coverage after hours.
- Mandatory tags when closing or moving stage.
- No personal phones for new customers. The company number is the only sales channel.
- Handoff in the note, not in an internal WhatsApp voice note.
Academy and insurance broker teams that do this well are not larger: they are more ordered.
What to look for in the product
- Collision: does it warn if two people open the same chat?
- Mentions (@colleague) and notes.
- Roles: agent, supervisor, admin.
- Unlimited history (or at least years, not 30 days).
- Channels together: WhatsApp + Instagram + email, if your customer jumps between them.
- Optional mobile: app or PWA for people on the street, on the same inbox, not on their personal WhatsApp.
ManyContacts is built around that mailbox. Kanban and campaigns sit on it, not the other way around.
Personal phones: how to leave without drama
Do not disconnect every number on Monday at 9. Plan:
- Pick the official number (the one already on the website, or the best known).
- Connect it to the API. The other numbers are used only to say: “write to us here”.
- Import contacts. App history can be migrated in many cases; ask at signup.
- For two weeks, salespeople only reply in the panel.
- Switch off personal WhatsApps for new customers.
The usual fear is “I will lose the personal touch”. Personal touch is not the phone’s IMEI. It is answering fast and not making the customer repeat themselves.
Inbox + AI: who speaks first
The inbox does not force a human to greet at 23:00. You can let the AI agent ask the qualification questions and, when there is an appointment or a quote, assign a salesperson. The chat stays in the same inbox. There is no bot in another galaxy.
That is what we ask for in automotive, training and clinics: 24/7 coverage without 15 people on call.
How to roll it out in 14 days
Week 1. Official number on the API. Users created. Ban replying to new customers from a personal phone. 30-minute meeting: assignment, tags, what counts as “closed”.
Week 2. Weekend shifts or night AI. First response-time report. Clean chats with no owner. Progressive shutdown of satellite numbers.
If on day 14 you still hear “I’ll send it on my WhatsApp, it’s faster”, you do not have a product problem. You have a management problem. The inbox only works if the salesperson’s incentive is not to hide the lead.
What changes for the salesperson on the street
They do not lose the phone. They change the app. From the street they open the same chat, upload a photo of the DNI or the car, and leave a note. The colleague in the office can continue if a call comes in. The customer does not notice two companies: they notice they are not asked to repeat themselves.
That is more “personal” than three days on read because the number’s owner was on leave.
Next step
If company WhatsApp today is the sum of everyone’s phones, the inbox is the first project, not the last. Create the account and put two agents in the same day. Or book a demo and we set it up around your flow.