WACrew

Blog

One WhatsApp number, multiple users: your options and the trade-offs

Three ways to put a team on one WhatsApp number (linked devices, the official API with a support platform, or a panel on top of your own account), what each costs and risks, and the team rules that matter with any tool.

Updated 5 min read
On this page
  1. Route 1: linked devices
  2. Route 2: the official API with a support platform
  3. Route 3: a panel on top of your own account
  4. Team rules that apply with any tool
  5. Moving to a team without losing context
  6. FAQ

At some point, one person can't keep up with the company WhatsApp anymore. Then comes the question: how do you put more people on the same number without two of them answering the same thing, without a customer falling through the cracks and without handing the whole account to everyone?

There are three routes, with very different costs and risks. This guide walks through each one and ends with the team rules that apply whatever tool you pick.

Route 1: linked devices

WhatsApp itself lets you use one account on more than one device. Besides the main phone, you can link up to four devices, such as computers running WhatsApp Web or another phone in companion mode (WhatsApp blog). Each team member opens WhatsApp Web on their computer and that's it.

It's free and works the same day. The problems show up with use:

  • Everyone sees everything. There are no per-chat permissions. The intern sees the contract negotiation and the chat with your co-founder.
  • Nobody knows who replied. To the app, every message came from the same account. You can't tell whether Anna or Peter sent it, or who promised that deadline.
  • Two people answer at once. With no queue and no sign of who is handling a chat, the same question gets two answers, sometimes different ones.
  • Device limit. Past four linked devices, someone has to be logged out. Linked devices also log out if the main phone goes unused for a couple of weeks.

For two or three people who talk all day, it works. Beyond that, it gets messy.

Route 2: the official API with a support platform

Meta's official API (the WhatsApp Business Platform) doesn't depend on a phone and was built for teams. Platforms such as respond.io, Wati, Twilio-based tools and many others use it and add chat routing, department queues, handoffs between agents and reports.

Pros: far more agents, access control and the route Meta approves.

Costs and limits: Meta charges per template message by category, and the platform charges a monthly fee, often per agent. The API also has its own rules, like the 24-hour window for replying without an approved template. We compare hosted options in respond.io alternatives and WhatsApp AI agent platforms, and the app-versus-API decision in WhatsApp Business app vs API.

For companies with high volume, departments and outbound messaging, this is the right route.

Route 3: a panel on top of your own account

There's a third path, used by people who support project clients and don't want to move to the official API: a panel that connects to the WhatsApp account you already use (the way WhatsApp Web does) and creates separate logins for the team.

That's what WACrew does. It's open source and runs on your own server:

  • Each team member gets their own login, created by you, with a password and a list of allowed chats. They sign in at the same link and only see what was shared with them. No QR code, internal notes or contract.
  • Every message records who wrote it. You from your phone, you from the panel, Anna from the panel, or the AI. It's clear who promised what.
  • Team members' messages go through the same review that blocks wrong forms of address and repeated messages.
  • If a team member replies, any pending automatic reply in that chat stops. Nobody talks over anyone.

The caveat is the same as with any tool that uses the WhatsApp Web protocol instead of the official API. For answering your own customers at normal volume, it usually works fine. For bulk messaging, it doesn't. More context in open-source WhatsApp APIs and the open-source CRM angle in open-source WhatsApp CRM.

Team rules that apply with any tool

Tools help, but agreements are what prevent chaos.

One owner per chat. Every customer or group has one person responsible for answering first. Others step in only when asked or when the owner is away.

Queue by wait time, not by latest message. Whoever has waited longest comes first, no matter who owns the chat. The reasoning is in WhatsApp response time.

Agree on what team members can promise. Status and information, yes. New deadlines, discounts and extra scope, only with whoever decides. Write it on one page and share it.

One house voice. If every team member writes very differently, the customer notices the handoff. It doesn't have to be identical, but agree on the basics: how you address people, emoji, how you open and close.

Review the first few weeks. Read the replies of anyone new. Adjusting tone early is easier than undoing a misunderstanding with a customer.

Moving to a team without losing context

Putting a team on the number you used alone needs extra care with what's already in the chats.

  1. List your active customers and assign an owner to each before giving access.
  2. Write down the context that only lives in your head, like agreements made by phone and pricing deals, in a note per customer.
  3. Tell your closest customers that someone else on the team will also answer. Said by you, it sounds like care. Discovered on their own, it sounds like being dropped.
  4. Start each team member with a few chats and expand as they pick up the tone.

Changing numbers at the same time the team arrives usually costs more than it gains. If you can keep the number customers already know, keep it.

FAQ

Can I have multiple users on the free WhatsApp Business app? Yes, through linked devices, with the device limit and no per-chat access control.

Do I need the official API to have a team on WhatsApp? For large teams with departments and outbound messaging, yes. For a small team supporting project clients, a panel on top of your own account works without changing numbers.

How do I know who replied to each message? In the regular app, you can't. You need a tool that records the author of every message, such as API platforms or the WACrew panel.