WhatsApp Business
5 min read

How to Automatically Route WhatsApp Messages to the Right Team, Not One Queue

How to Automatically Route WhatsApp Messages to the Right Team, Not One Queue

Summary

Saysimple's Smart Routing Module sends every incoming WhatsApp message to the right team or person automatically, based on four real triggers: contact information and labels, keyword recognition, opening hours, and template response. Once a trigger fires, the module can assign the conversation to a team, to the most suitable available employee within that team, to one specific person, or attach tags and labels for follow up. This is the mechanism that replaces someone manually reading and forwarding every message, the step that breaks down once more than one team shares a WhatsApp number. It is why 500+ businesses run their WhatsApp on Saysimple today.

TL;DR

  • The Saysimple Smart Routing Module recognizes conversations using four triggers: contact information and labels, keyword recognition, opening hours, and WhatsApp template response.
  • Once a trigger fires, it can assign a conversation to a team, to an employee within that team, to one specific employee, or apply tags and labels.
  • BMN Building Materials centralized 85 branches under one WhatsApp number and routes each conversation to a customer's preferred branch with this module.
  • A shared inbox alone is enough for one team. Once a second team, department, or location answers the same number, the Smart Routing Module is what keeps that number usable.

A business that puts one WhatsApp number on its website usually starts with a single team behind it. Someone reads every message and replies, or a small group shares one shared inbox and sorts things out by eye. That works fine right up until a second team needs the same number, a second location opens, or the volume gets high enough that sorting messages by hand becomes a job of its own.

The fix at that point isn't a bigger inbox or more people watching it, it's the Saysimple Smart Routing Module deciding where each message goes before anyone has to read it. The module looks at signals already available in a conversation, a label already linked to the contact, a word or topic in the message, whether a team is currently within its working hours, or which WhatsApp template a customer just replied to, and assigns the conversation automatically, the same way a phone system routes a call to the right extension instead of ringing every desk in the building.

What follows is exactly which triggers and actions the Smart Routing Module supports, and how one Saysimple customer applied it across 85 locations.

The Four Triggers That Decide Where a Message Goes

A routing rule needs something to route on, and Saysimple's Smart Routing Module works with four of them. Contact information and contact labels route a conversation based on customer type, previous interactions, or labels already linked to that contact, so a returning enterprise account can land with the same team every time. Keyword recognition looks at specific words or topics in the conversation and routes accordingly, which is what separates a sales enquiry from a support question without anyone having to read either first. Opening hours checks whether a team or employee is currently within its working hours before assigning anything to them, so a message sent at 11pm doesn't sit in front of someone who logged off hours ago. Template response is WhatsApp specific: when a customer replies to a particular WhatsApp template message the business sent, that reply automatically triggers routing tied to the original template, which is useful for anything built around an outbound flow, an appointment reminder, a delivery update, a renewal notice.

None of this requires a customer to know routing exists. From their side, they send one message and a conversation opens with someone who can actually help, which is the entire point.

The mistake we see most often is treating this as an inbox permissions question, deciding who is allowed to see which conversations, rather than a routing question, deciding which conversation reaches which person in the first place. Permissions control visibility after a message has already landed somewhere. The Saysimple Smart Routing Module operates at that earlier step, before a conversation ever reaches an inbox view.

What Happens Once a Trigger Fires

Recognizing a conversation is only half the module. The other half is what it actually does with that recognition, and Saysimple built five concrete actions into it rather than leaving that step generic.

TriggerWhat it recognizesFits best when
Contact information & labelsCustomer type, prior interactions, or labels already linked to the contactReturning customers or accounts that should always reach the same team
Keyword recognitionSpecific words or topics detected in the conversationClearly distinct request types, such as sales versus support
Opening hoursWhether a team or employee is currently within working hoursTeams or branches staffed only during set hours
Template responseA reply to a specific WhatsApp template the business sent (WhatsApp only)Follow up flows where the original template already tells you what the reply is about

Once one of those triggers matches, the Smart Routing Module can take any of the following actions:

  • Assign to a team: the whole conversation goes into a specific team's queue.
  • Assign to an employee within a team: the system automatically selects the most suitable available employee in that team, rather than dropping it into a queue for anyone to pick up.
  • Assign to a specific employee: direct routing to one named person, no team queue in between.
  • Assign tags: for follow up and reporting, on top of or instead of a team assignment.
  • Assign labels: internal organization and categorization, so the conversation is easy to find and filter later.

A Real Case: Routing 85 Branches From One Number

BMN Building Materials, an 85 branch building materials wholesaler in the Netherlands, faced a version of this problem at real scale. Customers were actively asking to reach the company on WhatsApp, but a single shared number across that many locations would have meant every branch either fielding messages meant for another location, or the company avoiding WhatsApp altogether to sidestep the mess.

Instead, BMN rolled out WhatsApp in phases, starting with one branch cluster before centralizing under a single number with the Smart Routing Module sending each conversation to a customer's preferred branch, using contact and label based triggers to match a customer to the branch they actually deal with. Web chat was added on top once the routing structure held up. The result, in the company's own account, was smoother and clearer communication with customers, tracked through NPS rather than a single headline figure. What made that possible wasn't the shared number itself, it was the same trigger and action logic described above, running at 85 branch scale.

Getting Your Own Routing Rules Live

A single shared inbox works fine for one team of any size. The signal that the Smart Routing Module is actually needed isn't team size, it's whether more than one team, department, or location now answers from the same number. Before setting up routing rules in Saysimple, decide these rather than mapping every possible rule first:

  • A clear, short list of destinations a message could reach: specific teams, named employees, or tag and label sets, not a vague catch-all.
  • Which of the four triggers each rule should use, contact information or labels, keyword recognition, opening hours, or template response, chosen per destination rather than guessed at once for everything.
  • Which action fires when a trigger matches: team assignment, automatic assignment to the best available employee within a team, direct assignment to one named person, or simply tags and labels for reporting.
  • One fallback destination for anything that doesn't match a rule cleanly, so a message never simply goes nowhere.
  • A live number already active on Saysimple's shared inbox, since the Smart Routing Module sits on top of an existing WhatsApp setup rather than replacing the need for one.

Teams that have already connected WhatsApp to a CRM or helpdesk for customer context often find the Smart Routing Module is the natural next layer: the CRM tells the agent who they're talking to, and the module makes sure that conversation reached the right agent in the first place.

Closing thoughts

Smart routing solves a problem a shared inbox was never built to solve on its own: deciding where a conversation belongs before a person has to figure it out. BMN's 85 branches did not get simpler by adding more people to watch one WhatsApp number, they got simpler once the Saysimple Smart Routing Module did that sorting automatically, branch by branch, using the exact same four triggers and five actions available on any Saysimple account today. That is the setup running behind 500+ businesses on Saysimple right now, and it is available on your number as soon as you turn it on.

Curious what the Saysimple Smart Routing Module would look like across your own teams or locations? Book a demo with Saysimple and we will configure your actual triggers and actions live, on your setup.

Sources

See what Saysimple neo looks like in your business.

Book a 30-minute demo. We'll walk through your use case, whether that's order desk automation, WhatsApp campaigns or ERP integration, and show you exactly how Saysimple neo works for B2B Commerce teams.

Trusted by 500+ customers

KlantKlantKlantKlant