A lead fills in the demo form on Monday. On Tuesday, can you show that a person on your team has it?
A routing rule tells you where a lead should go. Whether it arrived is a separate question. The rule says demo requests go to the West team within a day, and the CRM has no report that lists the requests that never arrived.
This guide covers what lead routing is, how it works in HubSpot and Salesforce, what routing software should do, and how to check each day that every lead reached a person. The method is the Magnetiz Lead Routing Playbook, with a worksheet for each step.
What is lead routing?
Lead routing is the set of rules that decides what happens to a new lead and who owns it. It covers which leads go to sales, which go to marketing emails, which are left alone, and which named person is responsible for the next step.
Routing has three parts. Qualification decides what the lead is. The route decides what happens to it. Assignment decides who holds it.
Teams often build only the third part. A round robin spreads every form fill across the reps, and a student researching a paper gets the same treatment as a VP asking for pricing.
Good routing settles the first two parts before it picks a person. It also covers every way a lead can come in. That list is usually longer than the demo form, and includes resource forms, chat, meeting bookings, product sign-ups, shared inboxes, event lists and referrals.
Watch for a routing design that starts with the reps. Start with the list of sources, because a rule can only act on a lead that reaches it.
How does lead routing work in HubSpot?
In HubSpot, lead routing runs in workflows. A form submission or a property change enrolls the record, and workflow actions set its owner. The Rotate record to owner action spreads records across a list of users or a team.
HubSpot's documentation says that action needs a Sales Hub or Service Hub Professional or Enterprise subscription, and that a user needs an assigned Sales or Service seat to be in the rotation.
Three places deserve a look before you trust a HubSpot routing workflow.
- Enrollment. The workflow only acts on records that meet its trigger. A lead created by an import, an integration or a second form may never enroll.
- Branch order. If and then branches run top to bottom. A lead that matches no branch falls out with no owner unless you add a final branch that catches it.
- The spam folder. HubSpot holds submissions it flags as spam on a separate page. Its documentation lists "Unregistered Site Domain" as a spam type for forms embedded on a site whose domain has not been added to the account, and says unreleased spam is deleted after 90 days. A held submission creates no contact and triggers no workflow until someone releases it.
Watch for a domain change, a new landing page tool or a redesigned site. Each one can move real submissions into the held folder without an error anywhere.
How does lead routing work in Salesforce?
In Salesforce, lead routing runs on lead assignment rules. One rule is active at a time, its entries are checked in order, and the first entry that matches assigns the lead. Entries can assign to a user or to a queue.
Salesforce's documentation is specific about the lead that matches nothing. When no entry matches, a web lead goes to the default lead owner set in Lead Settings.
That default is the fallback, and it is worth opening the setting to see whose name is in it. It is often the admin who set the org up years ago.
Teams that need more than ordered entries add Flow, or a routing product on top. The same three questions apply to any of them. Which leads does it see, what order are the rules checked in, and where does a lead go when no rule matches?
Watch for an assignment rule that was edited by adding entries at the bottom. Order decides the result, so a broad entry near the top can swallow leads a newer entry was written for.
What should lead routing software do?
Lead routing software should match a lead to its account, apply rules in a stated order, assign a named owner, alert that owner, and keep a record of which rule fired. A CRM's built-in tools do some of this, and dedicated products do more of it.
Whatever you use, test it against six jobs.
| Job | The question to ask |
|---|---|
| Match | Does it check for an existing contact, account or open deal before it creates anything? |
| Order | Can you read the rules in the order they are checked, and does the first match win? |
| Fallback | Where does a lead go when no rule matches, and who is that person today? |
| Alert | Does the owner get the lead with context, in the channel they already read? |
| Record | Can you see, for any lead, which rule fired and when? |
| Proof | Can you count the leads that came in and the leads that reached an owner, and compare? |
Most tools are strong on the first four. The last two decide whether you can trust the rest.
Watch for a demo that shows the rule builder and never shows a lead that failed. Ask to see what the tool does with a lead that matches nothing.
What are lead routing best practices?
The practices that hold up are the ones that keep unknowns visible and keep a person on the uncertain calls. Six of them carry most of the weight.
- List every source first. Each one gets a row, a count of its own and a named owner of the connection to the CRM.
- Score fit and intent apart. Fit is who the lead is. Intent is what they did. One combined number lets a busy scraper outrank a quiet buyer.
- Score an unknown as unknown. A signal you could not verify is null. Zero means you checked and the answer was bad. Two or more unknowns on the fit side send the lead to a person.
- Write the assignment rules in order. Existing account owner, then open deal owner, then named accounts, then territory, then round robin, then a named fallback.
- Check review first. Conflicting evidence, an unclear duplicate and a score near a band edge go to a person before any rule routes them.
- Earn unattended routing lane by lane. Each lane starts with a person confirming every route. It runs alone only after a streak of confirmed routes, and one changed route resets the streak.
If an AI model helps, give it the reading. It can summarize the company and propose a score. The route and the owner are set by the rules, in the CRM or in code.
The HubSpot Lead Scoring Playbook covers how to build the fit and engagement scores themselves.
See all six steps in the playbook →
Watch for the no fit lane. A buyer wrongly marked no fit is served politely and never followed up, and no report shows it. That lane earns unattended routing last.
How do you know your lead routing is working?
You know lead routing is working when the number of leads counted at each source matches the number that reached an owner and were touched inside your time limit, every day. The count has to start at the source. A count taken inside the CRM only covers the records the CRM holds.
A routing failure rarely shows an error. The playbook names five places a lead can stop.
| Where a lead stops | What it looks like | How to see it |
|---|---|---|
| At the source | The form tool holds the submission or files it as spam | Read the source's own log and its held folder |
| Between tools | The connector reports success and the CRM has no record | Compare the source count with the CRM count |
| In the CRM, no route | The record exists and no rule matched it | List yesterday's records with no route value |
| Routed, no owner | A route is set and the owner is blank or inactive | List routed records with no active owner |
| Owned, untouched | An owner is set and nothing happened inside the limit | List qualified records past the limit with no activity |
The daily read is one row per source. Counted at the source, held at the source, in the CRM, routed, owned, touched. The gap is the first number minus the last, and every lead in the gap gets a name and a reason.
Here is an invented example. Northgate Freight Software runs a demo form, a guide form and chat. On Tuesday the CRM shows 15 new leads from Monday, all routed. The read finds three problems.
- The demo form counted six submissions and the CRM held four. Two sat in the form tool's spam folder after a domain move, and one was a real request from a 200-person company.
- One demo lead was routed to a rep who left last month. No fallback owner was named.
- Chat sent zero leads on a day it normally sends two to five. A test message showed the widget had lost its connection to the CRM.
None of the three produced an error. The CRM's count was correct for the records it held. The source count is what showed them.
Two more habits keep the check honest. Send a test lead through each fragile source once a week and after any change to a form, a domain or a connected tool. And treat a zero from a source that normally sends leads as a finding until it is explained.
Once a week, read the routing itself. Time from arrival to first touch, the share of qualified leads touched inside the limit, the age of the review queue, and the routes a person changed, lane by lane. Once a month, join each route to what happened next. A meeting that came from the nurture or no fit lane is a lead the rules ranked too low.
Watch for a quiet week. A quiet week and a broken path look the same on a dashboard.
The pattern across the six steps
Every step replaces an assumption with a count. The inventory counts the sources. The scores keep unknowns as unknowns. The assignment order ends in a named person. The review queue records why a person decided. The landed lead check compares two counts, and the routing read joins routes to results.
The playbook has the worksheet for each step, five sample leads with an answer key, and the Northgate day in full.
Get the Lead Routing Playbook →
Frequently asked questions
What is lead routing?
Lead routing is the set of rules that decides what happens to a new lead and who owns it. It has three parts. Qualification decides what the lead is, the route decides what happens to it, and assignment decides which person holds it. Good lead routing covers every source a lead can come in through, and it ends each path with a named owner.
How does HubSpot lead routing work?
HubSpot lead routing runs in workflows. A form submission or property change enrolls the record, and actions such as Rotate record to owner set the owner. HubSpot's documentation says that action needs a Sales Hub or Service Hub Professional or Enterprise subscription and an assigned seat for each user in the rotation. Check enrollment triggers, branch order and the spam submissions page before trusting a HubSpot lead routing workflow.
How does lead routing work in Salesforce?
Lead routing in Salesforce runs on lead assignment rules. One rule is active at a time, its entries are evaluated in order, and the first matching entry assigns the lead to a user or a queue. When no entry matches, a web lead goes to the default lead owner in Lead Settings. Many teams add Flow or a routing product when ordered entries are too limited.
What should lead routing software do?
Lead routing software should match a lead to existing records, apply rules in a stated order, assign a named owner, alert that owner with context, and record which rule fired. It should also let you compare the leads that came in with the leads that reached an owner. Ask any lead routing software vendor to show what happens to a lead that matches no rule.
What are lead routing best practices?
Lead routing best practices start with a list of every lead source. Score fit and intent apart, keep an unverified signal as unknown, write assignment rules in the order they are checked, and name a fallback owner. Send uncertain leads to a person, and let a lane run unattended only after a streak of routes a person confirmed.
How do you know your lead routing is working?
Lead routing is working when the leads counted at each source match the leads that reached an owner and were touched inside your time limit. Run that comparison every business day, starting from the source's own count. Read the form tool's held or spam folder each time, and send a test lead through fragile sources weekly.
Why do leads go missing without an error?
Leads go missing without an error because each tool in the path only reports on its own step. A form tool can hold a submission as spam, a connector can report success with no record created, and a rule can assign a lead to an inactive user. Each step looks fine alone. Comparing the count at the source with the count at the end of the path is what shows the gap.