Marketing operations
How to set up lead routing that assigns every lead
Lead routing is the set of rules that decides who owns each new lead and alerts them to follow up. To set it up, choose a routing model, list the fields the rules need, write rules in priority order with a fallback owner, automate assignment in your CRM, Make or Zapier, and test before go-live.
What lead routing is, and how it differs from lead scoring
Lead routing assigns each new lead to an owner as soon as it arrives (or, if you route after qualification, as soon as it qualifies), using rules written in advance: this region goes to that rep, existing customers go to their account manager, and anything the rules miss goes to a named fallback owner. It also alerts the owner, so assignment turns into follow-up.
It is often confused with two related systems:
- Lead routing answers who owns the lead.
- Lead scoring answers how good the lead is, by fit and engagement.
- Lifecycle stages answer when a lead is ready for sales; see how to define MQLs and SQLs.
Common lead routing models
Route after qualification decides when a lead enters routing; the other three decide who gets it. Use one alone, or layer them in this order: existing account owner first, then territory or segment rules, then round robin within each territory, then a fallback owner.
| Model | How it assigns | Works best when | Main risk |
|---|---|---|---|
| Round robin | Rotates leads through a list of reps in turn | Reps and leads are interchangeable | Ignores capacity, time off and fit |
| Territory or segment rules | Matches region, company size, industry or product to an owner | Reps specialize by market or deal size | Blank or messy fields misroute leads |
| Existing account owner first | Sends the lead to the owner of its company record | Accounts have several contacts, or you sell to existing customers | Personal email addresses match no company |
| Route after qualification | Holds leads in nurture until they meet the MQL definition, then routes them to sales | Volume is high and many leads are early-stage | Hand-raisers wait when they should skip the queue |
Round robin
Keep one rotation list, and remove people the day they go on leave or leave the company. For unequal shares, weight the list where your tool allows a name twice (a sheet or data store does): Rep A, Rep A, Rep B gives Rep A two of every three leads. Load-balanced rotation assigns to whoever has the fewest open leads instead.
Territory or segment rules
Write territories as a table (region, company size band, owner) and build one rule per row, on dropdown fields rather than free text. When territories change, update the rules the same day.
Existing account owner first
Match leads to companies by email domain and copy the company owner onto the lead. Exclude free email domains such as gmail.com, and decide in advance who gets leads whose account owner has left.
Route after qualification
Send demo, pricing and contact-sales requests to sales immediately. Everything else waits until it meets your MQL definition, so write that definition down and agree it with sales first.
How to set up lead routing, step by step
Plan the first three steps on paper, build the rules in HubSpot, Make or Zapier (covered in the next two sections), then test.
List the fields routing depends on
Every rule reads a field, so check where each one comes from and how often it is blank; if many are blank, work through the CRM audit checklist first. Use dropdowns or normalized values: a rule looking for "United States" misses "USA". The fields most rule sets need:
- Country, state or region, for territories
- Company size band, for segment rules
- Email domain and associated company, for account matching
- Form or lead source, to separate demo requests from content downloads
Write the rules and a fallback owner
List the rules in order, most specific first; the first match wins. The last rule assigns a fallback owner: a named person who checks that queue daily, not a shared inbox. Each lead landing there reveals a rule gap to fix.
| Order | If the lead | Assign to |
|---|---|---|
| 1 | Belongs to a company that already has an owner | The company owner |
| 2 | Is in North America and has 200 or more employees | Enterprise rep |
| 3 | Is in North America | Round robin: Rep A, Rep B |
| 4 | Is in Europe | Europe rep |
| 5 | Matches none of the above, including a blank country | Fallback owner (sales manager) |
Set a response-time expectation and an alert
Agree a response-time target per lead type with sales, such as one business hour for demo requests and one business day for downloads (illustrative; set yours by what the team can staff).
- At assignment: create a task due at the target and notify the owner by email, Slack or Teams.
- At the deadline: if nothing is logged, alert the owner's manager or reassign the lead.
- Outside business hours: decide whether the clock starts at the next opening.
Test with real records before go-live
Test with the routing values of real leads (country, company size, form or lead source) rather than invented combinations, because real data carries the edge cases. Never reuse a real person's email address: HubSpot, for example, matches contacts on email and would update the live record instead of creating a test one.
- 01Pick about 20 recent leads, including edge cases such as a blank country, a personal email address and an existing customer.
- 02Write down the owner each should get.
- 03Recreate them as test records using test email addresses you control, and point tasks and alerts at yourself while testing. If your CRM links contacts to companies by email domain, check which company each test record was linked to. Run them through and fix every wrong owner, task or alert.
- 04Check that no existing record changed owner, then delete the test records.
- 05Go live on one lead source, watch the fallback queue daily for two weeks, then add the rest.
HubSpot lead routing: workflows and owner rotation
HubSpot lead routing is usually built with workflows. Available actions and record types depend on your subscription, and menus change, so check your portal before designing around a specific action.
If fields, stages or owner records need fixing before routing can run, fix those first; a HubSpot consultant can help with the setup. A typical routing workflow has five parts:
- Enrollment: contacts (or leads, if you use HubSpot's lead object) whose owner is unknown. This catches imports and integrations as well as form fills. If you route after qualification, add the MQL or hand-raise condition to enrollment.
- Company owner first: if the associated company has an owner, copy it onto the contact. If you rely on automatic company association, add a short delay before this branch so the association exists.
- If/then branches that check the remaining routing fields in rule order.
- Owner rotation: the Rotate record to owner action shares records among named users or a team and can skip users marked away. Leave its overwrite option off so returning contacts keep their rep.
- A fallback branch: if the owner is still unknown (say, everyone in the rotation is away), assign the fallback owner. Then, on every path, create the task and internal notification.
Example: the rule set above as a HubSpot workflow
Built from the illustrative two-region rule set earlier in this guide, the workflow checks five branches in the same order as the rules. Every path ends with the same two actions: a follow-up task for the new owner, due at your response-time target, and an internal notification.
| Branch | Condition | Action |
|---|---|---|
| 1. Company owner | The associated company has an owner | Copy the company owner onto the contact |
| 2. North America enterprise | Region is North America and company size band is 200 employees or more | Set the contact owner to the enterprise rep |
| 3. North America | Region is North America | Rotate the record between Rep A and Rep B |
| 4. Europe | Region is Europe | Set the contact owner to the Europe rep |
| 5. Fallback | No branch matched, or the owner is still unknown after rotation | Set the contact owner to the fallback owner (sales manager) |
Automated lead routing across tools with Make or Zapier
Automated lead routing outside the CRM fits when leads come from tools with no native connection to it, when rules need data held elsewhere (say, a territory table in Airtable), or when alerts belong in Slack. Make branches with a router and filters; Zapier uses Paths, filters and lookup tables.
Round robin needs a counter stored between runs, in a Make data store, Storage by Zapier or a sheet: next rep = the rep at position (counter mod number of reps), counting positions from 0. Illustrative example: with Rep A, Rep B and Rep C at positions 0, 1 and 2 and a counter of 7, 7 mod 3 = 1, so Rep B gets the lead and the counter becomes 8.
Read and update the counter in consecutive steps, and in Make turn on sequential processing in the scenario settings, so two leads arriving together do not read the same value. In Zapier, a Delay After Queue step before the counter serves the same purpose.
Search the CRM by email and domain before creating a record, to avoid duplicates. Keep one system in charge of the owner field, because a workflow and a Zap that both assign owners overwrite each other. On any error, assign the fallback owner and alert whoever maintains the scenario or Zap. This is typical Make workflow automation work.
How to tell whether your lead routing works
Check these metrics weekly for the first month after go-live, then monthly. Report time to first touch as a median, since a few overnight or weekend leads distort the average. Illustrative example: first touches at 10, 25, 40, 90 and 600 minutes average 765 ÷ 5 = 153 minutes, but the median is 40 minutes.
| Metric | How to calculate it | What a problem looks like |
|---|---|---|
| Time to first touch | The owner's first logged call, one-to-one email or meeting minus the time the lead was routed, counted the same way as your target (business or calendar hours) | A median above your response-time target |
| Unassigned count | Leads that reached your routing trigger (arrival, or the MQL definition if you route after qualification) and still have no owner one hour later | Anything above zero |
| Fallback share | Fallback leads ÷ all new leads × 100 (illustrative: 12 ÷ 200 × 100 = 6%) | A rising share: the rules miss a type of lead |
| Manual reassignments | Owners changed by hand within 7 days of routing | Rules that do not match how sales works |
Lead routing mistakes that lose leads
Routing depends on clean data and agreed stage definitions, so it belongs with wider marketing operations consulting work rather than a one-off workflow. Check for these mistakes first:
- No fallback owner, so leads the rules miss sit unassigned.
- Rotations that include people on leave or who have left.
- Rules spread across forms, workflows and other automations that overwrite each other.
- Assignment with no alert, so the owner finds the lead days later.
- No written record of the rule order, owner list and fallback owner.
Questions this guide answers
What is the difference between lead routing and lead assignment?
Assignment is the act of setting the owner field. Routing is the rule set around it: account matching, the choice of owner, the fallback when no rule matches and the alert that starts follow-up. The terms are often used interchangeably.
Can HubSpot do round robin lead routing?
Yes. HubSpot workflows include an action that rotates records among named users or a team, and the meetings tool offers round-robin booking links. Which of these your portal can use depends on your subscription.
How does lead routing work in Salesforce?
The design is the same. Salesforce lead assignment rules check their entries in order and assign the lead to the first match; only one lead assignment rule can be active at a time, and the default lead owner in lead settings is the fallback. The rules run automatically on web-to-lead and when a user checks the box to assign using the active rule. Leads created through the API or an integration can skip them unless the integration applies them, so test that path too.
Does a small team need lead routing?
Yes, once two or more people share inbound leads. With one salesperson, still build the fallback and the alert, so a lead from a new form or integration never sits without an owner.
Leads still slipping through?
Bring your routing rules, or a description of how leads get assigned today, to a 20-minute call. I'll show you where leads get lost and what to fix first.
Book a 20-minute lead routing reviewMichelle Ivanova runs imivs consulting, building marketing operations, CRM workflows and reporting automation in the tools a team already uses.