Routing WhatsApp leads to the right salesperson
Every UAE sales floor solves this the same way at first: give the lead the agent's personal number. It works until the agent resigns, and then you discover the pipeline left with them.
Short answer. One business number, a shared team inbox, and programmatic assignment. Route by language, then area, then product line, with round-robin only as the fallback. Never route by handing out personal numbers.
Why the personal-number pattern fails
It is not a philosophical objection. It fails in five concrete ways:
- The history leaves. When the agent resigns, every conversation, every quoted price and every promise goes with the handset. In a market with UAE-level sales turnover this is not hypothetical.
- You cannot reassign. A customer messaging a number nobody is monitoring gets silence, and there is no way to move that thread.
- You cannot audit. What was promised on price, availability or delivery is unknowable.
- No coverage. Annual leave, sick days and Fridays become dead zones.
- Numbers get banned. An agent doing bulk outreach from a personal number is doing exactly what WhatsApp's automated systems are built to stop.
The free WhatsApp Business app does not solve this either: it is built around one primary device with a limited number of linked devices, and it has no concept of assigning a conversation to a person. See one number for a whole sales team for where that line sits.
What the API changes
On the Cloud API the phone number belongs to the business, not to a handset. Conversations arrive as webhooks into your system, and assignment is a database field. That gives you three things you cannot otherwise have: a lead can be reassigned mid-conversation, an unanswered lead can be escalated on a timer, and every message is attributable to a named user.
One detail that matters operationally: the 24-hour service window belongs to the number, not to the agent. Handing a conversation from one salesperson to another does not restart billing and does not require a new template. Hand over freely.
Routing rules that fit a UAE sales floor
- Language first. This is the UAE-specific one and it outranks everything else. A customer who opens in Arabic and gets an English-only agent is a lost lead regardless of how well that agent knows the product. Detect from the first inbound message and route on it. Same for Hindi, Urdu, Tagalog and Russian depending on your market.
- Area or emirate. Decides serviceability and, in real estate and home services, decides who actually knows the community.
- Product or service line. Straightforward once qualification has captured it.
- Campaign or ad set. Click-to-WhatsApp ads can pass a referral payload identifying the ad. Route high-intent campaigns to your strongest closers rather than to whoever is next in the queue.
- Existing relationship. A returning customer goes back to the person who handled them last. This one is worth more than any of the others and is the most commonly skipped.
- Round-robin, last. Fair, and a signal that you had no better rule available.
The rules that matter more than the routing
Assignment is easy. What separates a working sales floor from a broken one is what happens when assignment does not produce a reply:
- Unanswered timer. No agent response in N minutes and it reassigns automatically. Set N in minutes, not hours.
- Out of hours. Route to whoever is on, or send an honest acknowledgement with a real response time. Silence is worse than "we open at 9am".
- Window expiry warning. Warn the agent before the 24-hour window closes, because after that they need a template and most will simply not bother.
- Capacity limits. An agent holding forty open conversations is not working forty conversations.
Reporting you get for free
Once assignment lives in a system rather than on handsets, you can answer questions that were previously unanswerable: response time by agent, conversations per agent, which source produces leads that actually convert, and which agent lets windows expire. That last one is usually the most revealing number on the whole dashboard.
Adjoltz builds these flows for UAE brands on Meta's official Cloud API — correct template categories, the buttons, and the inbox behind them. Messages at Meta's rate with zero markup, from $149/month.
Frequently asked questions
Can multiple salespeople use one WhatsApp number?
Yes, on the WhatsApp Cloud API. The number belongs to the business, conversations arrive in a shared team inbox, and assignment is handled by your system rather than by a handset. The free WhatsApp Business app is built around one primary device with a limited number of linked devices and has no concept of assigning a conversation to a person.
Should salespeople use their personal WhatsApp for leads?
No. The conversation history leaves with the employee when they resign, you cannot reassign a thread, you cannot audit what was promised, there is no coverage during leave, and bulk outreach from a personal number is what WhatsApp's automated enforcement is designed to stop.
How should WhatsApp leads be routed in the UAE?
Language first, because a customer who opens in Arabic and gets an English-only agent is lost regardless of product knowledge. Then area or emirate, then product line, then the ad campaign that produced the lead, then any existing relationship, with round-robin only as the fallback.
Does reassigning a WhatsApp conversation cost anything?
No. The 24-hour customer service window belongs to the phone number, not to the agent, so handing a conversation from one salesperson to another does not restart billing or require a new template.
Related: do I need the WhatsApp API, or is the free app enough?
