Most small teams hit the same wall. The company WhatsApp number lives on one phone. Sales uses it in the morning, support in the afternoon, and the owner takes it home at night. Then two customers write at the same time, or one writes while the phone sits in a drawer, and the cracks show.
This guide explains what the WhatsApp Business app really allows, where it stops, and how to give several people their own login on the same company number with the WhatsApp Business API and a team inbox, with a step-by-step setup list at the end.
Why does one number shared by a team stop working?
The symptoms are familiar if you have lived through them:
Shared login. Everyone knows the phone's PIN or uses the same WhatsApp Web session. Nobody knows who wrote what.
Two people answer the same customer. One rep sends a quote, another sends a different one five minutes later.
Nobody answers. Each person assumes someone else has it. The customer waits an hour, then writes to another business.
No record. When a rep leaves, the chats, contacts and promises leave with the phone, or with their personal number.
No numbers. You cannot tell how many conversations came in this week, how long the first reply took, or who closed what.
None of this is a people problem. It is a tooling problem: one phone was designed for one person.
Can the WhatsApp Business app handle several users on one number?
Partly. The free WhatsApp Business app lets you link a handful of extra devices, such as a laptop, a tablet or a second phone, to the same account through Linked devices. WhatsApp documents the current limits and conditions in its help center, and they change from time to time, so check there rather than trusting a number you read elsewhere.
Linked devices solve one thing: more screens. They do not solve the team problem, because every linked device sees exactly the same thing:
No assignment. There is no way to say "this chat belongs to Ana". Every device sees every chat and anyone can reply to anything.
No visibility control. A new hire sees the full history with every customer.
No audit trail. Every reply goes out as "the business". You cannot tell afterwards who sent which message.
No notes, no reports. No private notes between colleagues, no response times, no volumes per person.
Still tied to one phone. The primary phone owns the account, and the linked devices depend on it.
For a two-person shop this is often enough. For a sales team of four or a support desk, it is not.
What is the real answer: the WhatsApp Business API plus a team inbox?
The WhatsApp Business API (Meta also calls it the WhatsApp Business Platform or Cloud API) is Meta's official way to connect a number to software instead of a phone. On its own it is only an API. What turns it into a multi-user WhatsApp is a team inbox: a web application where each person has their own account and everyone answers from the same company number.
This is the shift that ends the chaos:
Each user logs in with their own email and password. No shared PIN, no shared session.
Every message is stamped with the person who sent it.
Conversations become things you can assign, label, hand over, reopen and report on.
The number belongs to the company, not to a phone or an employee.
On the customer's side, nothing changes. Messages still arrive as a normal WhatsApp chat from your business name and number. They only notice faster replies.
On cost, the API is not a licence you buy from Meta. Meta bills messaging by its own price list (since October 1, 2026, free-form replies inside the 24-hour window are billed per message after the first 1,000 per number per month), and the inbox provider charges separately for the software. HellouOne passes Meta's fees through at 0% markup; plans are on the pricing page.
Do you lose your number when you move to the API?
No. This is the most common fear and it is unfounded. There are two ways to get there, and both keep your number.
Path 1: move the number to the API. The number is disconnected from the WhatsApp Business app and connected to the API. Customers keep writing to the same contact; your team now answers from the inbox. Meta does not carry the app's own chat history over, so back it up from the phone first if you want to keep it. The full walkthrough is in how to move your WhatsApp Business number to the API and keep it.
Path 2: coexistence. The WhatsApp Business app stays on the phone and the team inbox runs on the same number at the same time. The owner keeps the app they know, the team works in the inbox, and the business migrates gradually instead of on one nervous Monday. We cover the details in WhatsApp coexistence: app and team inbox on one number.
HellouOne supports both. Pick migration if the phone is already a liability and you want a clean break. Pick coexistence if the owner or a key seller is not ready to give up the app, or you want to test the inbox with part of the team first.
What do you gain once the whole team answers from one inbox?
The point of a multi-user WhatsApp is not just more hands. It is the rules around those hands.
Assignment rules. New conversations go to a person automatically: round robin across the sales team, or by priority so hot leads jump the queue. Nothing falls between two people. The options are explained in who sees what and who gets the next conversation.
Visibility levels. HellouOne has five, from "only my assigned chats" up to "everything in the account". A new rep sees their own conversations, a supervisor sees the team's, the owner sees it all. This is also what protects your customer list when someone leaves.
Private notes and @mentions. Ask a colleague for a price or a delivery date inside the conversation without the customer seeing it. The context stays with the chat.
Reports. First-response time, conversations per agent and per team, and sentiment: the questions you could never answer with a phone.
AI agents answer first. An AI agent takes the first message at any hour, answers the frequent questions, qualifies the lead and hands it to the right person through a handover area. Your team starts from a conversation that already has context.
How do you set it up, step by step?
The whole thing takes an afternoon if you have the pieces ready. In order:
Decide who owns the number. It must be a company number tied to a company Meta Business account, not an employee's personal line.
Pick your path: migrate or coexist. If the number currently runs the Business app, coexistence lets you start without turning anything off.
Create or verify the Meta Business account and connect the number to the API. In HellouOne, LIA, the setup assistant, guides this from inside the product.
Create a user for each person. One login each, real names. Resist the shared "sales" user; it brings the old problem back.
Build teams. Sales, support, collections, branches. Teams are what assignment rules and reports are built on.
Set assignment rules. Round robin for sales, priority for VIP or returning customers, a default team for everything else.
Set visibility per role. Reps see their own chats, supervisors see their team, admins see everything.
Load the shared answers. Canned responses for the ten questions you answer every day, macros for the actions you repeat.
Switch on an AI agent for the first touch. Give it your FAQ, catalog and business hours, and define the handover area so it knows which team gets what.
Watch the reports for a week. Response time and unassigned conversations are the two numbers that tell you whether the rules are right.
How this works in HellouOne
HellouOne is a WhatsApp team inbox with AI agents built in, so the setup above is the product's default shape, not a custom project.
One number, one login per person. Every plan includes human agent seats (1 on Starter, 3 on Team, 6 on Growth, more on Scale and above). The 7-day free trial gives you 2 agents and 2 inboxes with no card, so you can try the multi-user workflow before paying.
Migrate or coexist, your choice. Connect the number to the API and keep it, or keep the WhatsApp Business app and run the HellouOne inbox on the same number. LIA guides the connection step by step.
Team rules out of the box. Round-robin and priority assignment, five visibility levels, private notes and @mentions, handover areas, canned responses, automations and macros, and reports per agent, team, conversation and sentiment. The full list is on the features page.
AI agents first, people second. An AI agent answers the first message, qualifies and routes to the right team; your people pick up with full context. Every plan includes a monthly quota of AI messages.
0% markup on Meta's fees. You pay Meta's price list for messages and nothing on top.
It talks to your other tools. 16 connectors and two-way CRM sync (HubSpot, Pipedrive, GoHighLevel, DataCRM); developers get the API and SDK at one.hellou.ai/docs.
See how the pieces fit together on the how it works page, or start the trial and connect your number today.
What should you decide this week?
If three or more people touch your WhatsApp number, you have already outgrown linked devices. The decision is not whether to move to a team inbox; it is whether to migrate the number outright or run coexistence first. Either way the number stays yours, and for the first time you can see who answered, how fast, and what happened next.
