Routing and Assignment Rules for Multi-Location Canadian Businesses
Send every message to the right branch, team or agent: routing by location, language, channel and topic, with fallbacks so nothing sits unanswered.
In this article
Routing and Assignment Rules for Multi-Location Canadian Businesses
A customer in Moncton texts the number on your invoice. It lands in a shared queue where an agent in Calgary picks it up, does not know which branch serves that address, and replies with the wrong hours. Meanwhile a French enquiry from Trois-Rivières sits for two hours because the only bilingual agent on shift never saw it. Neither is a staffing problem. Both are routing problems, and message routing rules are the cheapest fix available to a multi-location business in Canada.
Routing is the layer that decides who owns a conversation the moment it arrives. Get it right and a national business with branches in four provinces feels like one competent company to the customer. Get it wrong and you get the two symptoms every operations manager recognizes: conversations nobody claims, and conversations three people answer at once. Canada adds two wrinkles that most routing advice ignores — language preference is a first-class routing dimension here, and time zones stretch four and a half hours from St. John's to Victoria, so "the team" is never all online at the same moment.
This guide covers the dimensions worth routing on, the assignment strategies behind them, the permissions that keep branches separated, and the fallbacks that stop a conversation from ageing out in silence.
The routing dimensions that actually matter in Canada
Most teams over-engineer this. Five dimensions cover almost every real case.
Location or service area. Postal code prefix, the phone number the customer messaged, or the branch selector on a web form. The forward sortation area — the first three characters of a postal code — is usually enough to decide which branch owns a lead. Do not try to route on a full address the customer has not given you yet.
Language preference. English or French, stored on the contact record so it survives the conversation. A francophone customer who asked once should never have to ask again. If you have not standardized on how you capture and store that, start with bilingual customer service in English and French.
Channel. SMS and web chat carry an expectation of a quick reply. Email tolerates a longer window. Routing by channel lets you staff the fast queues properly instead of averaging everything together.
Topic or department. Sales, service, billing, warranty, careers. Either the customer picks it, a bot classifies it, or the intake form sets it.
Existing account ownership. This one overrides the rest. If a customer already has a rep, the conversation goes to that person regardless of what the postal code says. Breaking an established relationship to satisfy a round-robin rule is how you annoy your best accounts.
Assignment strategies
Once a rule has picked a queue, something has to pick a person.
| Strategy | How it works | Best for | Watch out for |
|---|---|---|---|
| Round robin | Next conversation to the next available agent in order | Inbound sales where any rep can take any lead | Ignores how loaded each agent already is |
| Load balanced | Assigns to whoever has the fewest open conversations | Support teams with variable handling times | One slow agent can look "available" while stalled |
| Sticky ownership | Same customer always returns to the same agent | Account management, brokerage, B2B service | Breaks when that person is away — needs a fallback |
| Skill-based | Matches a tag such as French, commercial, or a product line | Bilingual teams, technical products | Small skill pools become bottlenecks |
| Manual pickup | Conversations sit in a visible queue, agents claim them | Small branches, low volume | Cherry-picking; the hard ones age |
| Location queue | Routed to a branch, then assigned inside it | Franchises and retail chains | Needs a national fallback for after hours |
In practice most multi-location businesses run a hybrid: sticky ownership first, skill-based second, load-balanced last.
Fallbacks, or what happens when nobody is there
A routing rule without a fallback is a trap. Every rule needs an answer to three questions: what if the assigned agent is away, what if nobody in that queue is online, and what if the conversation is simply not answered.
- Away status. When an agent marks themselves away or their shift ends, their new assignments divert to the branch queue automatically. Existing threads stay visible so the covering agent has full history.
- Empty queue. If the Halifax queue has nobody online at 8:00 a.m. Atlantic, route to the national queue rather than letting it sit. A customer does not care which office replies.
- Escalation timer. If a conversation has no first reply within your target, reassign it and notify a supervisor. Set the timer per channel — tighter for text and chat, looser for email.
- After-hours capture. Outside business hours, send an honest auto-reply with the real reopening time in the customer's time zone and hold the conversation in an overnight queue. The mechanics are covered in after-hours coverage across Canadian time zones.
- Unroutable messages. Anything the rules cannot classify goes to a triage queue that one named person checks. Never to "everyone".
A routing rule table you can copy
| Condition | Action | Fallback |
|---|---|---|
| Contact has an assigned account owner | Assign to that owner | Owner away → their team queue |
| Language field = French | Assign to bilingual queue | No bilingual agent online → national queue, send French holding message |
| Postal code starts with V | Assign to B.C. branch queue | Outside B.C. hours → Ontario queue |
| Message contains "invoice", "billing", "facture" | Assign to billing queue | Unanswered 4 hours → supervisor |
| Channel = web chat, business hours | Load-balanced to live chat team | Nobody online → offer text handoff |
| Channel = SMS to the service line | Round robin, service team | No reply in 15 min → escalate |
| Source = careers form | Assign to HR queue | Unanswered 24 hours → HR manager |
| Nothing matched | Triage queue | Checked hourly by the duty lead |
Permissions: branches should not read each other's mail
Routing decides where a conversation goes. Permissions decide who can see it at all. For franchises, dealer networks and independently owned branches this is not a nicety — a franchisee's customer list is their asset, and one location browsing another's conversations is a genuine dispute waiting to happen.
Set it up so each location has its own workspace containing only its channels and contacts. Give regional managers read access across their region, head office a full view, and front-line agents access to their own workspace only. Where a customer legitimately moves between branches — a national commercial account, say — transfer the conversation explicitly rather than opening the walls. Omnifox handles this with per-workspace permissions, so an agent in Surrey opening the inbox simply does not see Winnipeg's conversations. Retail chains running the same structure across dozens of stores will find more detail in multi-location customer service for Canadian retail chains.
Worked example: a franchise with locations in four provinces
Take a home services franchise with corporate-owned locations in Ontario and Alberta and franchised locations in Quebec and Nova Scotia. One national toll-free number, one website, four sets of local hours, two languages.
- One intake, many owners. All channels land in Omnifox. The first rule checks the postal code the web form captured, or asks for it by text if the customer messaged the toll-free number cold.
- Language before location. French conversations from any province route to the Quebec team's bilingual agents first, because that pool is where the capability lives, then transfer to the servicing branch with a note.
- Franchise separation. Each franchise is its own workspace. Corporate sees aggregate reporting but not the message bodies of franchise conversations.
- Time-zone chaining. Atlantic opens first and takes national overflow until Ontario is online; Alberta covers the tail end of the day.
- Escalation. Anything unanswered for thirty minutes during business hours pings the branch manager; four hours pings the regional lead.
Real message examples
The routing is invisible to the customer. What they see is wording, so write it deliberately.
Location capture by text: "Thanks for texting Northgate Home Services. So we can send the right local team — what's the postal code for the service address?"
Language check on first contact: "Bonjour / Hi! Préférez-vous continuer en français ou en anglais? Would you prefer French or English?"
Transfer between branches: "I've passed this to our Dartmouth team, who look after your area. Marie will pick it up from here — she can see everything we've discussed, so you won't need to repeat anything."
Escalation acknowledgement: "Apologies for the delay on this one. I've taken it over from my colleague and I have the full thread. To confirm: you need the warranty claim reopened on invoice 44120, correct?"
Internal note (not sent): "Commercial account, national contract. Do not reassign by postal code — always route to Dev on the corporate team."
Frequently asked questions
What is message routing in a shared inbox?
Message routing is the set of rules that decide which team, branch or agent owns an incoming conversation, based on conditions such as postal code, language, channel or topic. It runs the moment a message arrives, before any human sees it, and it should always end with an assigned owner or a visible queue rather than an unowned message.
How should a multi-location business route by language?
Store a language preference on the contact record and route French conversations to a bilingual queue before applying any location rule. Language capability is usually scarcer than geographic coverage, so it should be the higher-priority condition, with the servicing branch brought in afterwards by transfer.
Round robin or load balancing — which is better?
Load balancing is better for support, round robin is better for inbound sales. Support conversations vary wildly in handling time, so counting open conversations reflects reality better than counting turns. Sales teams usually want a fair distribution of opportunities, which is what round robin gives.
Can one branch see another branch's conversations?
Only if you let it. Workspace-level permissions let each location see its own channels and contacts and nothing else, with regional and head-office roles layered above. For franchise networks, separating workspaces should be part of the initial configuration rather than something you fix later.
Getting your routing rules in place
Start with three rules, not thirty: account ownership, language, and location. Add an escalation timer, name the person who checks the triage queue, and only then start refining. Routing rules that nobody understands get switched off within a month, and a simple set that everyone can explain will outperform a clever one that nobody trusts.
Omnifox gives you routing, assignment, workspace permissions and escalation timers across SMS, email, web chat, WhatsApp, social DMs and voice in one inbox. Start a free trial at omnifox.io/register, or compare what each plan includes on the pricing page. If you are configuring this as part of a wider launch, pair it with the 30-day shared inbox rollout plan for Canadian teams.
Ready to try it in your business?
Bring WhatsApp, Instagram, Messenger, email and calls into one inbox, and let AI handle the first reply. Set it up today.
7 days free. No credit card required.
Read more
-

WhatsApp CRM in South Africa: 2026 Guide to Sell More
-

How to Close a Sale on WhatsApp Step by Step (Practical Guide)
-

What Is a Macro in Customer Support
-

WhatsApp Calling in the UAE: Providers and Availability
-

How to avoid getting your WhatsApp number banned (anti-ban guide)
-

How to Build a WhatsApp Chatbot Without Coding
-

The Best Sales CRM in 2026
-

How to Use One WhatsApp Number With Multiple Agents
Comments (0)
No comments yet. Be the first to share your thoughts.
Leave a comment
Your email is never published. Comments are moderated before appearing.