A clinic, salon or repair shop that takes bookings on WhatsApp reaches the same point eventually. Three people can see the chats, nobody knows who is answering which, and a customer asking to move tomorrow’s appointment waits until someone notices. Chat routing fixes that by giving every conversation a named owner the moment it arrives.
Where that rule lives depends on the setup, and on the WhatsApp Business API it is not in WhatsApp at all. The API delivers messages; the inbox connected to it decides who handles them.
- The API doesn’t route chats — your inbox software does
- The free Business app shares chats but never assigns them — up to four linked devices, and everyone sees everything
- Assignment without the API — the app’s paid multi-agent mode, or Meta Business Suite’s Inbox
- Unowned chats run into the 24-hour window — after it closes, only pre-approved templates can go out
Why an unowned chat costs more on WhatsApp
An email can wait until Monday. A WhatsApp chat runs on a clock. Meta’s messaging documentation describes a 24-hour customer service window that opens when a customer messages or calls and resets each time they write again. While it is open, the business can send any kind of reply. Once it closes, it can only send a pre-approved template message.
So a chat left unclaimed overnight and through a busy morning can slide past the window, and a one-line answer becomes a template somebody had to write and submit in advance.
Appointment reminders run into the same rule, since they nearly always go out after the window has closed. How to set them up is in Automated Booking Confirmations and Reminders on WhatsApp.
Where chat routing actually lives
A WhatsApp conversation can be assigned in four places, each suited to a bigger team than the last.
The free WhatsApp Business app: shared, not assigned
The free app lets a small team share one number. WhatsApp’s own inbox guide sets the limit:
The WhatsApp Business app supports up to 4 linked devices on a single number, so multiple team members can view and respond to messages from their own devices.
— WhatsApp Business, “How to organize your inbox and scale your business on WhatsApp”
View and respond is the catch. Everyone sees every chat and nobody owns one. That works for two people at one desk and breaks once someone has to ask “did you get that one?”
Business app multi-agent: assignment on a subscription
WhatsApp now sells assignment inside the app. The Meta Verified page describes the multi-agent account as “connecting multiple devices to your account and assigning chats to your sales agents.” The WhatsApp Help Center puts the ceiling at 10 devices, with an Assign chat option for handing a conversation to any agent. The device count depends on a paid Meta Verified or Meta One subscription.
Meta Business Suite Inbox: one queue across channels
A business app synced to Meta Business Suite can be run from its Inbox, which can assign conversations to a specific person on WhatsApp as well as Messenger and Instagram, so all three channels share one queue.
The WhatsApp Business API: routing is yours to build
The API is where most people expect routing, and where Meta supplies the least of it. Each incoming message is delivered to the business’s own endpoint as a webhook, and that handover is where the platform’s job ends. There is no setting for who owns a chat. Whichever inbox, help desk or CRM receives the webhook runs the routing, so the rules can be as specific as the business needs.
Five routing rules that work
These five cover most appointment-based businesses, roughly in the order to set them up.
- Ask before assigning: open with a short menu: book, reschedule, prices, other. On the API, a reply-buttons message offers up to three choices and a list message handles more. The customer’s tap routes the chat.
- Send returning customers to their last contact: each incoming message carries the sender’s WhatsApp ID, so the inbox can assign the chat to whoever handled that customer before. Nobody has to explain their problem twice.
- Route ad clicks to sales: a message sent from a Click-to-WhatsApp ad carries a referral object identifying the ad. That is enough to route the lead, and later to see which ads brought it in, as Tracking Which Ads Actually Drive WhatsApp Leads explains.
- Give after-hours chats a morning owner: an automatic reply tells the customer when to expect an answer, and an assignment rule makes sure the first person on shift gives it.
- Reassign anything nobody picks up: round-robin spreads the load, but a chat assigned to someone on a break is still a customer waiting. After a set time, say 15 minutes in opening hours, an untouched chat moves to the next person.
A chatbot can field the opening questions, but routing decides who takes over, so it belongs in any plan for WhatsApp automation for business from the start.
Also Read: Automating WhatsApp FAQs Without Losing the Human Touch on Urgent Requests
Key Takeaways
- The API delivers messages; the inbox connected to it does the routing.
- The free Business app shares one number across four linked devices but never assigns a chat.
- Without the API, assignment means the app’s paid multi-agent mode or Business Suite’s Inbox.
- Start with a menu, then add the other routing rules one at a time.
Frequently Asked Questions
Can customers see which team member replied to them on WhatsApp?
No, not by default. For the WhatsApp Business app’s multi-agent setup, the WhatsApp Help Center is explicit: “Customers won’t be able to see which agent or which device a message was sent from.” On the API, every reply also goes out from the same business number, so a name only reaches the customer if it is in the message itself. A business that wants customers to know who they are talking to has to have agents say so, for example by signing the first reply.
Do team members need their own phone to answer WhatsApp chats through the API?
No. On the API, messages arrive at the business’s own server as webhooks and replies go out through the API, so staff answer inside whatever inbox the business connects, usually in a web browser. That is a real difference from the WhatsApp Business app, where each person works from a device linked to the business account.
Can two different inbox tools receive messages from the same WhatsApp number?
Not through one Meta app. Meta’s webhook documentation allows each Meta app a single endpoint at a time, and sending updates to more than one endpoint takes more than one app. In practice, one inbox should receive the messages and run the routing, with the CRM, booking system and reporting fed from it, rather than two tools competing for the same conversations.
Should each department get its own WhatsApp number?
Usually not. Separate numbers push the routing decision onto the customer, who has to know which number to message, and they split one customer’s history across several threads. Meta caps them too: business portfolios start with two registered business phone numbers, a limit that can be raised to 20. Separate numbers make sense for genuinely separate operations, such as different countries or brands. For departments inside one business, a single number with routing rules keeps each conversation in one place. Branches of one business sit in between; the trade-offs are in WhatsApp Business API for Multi-Branch and Multi-Location Businesses.
Can a chat be handed to a different team member halfway through?
Yes, in every setup that assigns chats at all. The Business app’s multi-agent mode lets you assign a chat to yourself or another agent, Meta Business Suite’s Inbox lets you choose the person a conversation is assigned to, and on the API reassignment is a feature of the inbox software. The customer sees the same thread either way. What a handoff can lose is context, so whoever passes the chat on should leave a note on what has already been agreed rather than make the customer repeat it.
Final Thoughts
Most WhatsApp routing problems are not WhatsApp problems. What is missing is a rule for who owns each chat. Pick the smallest setup that gives every conversation an owner, and add rules when the team outgrows it.
Want every WhatsApp chat landing with the right person?
ClubUnbrick sets up WhatsApp Business API inboxes with routing rules, human handoffs and reporting built around how your team already works.
What We Offer
- WhatsApp Business API setup — Getting approved and connecting a shared inbox your whole team can work from.
- Routing and assignment rules — Menus, returning-customer lookups, ad-lead routing and after-hours ownership.
- Chatbot and handoff design — Automated answers for routine questions, with a clean handover to a person for everything else.
- Response-time reporting — Seeing which chats wait, for how long, and where the rules need adjusting.
You can start with one number and a simple menu, then add rules as message volume grows.
