How to Share One WhatsApp Number With Your Team: Linked Devices vs a Shared Inbox
Your business has one WhatsApp number printed on the board, the bill book and the Google listing. Behind it, three people want to answer messages: the owner, a sales executive and someone at the counter. Right now they pass one phone around, or they all share a login on a spare handset. Replies get duplicated, chats get missed, and nobody knows who promised the customer what.
This guide explains the realistic ways to let a team share one WhatsApp business number, what each one can and cannot do, and when it is time to move to the WhatsApp Business API with a shared inbox.
Why Sharing One Phone Stops Working
A single phone is fine when one person handles every chat. It breaks down once volume grows or a second person joins.
Nobody owns a conversation. Two staff reply to the same customer with different answers, or each assumes the other one replied.
Staff leave and chats go with them. If the number lives on one employee's handset, history and access leave with that person.
Nothing is measurable. You cannot see response time, unanswered chats or who handled a lead.
Off-hours coverage is guesswork. The phone is with whoever last locked the shop.
Option 1: WhatsApp Business App on Linked Devices
The free WhatsApp Business app lets you link additional devices to the same account. At the time of writing, WhatsApp allows up to four linked devices alongside the main phone, so a laptop at the counter and a tablet in the back office can all show the same chats. Check WhatsApp's help pages for the current limit.
This is a good first step for a very small business. You also get labels, quick replies, a greeting message and an away message. Our guide to greeting, away message and quick replies shows how to set these up.
The limits are real, though:
No agent identity. Every reply goes out from the business, with no record of which staff member sent it.
No assignment. You cannot hand a chat to a colleague or stop two people replying.
No automation at scale. Bulk campaigns and chatbots are not part of the app.
Linked devices depend on the main phone. If the main phone stays offline for too long, linked devices get logged out.
Option 2: A Shared Login on a Spare Phone
Many shops keep a spare handset at the counter with the business number on it. It works, but it has the same problems as one phone, plus a security one: anyone who touches the phone can read every chat, including customer addresses and payment details. It also relies on one battery and one SIM staying healthy. We would treat this as a stopgap only.
Option 3: WhatsApp Business API With a Shared Team Inbox
With the WhatsApp Business API, the number is not tied to a phone at all. It connects to software, and your staff log in to that software with their own accounts. Each person sees the same live inbox, in a browser or app, from wherever they work.
This is the setup built for teams. A shared inbox such as VedLink AI's team inbox gives you:
Assignment: each conversation has an owner, so a customer is not answered twice.
Internal notes: staff can leave a private note on a chat for the next person, without the customer seeing it.
Roles and permissions: a counter executive can reply while only a manager can see reports or export contacts. See staff roles and permissions.
Other channels in one place: Instagram, Facebook and website chat appear in the same inbox, as covered in our unified team inbox guide.
Automation: chatbot replies, auto follow-ups and template campaigns sit alongside human replies.
What Changes When You Move to the API
Moving a number to the API is a real change, so plan it rather than do it in a hurry.
The number usually cannot run on the app and the API at once. Normally, a number moves to the API and stops working in the regular WhatsApp or WhatsApp Business app. Meta has introduced options for running both in some cases, but availability depends on region and setup, so confirm with your provider before you rely on it. Our guide to phone number requirements for India covers what is needed.
Chat history may not move across. Treat old chats on the app as something to export or note down before the switch, and ask your provider what can be migrated.
Messaging rules apply. Once on the API, you reply freely inside the 24-hour window and use approved templates outside it. This is explained in the 24-hour messaging window.
For a side-by-side view, read WhatsApp Business API vs the Business app.
How to Decide: A Simple Rule of Thumb
One or two people, a few dozen chats a day: the Business app with linked devices is usually enough.
Three or more staff, or chats you cannot afford to miss: move to the API and a shared inbox.
You run campaigns, appointment reminders or order updates: you need the API regardless of team size, because those use templates.
Several branches under one brand: use the API so branch staff share one inbox with clear assignment, instead of ten phones.
Example: A Clothing Store With Two Branches
Picture a clothing store with two outlets and one WhatsApp number. Customers message to ask whether a size is in stock. On a single phone, the owner answers when free and the rest wait.
With a shared inbox, the message lands for everyone. A quick reply with the store address and timings goes out first. The enquiry is assigned to the branch that has the item. If the customer writes after closing time, an away message sets expectations, and the first staff member in next morning sees it at the top of the unassigned list. This is an illustration of the workflow, not a result you should expect to match exactly.
Setting Up a Team Workflow That Sticks
Decide who answers what. Sales enquiries, order status and complaints can each have an owner or a queue.
Write your quick replies once. Store the common answers (timings, address, return policy) so everyone uses the same wording.
Set a reply-time target. Even an internal goal, such as answering within a set number of minutes in working hours, makes missed chats visible.
Use notes, not side chats. Keep internal discussion inside the conversation record, not in a separate staff group.
Review weekly. Look at unanswered and slow chats, and adjust assignment.
Frequently Asked Questions
Can two people use the same WhatsApp number at the same time? On the Business app, yes through linked devices, with limits. On the API, any number of staff can log in to the shared inbox, depending on your plan.
Do customers see which staff member replied? Not unless you write the name in the message. A common habit is to sign off with the agent's first name.
Do I need a new number for the API? Often you can reuse your existing business number after moving it, but it must meet Meta's requirements. Read the phone number guide above before you start.
What does it cost? Plan prices are on our pricing page, and Meta's per-message charges are separate and change over time. Our API pricing explainer walks through what makes up the bill.
Final Thoughts
Sharing one number is not a technology problem so much as an ownership problem. Start with the simplest setup that gives every chat a clear owner. When the phone becomes the bottleneck, move the number to a shared inbox so your team can work from their own logins.