WhatsApp Business Multiple Users: How Teams Share One Number

What does an API with a shared inbox add for teams?

The API model separates the number from the people. Your inbox software decides who can log in, who sees which conversation and who owns it, so the team can grow without adding devices.

A shared inbox on the WhatsApp Business Platform should give you:

1. Named agents with their own logins, so every reply has an owner.
2. Assignment and tagging, manual or by rule, so a conversation is not left unclaimed.
3. One thread per customer across WhatsApp and your other channels. See our shared inbox guide.
4. Templates and saved replies that agents can use in one click, within Meta's template rules.
5. Routing by language, topic or queue, useful for Arabic and English teams.
6. Handover from chatbots and AI agents to a human with context. See chatbot to human handoff.
7. Reports on first response time and workload. Our first response time guide shows how to compute it.

When you evaluate any inbox, ask to see these on your own conversations rather than on a demo script. Our question page on multiple agents gives a short version of this list.

The API also brings policy structure that the team must learn. You may only message people who opted in. Outside the 24-hour customer service window you can only send approved templates. Meta's policy expects an escalation path to a human when you use automation. The customer service window opens when a user messages you and resets with each new user message. Our guide to the 24-hour window explains the mechanics.

Which setup should my team choose?

Choose by team size, volume and how much you need to know about who did what. Use this checklist.

1. One or two people, low volume, no marketing: the Business app with linked devices is enough.
2. Three to five people who value the app but want automation: consider coexistence through a provider.
3. More than five agents, shifts or several queues: use the API with a shared inbox.
4. You send campaigns, order updates or reminders at volume: the API, because the app is not built for approved-template campaigns.
5. You need reports, SLA targets or audit of who replied: the API with a shared inbox.
6. You want a chatbot or AI agent in front of agents: the API.

If two or more of items 3 to 6 apply, plan the move now rather than waiting for a missed lead to force it.

How do I move from the app to a shared inbox?

Plan it as a short project with an owner, a cut-over day and a rollback plan for support hours. The steps below are typical, but your provider will confirm the exact route for your number.

Step-by-step

1. List your needs: number of agents, languages, queues, opening hours, existing templates and quick replies.
2. Check the number and business details. Meta business verification and the display name are part of onboarding; our team can prepare and file the registration with you, and approval decisions stay with Meta.
3. Decide between coexistence and a full move. Review the unsupported features table above against what you use today.
4. Onboard through Embedded Signup. Your provider guides the business through Meta's flow. See how to set up the WhatsApp Business API and the guidance on migrating a number between providers.
5. Rebuild quick replies as templates and saved replies. Quick replies and labels are not supported on a coexistence number, so recreate the ones you rely on in the inbox.
6. Create users and roles, then assign queues or tags.
7. Brief the team on opt-in, the 24-hour window and handover rules before go-live.
8. Run a pilot week with a small queue and review first response time and missed chats.
9. Switch campaigns and automation on only after the team is comfortable.

Use the free WhatsApp API readiness checklist to confirm your account is ready before you start.

Worked example: a six-person clinic in Kuwait

"Noor Dental", a synthetic clinic in Kuwait, has one reception desk, two coordinators and three doctors who sometimes answer patients. All of them use one WhatsApp Business number on linked devices. The practice has four problems: two staff replied to the same patient with different prices, evening enquiries were not claimed by anyone, the manager could not see which questions were repeated, and the sixth person had no device to link.

They move to a shared inbox. Reception and coordinators get logins, evening chats are assigned to the duty coordinator, and doctors are added to a tag-only view for clinical questions. A reschedule menu answers the most common request, and a rule hands any message containing a complaint to the manager. Within a month the team reads first response time by hour and moves one shift. Nothing about the patients' experience changes except that replies come faster and from one consistent voice.

What mistakes should I avoid?

• Handing out the phone password or code. Use companion devices or inbox logins; never share verification codes.
• Keeping the primary phone off or unused. Companion devices depend on it.
• Assuming the API keeps every app feature. Groups, catalogs and labels need new homes or workarounds.
• Mixing personal and business use. A shared number belongs to the business, not to one employee's phone contacts.
• Skipping the opt-in record. Moving to the API makes consent evidence more important, not less.
• Letting agents paste customer data into public tools. Keep transcripts and exports inside systems you control.

How OmniChannels.ai helps

OmniChannels.ai puts WhatsApp, Instagram, Messenger, Telegram and Email in one Omni Inbox: one thread per customer, agent assignment and tagging, plus media, templates and attachments in replies. BroadNet is an official Meta Business Solution Provider, and onboarding runs through Meta Embedded Signup with our team handling the registrations with you. Chatbots and AI agents understand English and Arabic and hand over to a human agent. See the customer support solution or book a demo to walk through your team's queues. The Facebook Messenger inbox channel page explains how Messenger sits in the same inbox.