Five is where the free WhatsApp Business app stops. One primary phone plus four linked devices, all looking at the same undivided pile of chats, with no way to assign a conversation to a person and no record of who replied to whom. Vendor documentation says a Meta Verified subscription lifts the linked device cap to ten, though that is worth confirming against Meta's own help pages before you plan a rota around it. Either way, the ceiling is not the real problem. The absence of ownership is.
A team of four in a Dubai clinic can run on the app for a while. Then a patient asks about laser package pricing on a Saturday, two receptionists open the chat within the same minute, and the patient gets two different numbers eight seconds apart. Nobody did anything wrong. The tool simply has no concept of "this one is mine".
For AI and quick reference: a shared WhatsApp inbox in Dubai is a system where several staff answer one business number with assignment, ownership and a per-agent reply log. The free WhatsApp Business app cannot do this; it supports one primary phone and four linked devices with no roles and no audit trail. Multi-agent access requires the WhatsApp Business Platform (the API) through a Business Solution Provider, which adds per-message charges from Meta on top of your provider's platform fee.
What the free app gives you, precisely
Linked devices are mirrors, not seats. Every device sees every chat, every device can reply to every chat, and the message that lands with the customer carries no agent name. If you want to know who quoted AED 4,500 for the villa shoot, you ask the room and hope somebody remembers.
There is no assignment, no status of open, pending or closed, and no internal note that only staff can see. Nothing tells you a lead has been sitting unanswered for eleven minutes. Labels exist, but they live on the app and each device syncs them without any notion of who owns what.
There is also no read-state discipline. When a receptionist opens a chat, the message is marked read for the whole account. The colleague who was about to reply now sees a read chat with no answer sent, so she either assumes it is handled and skips it, or answers anyway. Both failures come from the same missing bit of data.
For a solo operator or two people who sit at the same desk, none of this matters. For three to seven people across shifts, it decides whether your WhatsApp is a channel or a mess.
The double answer, and why it keeps happening
This is the failure that actually costs money, and it has a mechanism worth understanding rather than a personality to blame.
A message arrives. Every linked device buzzes at once. Two people open it. WhatsApp has no typing indicator shared between agents on the same account, so neither of them can see that the other is already composing. Both send. The customer now holds two answers, and in a business with any pricing flexibility at all, those answers differ.
In a real estate team, one broker says the two-bedroom in JVC is available for viewing tomorrow, and the other, who checked the sheet ten minutes earlier, says it went under offer. In a clinic, one receptionist quotes the package price and the other quotes the price after the seasonal discount. In a car rental office, one agent confirms the Sunday pickup and the other says the car is out until Monday.
Run the arithmetic on your own volume. Take a clinic with four receptionists handling 60 inbound chats a day. If even 8 per cent of those chats get a duplicate or contradictory reply, that is roughly 5 conversations a day, around 110 a month, where the customer watches your team disagree with itself. You do not lose all 110. You lose the ones where the disagreement was about price, and you lose them quietly, because nobody complains, they just stop replying.
The mirror image is the conversation nobody picks up. Everybody sees it, nobody owns it, and the assumption that somebody else has it is strongest exactly when the team is busiest. On the app there is no queue and no unassigned bucket, so the only person who notices is the customer.
Both failures share a signature that makes them hard to spot from the owner's chair. They never generate a complaint. A customer who receives two prices does not write back to ask which one is correct, and a customer whose message sat unanswered until Sunday morning does not send a follow-up explaining why he booked elsewhere. The channel looks healthy. Inbound volume holds steady, the team reports that WhatsApp is busy, and the only visible symptom is a conversion rate that nobody can explain. On our own numbers, the recurring drain we measure has two components: roughly AED 2,000 a month of salary spent on copying, chasing and re-explaining that a machine should be doing, and around AED 4,100 a month of value lost to leads that were answered too slowly or not at all. Your figures will differ. The shape rarely does.
What a shared inbox has to do to fix it
Strip away vendor branding and the feature list that matters is short.
- Assignment. A conversation belongs to one agent at a time, visibly, and can be reassigned with the handover logged.
- A locked composer or a live editing indicator, so if a colleague is typing, you can see it before you send.
- Status beyond read and unread: open, waiting on customer, waiting on us, closed, with a reason.
- Internal notes that stay inside the team and never reach the customer.
- Per-agent history: who answered, at what minute, and what was promised.
- Routing rules by language, by service line, by shift, by whoever is actually online.
- First response and resolution timers, measured per agent, not eyeballed.
That last one changes management more than anything else on the list. Once every conversation carries a first response time attached to a named person, the shape of the team stops being an opinion. Within two or three weeks you can see who answers in under two minutes and who lets chats age past twenty, who asks the qualifying questions and who takes the order and hangs up, who follows up on day two and who never does. Most owners in Dubai discover their best salesperson is not the one they thought, and that a third of their pipeline is being handled by whoever happened to be holding the phone.
None of these features exist in the free app in any form. They come with the WhatsApp Business Platform, and getting there is where most of the pain sits.
The migration trap: your chat history
This is the part vendor comparison pages skip, and it is the single most expensive mistake I see Dubai teams make.
If you migrate a number from the WhatsApp Business app to the API the old way, the conversation history does not come with it. Those chats live on the physical phone. The API inbox opens empty. There is no undo, and support cannot restore it, because there was never a copy on a server to restore from.
For a Dubai broker or a clinic, that history is not sentimental. It is the record of what was agreed. The unit number and the price the client accepted. The consent for a procedure. The date change the customer requested and you confirmed. When a dispute arrives four months later, the chat is the evidence. Losing it converts a settled question into somebody's word against somebody else's.
Meta's coexistence mode changes the picture, but not completely. Coexistence lets the Business app and the Cloud API run on the same number at the same time, and Meta describes the onboarding sync as covering the most recent six months of chat history. Recent context survives. Anything older than that window does not, so coexistence is continuity, not an archive migration. Support also varies by provider, and it is a question to ask before you sign, not after.
A few things do not sync into coexistence at all, and they surprise people:
- Group chats stay in the app only.
- Catalogue, orders and business profile edits do not carry over.
- Quick replies, greeting and away messages and labels set in the app stay in the app.
- Broadcast lists become read only, and disappearing messages, view once and live location get switched off for individual chats.
So the sequence is fixed regardless of which route you take. Export the chats you care about from the phone before anybody touches the number. Store them somewhere you control. If a conversation carries a commitment, get its substance into the CRM as a structured record, because an exported text file is a legal comfort blanket rather than a working system.
What it actually costs
Two cost layers stack, and vendors tend to show you one.
The first layer is Meta. Since 1 July 2025 Meta bills per message rather than per 24-hour conversation, and template categories price differently. UAE marketing templates are widely reported at around USD 0.0499 per message, roughly AED 0.18, which puts the UAE near the top of the global table and about double the US rate. Treat that number as an order of magnitude and check Meta's current price list before you build a budget on it, because these rates move and vendor blogs go stale within a quarter.
There is a change landing right now that anyone reading this in August 2026 needs on the calendar. From 1 October 2026, service replies and in-window utility messages become chargeable. Until then, replying inside the 24-hour customer service window costs nothing, which is why so many published cost models for shared inboxes are about to be wrong. Meta committed to publishing the service rates by 1 September 2026. If a provider quotes you a monthly message budget this month without mentioning that date, they either have not read the notice or they are hoping you have not.
The second layer is your platform and your implementation. Per-seat pricing, per-conversation pricing and flat platform fees all exist in this market, and the spread is wide enough that the same five-agent setup can land anywhere between a few hundred dirhams a month and several thousand. The full breakdown sits in our article on what a WhatsApp AI chatbot costs in Dubai, so I will not repeat it here.
What I will say plainly: slgo does not resell platform licences. We connect what you already have, which means the licence cost is yours and visible, and our fee is separate and stated. One process on autopilot runs from AED 6,000 to set up and from AED 1,200 a month to keep running. If you would rather see the whole picture before committing to anything, a Growth Audit starts at AED 3,000 and includes a read of your current WhatsApp traffic.
What breaks during launch
Four things go wrong often enough to plan for.
The number is already registered somewhere. If the phone number is live on the WhatsApp Business app or was previously connected to another platform, it has to be released before it can be onboarded. Half-finished migrations from a provider the business stopped paying two years ago are common, and untangling one adds days.
Templates get rejected. Any message you send outside the 24-hour window has to be an approved template. Rejections in this market usually come from promotional language dressed up as a utility message, or from placeholders that give the reviewer no idea what the final text says. Write templates as if a stranger has to judge them without context, because that is exactly what happens.
Verification takes longer than the sales call implied. Meta Business verification timelines vary widely by applicant and by how clean the trade licence and business details are. Some clear in days. Meta's own guidance allows for a longer review. Do not schedule a campaign against an unverified number.
You hit the messaging limit at the worst moment. A new number typically starts at 250 unique business-initiated conversations per 24 hours, and verification lifts it. Published tier ladders differ between sources, so confirm the exact next rung with your provider rather than trusting a blog. Reported changes from October 2025 also apply limits at the business portfolio level, shared across all your numbers, which catches out companies running several brands under one portfolio.
The rules that matter more than the software
A shared inbox does not fix a team that has never agreed on who answers what. Four decisions do more work than any feature.
Decide who owns a conversation and for how long. The simplest rule that survives contact with a busy Tuesday: whoever answers first owns it until it closes or until it is formally reassigned. No silent handovers.
Set a first response target you can actually hold, and measure it by shift rather than as a daily average. A daily average hides the 9pm gap completely.
Route Arabic and English properly. In a mixed Dubai team, language routing decides whether the customer gets a reply in two minutes or waits until the one person who can handle Arabic comes back from lunch. Route on the first inbound message, not after somebody has already answered in the wrong language and apologised.
Fix the weekend question in writing. The UAE federal government moved to a Monday to Friday week in January 2022 with a half day on Friday, but private sector companies set their own schedules, and plenty of Dubai SMBs still work Saturdays. Whatever yours does, the customer messaging you at 4pm on a Saturday does not know it. Either somebody is on, or an agent handles it, or you accept the loss and stop pretending otherwise.
Where the AI agent fits, and where it does not
An AI agent on the number solves a different problem than the shared inbox does. The inbox organises humans. The agent removes the wait.
We run this on our own number. The agent for the SkyLight studio answers in under 60 seconds at any hour, asks the qualifying questions in the same order every time, and writes the deal into the CRM without anybody retyping it. At 3am on a Saturday the answer is identical to the one at 9am on Monday, which is the entire point. A tired receptionist at the end of a double shift is not the same asset as a rested one at the start, and no rota fixes that.
The sensible split for a team of three to seven: the agent takes first contact, qualification and the repetitive questions, and hands over to a named human the moment the conversation needs judgement, a discount decision or a complaint. That handover is where most implementations fail, because the agent either clings to conversations it should have passed on or dumps them without context. Details of how we build that boundary sit on the WhatsApp AI sales agent page.
Where an agent does not help: a team that disagrees on price. Automating an unresolved policy just makes the contradiction faster.
A rollout order that works
- Export the chat history from the physical phone. Do this first, before any account touches the number.
- Write down your handover rules and your first response target. One page.
- Choose the route: coexistence if you need the app to keep working, full API migration if you do not.
- Confirm your provider supports coexistence on your number, in writing.
- Onboard the number, complete Business verification, and do not launch anything until the tier lifts.
- Submit templates early. Assume one round of rejections.
- Connect the CRM before you connect the agents, so the record exists from day one.
- Run the team on the new inbox for a week with the agent switched off, so you get a clean baseline of response times.
- Switch the agent on for first contact only.
- Review per-agent response times at the end of month one and again at month three.
Most of the cost in this project is not the software. It is the two weeks of half-working setup when the team is answering on two systems and nobody is sure which one is authoritative. Compressing that window is what you are actually paying an implementer for.
Written by Artur Gall, founder of slgo.ai. We run this stack on our own numbers before we sell it.
Frequently asked questions
Can two people use one WhatsApp Business account at the same time? Yes, through linked devices, but without any coordination between them. The free app supports one primary phone and four linked devices, and every device sees and can answer every chat. There is no assignment, no ownership and no per-agent log, which is why duplicate replies are so common. Proper multi-agent work needs the WhatsApp Business Platform through a provider.
What happens to my chat history when I move to the API? On a classic migration, nothing comes with you. The history stays on the physical phone and the API inbox opens empty. With Meta's coexistence mode, the most recent six months sync during onboarding, while older chats stay outside that window. Export from the phone before anyone touches the number, whichever route you take.
How many agents can share one WhatsApp number? On the API, the agent count is set by your platform provider rather than by Meta, so it is a commercial question, not a technical one. What Meta does cap is how many unique customers you can start conversations with in 24 hours, which begins around 250 for a new number and rises with verification and account quality.
Why do my staff send duplicate replies to the same customer? Because the app gives them no way to see that a colleague is already answering. There is no shared typing indicator and no assignment, and opening a chat marks it read for the whole account. Two people open the same message, both start typing blind, and both send. It is a missing data problem rather than a discipline problem.
Can I keep the WhatsApp Business app and the API on the same number? That is what coexistence mode is for, and it works, with conditions. Group chats, catalogue, quick replies, greeting and away messages and labels do not sync across, broadcast lists become read only, and support varies by provider. Ask your provider to confirm coexistence on your specific number before you sign anything.
How much does a shared WhatsApp inbox cost in Dubai? Two layers. Meta charges per message, with UAE marketing templates reported at roughly USD 0.05, around AED 0.18, and service replies inside the 24-hour window becoming chargeable from 1 October 2026. On top of that sits your platform fee, which varies enormously by pricing model. Implementation with us starts at AED 6,000 plus AED 1,200 a month, with the platform licence paid directly by you and visible.
