What does routing actually mean on a WhatsApp channel?
On email, routing is mostly filing. A message lands in a folder and waits, and nobody is surprised if the reply comes tomorrow. WhatsApp behaves differently. A thread is a running conversation attached to a phone number, the customer expects a reply in roughly the rhythm of a text to a friend, and the thread never really closes. So routing here is about ownership of a live conversation rather than placement of a document, and it breaks into three decisions.
Classification is the first: what is this message about, and who is sending it. Assignment is the second: which person or team becomes responsible for the next reply, and how they find out. Continuity is the third, and it is the one most often skipped. When a conversation moves from a bot to a person, or from support to sales, the new owner should open it and see everything already said, including what the customer was asked and how they answered.
Continuity matters more on WhatsApp than on most channels because of the platform's reply rules. Free-form replies are only possible for a limited period after the customer's last message. Once that period lapses you are pushed into pre-approved template messages, which read like marketing and rarely restart a real conversation. A routing setup that parks threads in an unassigned pile is therefore not just untidy. It quietly burns the window in which you were still allowed to answer like a human.
Which routing rules are worth building first?
Most teams over-build this. A rule that fires once a month adds a thing every person has to remember, so start with the conditions that describe the bulk of your inbound messages, then stop.
Topic or intent comes first. Messages like where is my order, I want to change my booking, do you deliver to my area and I have a question about an invoice usually map cleanly onto teams you already have. Write the rule in the customer's words rather than your internal department names, because what is being matched is what the customer typed, not your org chart.
Known customer versus new enquiry is the second rule, and often the most valuable. A recognized number with a recent issue belongs with whoever handled it last. An unknown number asking about price belongs with sales right away, while they are still typing and still comparing you with someone else.
Language is third. If part of your customer base writes in another language, detecting that from the first message and routing accordingly saves a round of awkward apology. Business hours and time zone are fourth: the same message should reach a different owner at nine in the morning than at eleven at night, and the night-time path needs a defined behavior rather than an empty room. Account ownership is fifth. For anything resembling B2B, the assigned rep should get their own accounts, which means the routing layer has to read from your CRM rather than guess.
Five rules in that order will cover most of what arrives. Anything beyond them should earn its place by pointing at real conversations that went to the wrong person.
How do you route when one WhatsApp number serves the whole company?
This is the normal situation for a small or mid-size business, and it is the right one. Customers remember one number. What you need is not more numbers but a shared inbox where several teammates work the same number without colliding: visible assignment, private internal notes, mentions to pull a colleague in, and a status that says whether a thread is waiting on you or on the customer.
The practical obstacle is usually pricing rather than technology. When a help desk charges per agent seat, owners respond by buying as few seats as they can, which concentrates every WhatsApp thread on two overloaded people. Routing rules cannot help if there is nobody to route to. The same thing happens with per-resolution pricing, where handing more conversations to automation raises the bill, so teams throttle the automation that was supposed to absorb the routine work.
This is why flat pricing changes the shape of the setup. Corebee is a flat $99 per month with unlimited teammates and unlimited AI conversations, with no per-seat and no per-resolution charge, so putting the warehouse supervisor and the weekend part-timer into the rotation costs nothing extra. Whatever tool you choose, work out the seat question before you design the routing, because the pricing model decides how many destinations your rules are allowed to have. A shared inbox with three real owners routes better than a clever rule set with one.
Should the first responder be a menu or AI intent detection?
Keypad menus are predictable and easy to reason about. Press one for orders, press two for billing. They also get ignored. People on WhatsApp type what they want, often in a run-on sentence with two questions and an order number in it, and a menu answers that with a prompt to please choose a valid option.
Intent detection reads the message instead. The assistant works out what the person is asking, answers it if the answer exists in your material, and routes if it does not. The part that makes this trustworthy is the handoff condition: it should pass the conversation to a person whenever the customer asks for one, and whenever it is not confident, rather than improvising. Most of the damage done by support bots comes from confident wrong answers, not from honest escalation.
The quality of that first step depends almost entirely on what the assistant reads. Pointing it at your website and a maintained knowledge base is the work that decides whether routing is even needed, because a question answered correctly on the spot never has to be assigned to anyone. Treat your help content as the routing layer's training material, and keep a simple hybrid where the assistant asks one clarifying question when a message could belong to two different teams. Setting this up on a WhatsApp number is configuration rather than development work.
What should happen when no rule matches or nobody is free?
Every routing design needs an answer for the leftovers, and the answer should never be an unassigned queue. Name a default owner, even if that owner is you. An inbox where someone is accountable for the unclassified pile behaves completely differently from one where everybody assumes somebody else saw it.
Out of hours needs its own path. The minimum is an immediate acknowledgment that sets expectations honestly, followed by collecting whatever the morning shift will need: the order number, the address, the nature of the fault. Better than that is letting the customer finish the job themselves, which usually means booking a time. Corebee books meetings through Cal.com or Calendly and syncs what it learned to HubSpot, Salesforce, Pipedrive, monday or Zoho, so the conversation becomes a calendar entry and a CRM record rather than a note somebody has to retype. Phone overflow deserves the same treatment, with an AI receptionist that identifies itself as an AI, takes the detail and routes the follow-up into the same inbox as the chats.
Stale assignment is the other leftover case. Treat an assignment as a claim with a timer: if the owner has not replied within the period you choose, the thread returns to the team queue or moves to a named backup. One person being in a meeting should not be the reason a customer waits.
How do you keep routing accurate once it is live?
Reassignments are your measurement. Every time a human moves a conversation from one owner to another, somebody has labeled a routing mistake for you at no cost. Read those cases once a week and you will see which rule is too broad, which team name no longer matches reality, and which question keeps arriving in a form nobody anticipated.
When you find a misroute, fix the content before you add a rule. A large share of wrongly routed conversations are really questions your help material answers badly, and an article rewrite removes the conversation entirely rather than redirecting it. Prune aggressively. Rules rot faster than people expect, especially after a product change or a staff change.
Route to roles rather than individuals wherever you can, because individuals go on holiday and leave. And test the way a customer would: message your own number from your own phone, in the sloppy phrasing a real person uses, and see where you end up.
What do the main WhatsApp routing tools do differently?
The options are genuinely different in character, and the right pick depends on how structured your team already is.
Zendesk and Freshdesk come from the help desk tradition and bring mature skills-based routing, queues, service level targets and reporting. Both reward teams with defined roles and someone willing to own the configuration, and both are typically priced per agent. Intercom leans toward product-led companies with an in-app audience and a strong AI agent story, with pricing that moves with seats and automated resolutions. Gorgias is built around ecommerce, so routing can use order data from Shopify and similar platforms, which is exactly right for a store and less relevant outside retail. Chatwoot is open source and can be self-hosted, which appeals if you want to own the data and have the technical capacity to run it. Help Scout is deliberately simple and email-first, favored by teams that care about tone over workflow depth. Tidio sits at the lightweight end, quick to add to a small store for live chat and basic bots.
Against that field, Corebee is a flat-rate option with web chat, email, voice, WhatsApp, Slack, Facebook, Instagram, SMS and Telegram all live, which matters because routing rules built per channel diverge over time. If you are mapping the trade-offs in detail, a side-by-side read of the Zendesk alternatives is the shorter route than trialling seven tools. Whichever you choose, judge it on two questions: can every person who should receive a WhatsApp thread actually have an account, and does the next owner see the whole conversation when the thread arrives.