WhatsApp multi-agent: why linked devices are not enough once you are more than two

How many devices the WhatsApp Business app supports

If you are looking for WhatsApp multi-agent so several users can handle the same number, the first answer you will find is "use linked devices". It works, up to a point, and it pays to know where that point is.

WhatsApp's help center specifies it: on the WhatsApp Business app you can link your phone as one of up to four additional devices, the same as linking WhatsApp on a browser, a tablet or a computer. With the main handset, five screens in total.

For two people that is enough. For four it starts to hurt. And the reason is not the number.

Linking is not distributing

A linked device is the same account, open somewhere else. Everyone sees everything, everyone can answer everything, and there is nothing in between saying who owns what.

That produces a scene anyone who has lived it recognizes instantly. Two people answer the same message with two different replies. A chat goes unanswered because all three assumed someone else had it. Someone goes on holiday and their knowledge of the customer goes with them, because it lived in their head and not in the chat.

The app solves simultaneous access. It does not solve how work gets divided, because it was not built for that.

The three symptoms that you have outgrown it

You do not need a complicated diagnosis. If any of these three happens, you are already past what the app can give you:

1. Duplicate or contradictory replies to the same customer. The classic symptom that nobody owns the conversation.
2. You cannot say who handled a case. If a customer complains about something they were told, and you do not know who told them, you have no traceability.
3. You need someone to see some chats and not others. The app has no way to segment: whoever is linked sees the entire inbox, including the conversation with your supplier and the one with the customer negotiating price.

The third is usually what forces the change, because it stops being an operational annoyance and becomes a confidentiality problem.

What changes when the number lives in an inbox

Moving to the official API is not just "more devices". What changes is that the conversation stops being a chat on a phone and becomes a case with an owner.

With Alumbra Chat, every message from every connected channel lands in a single inbox. On top of that sits what the app cannot give you:

• Conversation assignment, to segment what each team member sees.
• Inviting your whole team with no device limits, so team size stops being the constraint.
• Tags and custom views, to sort the inbox by your business logic instead of by arrival order.
• Canned responses, for what gets answered twenty times a day.
• A mobile app, so leaving the office does not mean losing the thread.

What to sort out before adding people

Here is a warning that does not usually make it into articles about multi-agent: adding people to a messy channel multiplies the mess.

Before splitting the inbox across four, look at two things.

How much of what they answer is repeated. If 60% of messages are the same question, you do not need four people answering it: you need it answered on its own so the four can handle the rest.

How long first contact takes. With the official API the customer service window appears: when the customer writes, a 24-hour window opens to reply freely, and once it closes you have to pick it back up with a template that gets billed. Adding agents without cutting response time leaves you with more people arriving late to the same place. How that clock works is in the 24-hour window.

Key takeaways

• The WhatsApp Business app lets you link up to four devices besides the main one.
• Linking gives simultaneous access, not distribution: nobody owns the conversation and no traceability is left behind.
• The three symptoms of outgrowing it are duplicate replies, not knowing who handled what, and needing each person to see only their own.
• An inbox with assignment solves distribution, segmentation and the device limit.
• Before adding people, cut the repetitive work and the response time, or you will scale the problem instead of the solution.