WhatsApp Shared Inbox: One Number for a Whole Team

Can several people answer customers from one WhatsApp number?

Yes. There are two routes, and the right one depends on how many people reply and how much tracking you need. The first is the WhatsApp Business app with linked devices. The second is the WhatsApp Business Platform, where the number connects to software your whole team logs in to.

Customers see one business and one number in both cases. The difference is on your side: staff either share a chat list and sort things out among themselves, or each conversation has an owner, a status and a history. That second setup is what people mean by a shared inbox.

Why does one phone stop working as the team grows?

One phone stops working because a chat list shows who wrote to you and leaves open who is dealing with them. With two or three people in the same room, you can close that gap by talking across the desk.

Linking devices solves the access problem only. WhatsApp's announcement of the feature describes employees responding from their own phones under the same business account, and Meta's developer documentation puts the limit at four companion clients. More people can reach the number, but deciding whose job each chat is stays with you.

With a bigger team, or with staff on different shifts, the same problems tend to appear:

Two people answer the same customer, sometimes with different answers, while another chat gets no reply at all.
A case stalls when the person who knows it goes home, goes on leave or quits.
Reception, sales and accounts each need different conversations, and they scroll past each other's work to find their own.
A manager cannot tell how long customers waited or how many requests are still open without reading chats one by one.
Customers repeat their story because the next person cannot see what was promised last time.

What is a shared inbox and what does it do?

A shared inbox is software that puts incoming messages into a queue a team works together, with each conversation assigned to someone. It can sit on one WhatsApp number or combine several channels.

Picture a clinic with one number. Reception handles bookings, the billing desk handles payment questions, and a nurse answers follow-up questions after a visit. Each group opens its own queue, while the patient keeps writing to the number already saved on their phone. A clinic should also decide who may read which conversations, and take advice on its local privacy obligations.

Most of the value comes from these functions working on the same customer record:

Routing sends each new chat to the right queue by rule, so a billing question reaches accounts and a new enquiry reaches sales.
Assignment gives every chat one owner, automatically or by hand, so the team can see what is unassigned and what is theirs.
Tickets turn a chat into tracked work when a case needs follow-up, such as a damaged delivery or a complaint.
Contact history links the chat to the customer's record, so whoever opens it can see earlier conversations.
Internal notes let colleagues discuss a case inside the conversation without the customer seeing it.
Response targets, known as service level agreements or SLAs, make overdue chats stand out before the customer has to chase. Many inboxes track them.

What is the difference between the WhatsApp Business app and the WhatsApp Business Platform?

The app is a product you install and use yourself, while the Platform is a set of APIs that software connects to. Meta says the app is "built with the small business owner in mind". Its product page covers a business profile, showing products and replying when someone first writes or when you are away, and Meta's developer documentation also lists quick replies and labels among the app's tools. The product page does not mention routing rules, response targets, tickets or team inboxes.

Meta's documentation describes the Platform as APIs that let businesses communicate with customers at scale, and that documentation is written for developers. It includes the Cloud API for messaging and the Business Management API for accounts, phone numbers and analytics. Incoming messages reach your server as webhooks. The same overview mentions WhatsApp Manager, a web tool for accounts, numbers, templates and analytics, but it does not describe a screen where agents answer customers. In practice, that screen comes from the software you connect.

Meta offers two ways onto the Platform. With a partner integration, a partner handles setup through Embedded Signup, which Meta suggests for businesses that do not want to manage the API or that want ongoing support. With a direct integration, your own developers connect to the API and keep full control.

Cost differs too. Messages sent from the app stay free, while Meta charges for Platform messages per delivered message, by category and by the recipient's country code. A simple way to decide:

Stay on the app if a handful of people reply, volume is manageable and nobody needs reports on response times.
Move to the Platform with a shared inbox if chats need owners, several teams share one number, or WhatsApp conversations should sit next to your customer records.
Pick a partner or a software provider if you have no developers, and a direct integration only if you have people who can build and maintain it.

How do you set up a shared inbox on one WhatsApp number?

Start by choosing the number, then connect it and write your routing rules before anyone starts answering.

Meta will not register a number already in use on WhatsApp until it is deleted there. If your number is on the WhatsApp Business app, Meta's coexistence flow may save you from deleting it. It connects the existing account to the Cloud API through Embedded Signup, so the number works in both places and message history stays in sync. If the business agrees, up to 180 days of one-to-one chats can be shared, though group chats are excluded.

That flow has trade-offs. Broadcast lists are disabled, existing linked devices are unlinked and supported ones can be linked again, and Meta lists group chats, calls, catalogs, quick replies and labels as unsupported on the Cloud API side. Your provider has to offer the flow, and Meta's page does not state availability by country, so ask your provider to confirm it works for a Saudi or Jordanian number before you plan around it.

The steps below follow Meta's requirements for the Platform:

Choose a number you own, with a country and area code, that can receive a voice call or SMS. Meta does not support short codes.
Check whether that number is already on WhatsApp. If it is, decide between deleting it there and the coexistence route described above.
Set up your Meta business portfolio, your WhatsApp account and a display name, which appears in place of the number in WhatsApp clients. A partner's Embedded Signup flow walks you through these and verifies the number.
Settle who pays Meta. Depending on the partner type, either the partner shares a line of credit or you add a payment method to your Messaging account.
Connect the number to your inbox software and create one inbox for each team, such as support, sales or reception.
Write down who receives what, which cases become tickets and the response target for each queue.
Get templates approved for the messages you start yourself, such as appointment reminders or order updates, and keep a record of customer opt-in.
Pilot with one team for a week or two and review the unassigned and overdue chats before adding the next team.

What WhatsApp rules should your team know before going live?

The rules that shape daily work on the Platform are the 24-hour window, opt-in, automation limits, messaging limits and per-message charges.

Train agents on the window first, because it is the rule they will meet every day: a customer who went quiet two days ago can only be reached with a template. Meta changes these rules and rates, so check its current documentation before launch. As Meta documents them today:

The customer service window lasts 24 hours from the customer's last message or call. Inside it, agents can send text, media, documents and buttons without pre-approval. Once it closes, only pre-approved templates can go out.
You can only message people who have opted in, whether or not the window is open, and you must honor requests to stop. Meta's policy lists separate opt-in for each message category as a best practice.
Automated replies are allowed inside the window, but the policy requires a prompt and clear way to reach help, such as an in-chat transfer to a human agent.
Messaging limits cap how many unique people a business can message outside service windows in a moving 24 hours. Meta says new portfolios start at 250, and all numbers in a portfolio share the limit.
Since October 1, 2026, Meta charges for service messages beyond a monthly free tier. It also warned that it would stop delivering service messages for businesses with no payment method on file, so confirm yours is in place.

How does Repzo handle this?

The shared inbox in Repzo Workstation supports WhatsApp today, alongside email, Instagram, Facebook and web chat.

You connect a channel account to an inbox, and each inbox can have its own type, default team, auto-assignment mode and SLA policy, so support and sales can run separate queues. New conversations are routed by inbox rules and assignment strategy. Agents see updates in real time and can leave internal notes.

Repzo matches conversations to existing CRM contacts, so the agent has the customer's CRM record for context. When a case needs formal tracking, the agent creates a linked ticket from the conversation in one click. Fox AI, the assistant built into Workstation, drafts replies in the inbox and summarizes conversations and tickets.

For messages you start yourself, Repzo Send runs WhatsApp template campaigns to reusable segments, honors per-contact consent and suppressions, and paces sends to your Meta daily messaging limit. Clinics and service businesses can run appointment scheduling in the same workspace.

You can read more on the pages for Saudi Arabia and Jordan. If you want to keep a number you already use on WhatsApp, raise it early with our sales team, because the route depends on how that number is used today.

Frequently asked questions

Can two people use the same WhatsApp number at the same time?

Yes. On the WhatsApp Business app, staff can use linked devices, up to four companion clients. On the WhatsApp Business Platform, agents sign in to software connected to the number, and how many can sign in depends on that software.

Do I have to give up my current WhatsApp number?

Not always. A number in use on WhatsApp has to be deleted before it can register on the Platform. A number on the WhatsApp Business app may instead join through Meta's coexistence flow, if your provider offers it, and stay usable in both places.

Does each team need its own WhatsApp number?

No. Several teams can share one number and work separate queues in a shared inbox. If you do want more numbers, Meta caps new business portfolios at two registered numbers, rising to 20 once the business is verified or reaches a messaging limit of 2,000.

Is a shared inbox the same as a CRM or a help desk?

No, though they often connect. The inbox is where conversations are answered, the CRM holds customer records and deals, and a help desk tracks tickets through to resolution. Linking them lets an agent see the customer's record and raise a ticket from the chat.

Can we message a customer who last wrote three days ago?

Only with an approved template, and only if that customer has opted in. The 24-hour customer service window has closed by then, so free-form replies are no longer allowed until the customer writes or calls again.

Can a chatbot answer first on a shared WhatsApp number?

Yes, inside the 24-hour window. WhatsApp's policy allows automation there, as long as the customer has a prompt and clear way to reach help, such as a transfer to a human agent in the chat.