What is lead routing?
Lead routing is the set of rules that decides who in your team receives each new lead, and how quickly they’re told about it. Good routing gets a lead to someone who can actually help them, within a time you’ve agreed, with enough context to act. Bad routing sends it to a default owner, a person on holiday, or nowhere at all.
Most companies don’t think about routing until it fails. A lead fills in the demo form on Friday at 5pm, is assigned by round robin to a rep who’s on leave the following week, and nobody notices until the prospect emails again ten days later, by which time they’ve booked a call with a competitor. The routing technically worked. It just had no idea who was available.
This guide covers the design of routing, which applies to any CRM. For HubSpot-specific setup, see our guide to HubSpot lead routing.
What a routing system actually includes
Routing is often described as “assign the lead to an owner”. In practice it’s a chain of steps, and any of them can break:
- Capture. The lead arrives through a form, chat, booking tool, import or integration.
- Clean and enrich. Values like country and company size are normalized or filled in so the rules have something to work with.
- Match. Is this person or their company already in the CRM, and already owned by someone?
- Filter. Is it spam, a student, a job applicant, a competitor or an existing customer with a support question?
- Assign. Apply the routing rules and set the owner.
- Notify. Tell the owner, through a channel they actually watch.
- Monitor. Check the lead is followed up within the agreed time, and escalate if not.
When we look at routing problems, step 3 and step 7 are missing far more often than the assignment rules themselves.
Why routing should check existing accounts first
Routing should check for an existing relationship before applying any other rule, because a lead from a company you already work with almost always belongs with the person who knows that account.
Without matching, this happens: a new contact from a current customer fills out a pricing form. Round robin assigns them to a new-business rep, who calls them as a cold prospect, while the account manager has no idea a buying signal just came in. The customer gets two conversations that don’t know about each other.
Matching usually works on email domain to company domain. Watch for the edge cases: personal email addresses can’t be matched by domain, large organizations often have several domains, and agencies or consultants may use their own domain while buying for a client. Decide what happens when a match is uncertain. Sending those to a short review queue is often better than guessing.
Common routing methods
Most routing combines two or three of these.
Territory. Leads go to the owner of a region, country or state. Simple and easy to explain, but dependent on a clean country field. Blank or misspelled countries all fall to the default.
Segment or company size. Larger companies go to senior reps or an enterprise team, smaller ones to an inside sales queue or self-serve nurture. Needs reliable company size data, which usually means enrichment.
Product or interest. Leads who asked about a specific product or service go to the specialist. Works best when the form asks directly, rather than inferring interest from page views.
Round robin. Leads are rotated evenly across a group. Fair and easy, but blind to availability, workload and skill unless you add those checks.
Weighted distribution. A variation where some reps get more leads than others, for example new hires getting a smaller share while they ramp up.
Named or strategic accounts. A list of target accounts that always go to a specific owner, regardless of other rules.
Rule order matters more than the rules
Routing rules are evaluated in sequence, and the first match usually wins. Put the most specific rules first and the most general last. A typical order:
- Spam and junk filter
- Existing customer or open deal: route to account owner
- Named or target account: route to assigned owner
- Partner or referral source: route to partner manager
- Enterprise size: route to enterprise team
- Region: route to regional team or round robin within it
- Everything else: nurture or a monitored default queue
Salesforce lead assignment rules work this way explicitly, with only one rule active at a time and its entries evaluated in order. Workflow-based routing in other CRMs behaves similarly through branches, but the order is less visible, so it’s worth drawing out.
The most common ordering mistake is putting region before existing-account matching, so a current customer’s new contact goes to whoever covers their country.
What happens when no rule matches?
Every routing system needs a default, and the default needs an owner who checks it. If unmatched leads go to an admin account, a former employee, or “unassigned”, they are effectively lost.
Set the fallback to a real person or a monitored queue, and review its contents weekly. The fallback is also your best diagnostic. If 20% of leads end up there, the rules or the data feeding them need work.
Handling absences, capacity and working hours
Rotation without availability is where good routing designs fall apart.
Out of office. Decide how reps are removed from rotation when they’re away. Some tools read calendar status; most CRMs need someone to update the rotation manually. If it’s manual, make it part of the holiday request process, not something people remember.
Capacity. A rep with 80 open leads shouldn’t get the same share as one with 15. Some teams cap open leads per rep and skip anyone over the limit.
Working hours and time zones. A lead that arrives at 6pm needs a decision. Route to someone in a later time zone, hold for the next morning with a clear SLA, or send an automated acknowledgment with a booking link. Any of these is fine. Doing nothing isn’t.
Reassignment. If a rep leaves, their open leads need to go somewhere deliberately. Bulk reassigning to a manager, who then never redistributes them, is a very common quiet loss.
Notifications and response SLAs
Assigning an owner doesn’t mean the owner knows. Send notifications to where reps actually work, which may be the CRM’s mobile app, a team chat channel, or email. Include the context they need to act: what the lead did, which page or form, company, and any previous relationship.
Then agree a response time by lead type. A demo request might need contact within the same business day. A content download might be fine at three days or with no direct contact at all. Write it down, and add an escalation: if a high-intent lead hasn’t been touched by the deadline, alert the manager or reassign.
Measuring routing
A few numbers tell you whether routing is working:
- Time to first touch by lead type and by rep
- Leads in the fallback queue each week
- Reassignment rate, which shows how often routing got it wrong
- Distribution across the round robin group
- Leads with no activity after the SLA window
You don’t need a dashboard on day one. A weekly look at the fallback queue and untouched high-intent leads catches most problems.
Where to build routing
You have three broad options.
Native CRM tools. HubSpot workflows include a “Rotate record to owner” action and branching logic. Salesforce has lead assignment rules. Zoho and Pipedrive have their own assignment options. Native is easiest to maintain and keeps everything visible in one place. It struggles with complex availability or capacity logic.
Dedicated routing or scheduling tools. These add features like availability-aware rotation, account matching and booking at the point of form submission. They help with complex teams but add another system with its own settings to maintain.
Integration platforms. Zapier, Make or n8n can run routing logic, and webhooks can pass leads to custom code. Flexible, but routing logic hidden outside the CRM is harder for others to understand, and failures are quieter. If you go this way, add error alerts.
The right choice depends more on who will maintain it than on features.
Testing routing before go-live
Before you switch new routing on, push test leads through each path: one per region, each size band, an existing customer, an existing open deal, a personal email address, a blank country, a rep who’s out of office, and a lead arriving outside working hours. Check the owner, the notification, and the time it took.
A lead routing workbook gives you a structure for documenting rules, order, fallbacks and these test cases in one place. Keep it updated as the team changes, because routing rules go stale every time someone joins, leaves or changes territory.
Is round robin a good way to route leads?
It’s a good default for a team of similar reps handling similar leads. It works poorly on its own when reps have different specialisms, territories or capacity, or when leads come from existing accounts. Use it inside a group after the more specific rules have run.
How fast should sales respond to an inbound lead?
It depends on intent. High-intent requests like demos or quotes deserve contact the same business day at the latest. Lower-intent signals like content downloads may not need direct contact at all. The important part is agreeing a target for each type and measuring it.
Should routing happen in the CRM or in a separate tool?
Keep it in the CRM if your rules are simple enough to express there, because it’s easier to maintain and audit. Move to a separate tool when you need availability-aware rotation or matching logic the CRM can’t handle, and document where the logic lives.
How do we stop leads going to people who have left?
Make removing a departing rep from routing groups, workflows and notifications part of the offboarding checklist, and reassign their open records deliberately. Then check the fallback queue for a few weeks afterward.
If your routing has grown into something the sales team no longer trusts, our Lead Routing Automation service rebuilds it around matching, clear rule order, fallbacks and monitoring.