Multi-Number WhatsApp Setup: One Team, Many Numbers
One shared inbox, several WhatsApp numbers, and routing rules to match.
Growing past one WhatsApp number is usually less about volume and more about identity — a sales team and a support team don't want to share one inbox, and a business with a US and a UK presence doesn't want every customer routed through a single time zone. Multi-number WhatsApp setups solve both problems without splitting your team across separate tools.
WaSMS lets you connect several WhatsApp numbers to one workspace, so every conversation — regardless of which number it came in on — lands in the same shared system, with its own routing, reporting, and AI behavior per number.
When multiple numbers help
A few situations where a second (or fifth) number earns its place:
- Separate departments — sales and support get different numbers so customers self-select which team they're talking to, and each team's SLAs and staffing can be tracked separately.
- Regional presence — a US number and a UK number, each with a local-looking area code, routed to whichever team covers that region's hours.
- Product lines or brands — an agency running WhatsApp for multiple clients, each with its own number, inside one WaSMS account rather than juggling separate logins.
- Load spreading — very high-volume senders sometimes split broadcast traffic across numbers to stay comfortably within WhatsApp's messaging limits per number.
An example: an agency called Bright Signal manages WhatsApp for six clients. Instead of six separate tools and six separate logins for their team, every client's number connects into one Bright Signal WaSMS workspace — team members see only the numbers they're assigned to, but management gets one dashboard across all six.
Adding a second number
From Settings → Channels, click Add number and choose how it connects — either the official WhatsApp Cloud API route, or a gateway on your own device if you're using your own phone or SIM as the connection. Each number pairs independently, with its own QR scan or API credentials — there's no limit on how many you connect from WaSMS's side; the practical ceiling is how many numbers you can manage and staff sensibly.
One practical note: each additional number still needs its own connection — its own SIM and Android gateway if you're using the free bring-your-own-phone route, or its own Cloud API registration if you're going through Meta directly. Budget for that when planning how many numbers to add; the WaSMS side is free either way, but each number is still a real phone line or Cloud API registration to keep running.
Routing rules by team, region, or product
Once more than one number is connected, routing decides where each incoming chat goes. In WaSMS you can set rules based on:
- Which number received the message — anything to the support number goes to the support team's queue, sales stays with sales.
- Time of day / region — route the UK number's chats to whichever agent group is on shift for that time zone.
- Keyword or AI-detected intent — even within one number, WaSMS's AI can read the first message and route "I want a refund" differently from "do you ship to Canada."
Rules stack, so you can combine "this number" with "this time of day" with "this detected intent" for fairly precise routing without writing any code.
The goal of routing isn't more rules — it's fewer chats sitting in the wrong queue. Start with one rule per number and add complexity only when you see a real bottleneck.
Shared inbox view
Even with several numbers connected, agents work from one inbox. WaSMS shows which number each conversation came in on with a small tag or color, so a support agent covering two brands can tell at a glance which one they're replying as, without switching accounts. This is the same underlying inbox used to combine WhatsApp with SMS and email — see the unified inbox guide for how that works across channels, not just across numbers.
Because the inbox is shared, a customer's history stays attached to their contact record even if they've messaged more than one of your numbers over time — useful for agencies managing several client-facing lines where a contact might reasonably reach out to two different numbers over the life of the relationship. This is also where WaSMS's CRM view pulls its timeline from — one contact, one history, regardless of which number they used.
Per-number analytics
Reporting breaks out by number as well as in aggregate: response times, resolution rates, message volume, and AI-handled versus escalated percentage, each filterable to a single number or rolled up across all of them. This is what makes multi-number setups useful for management, not just routing — you can see that the UK number's average response time is slipping without it being buried inside a combined average. These per-number breakdowns feed directly into the reporting section of our WhatsApp customer service playbook.