Your leads aren't getting routed, and nobody noticed until a demo request sat untouched for three days. That's how most teams find out. Routing rarely breaks loudly. It breaks quietly, one blank State field or departed rep at a time.
The cause is almost never the routing tool. It's the data feeding your rules, rules nobody has touched since the last reorg, and no safety net for leads that don't match anything. The good news: you can fix lead routing in HubSpot and Salesforce without rebuilding your CRM.
In this article, you will find:
How to audit where your leads actually go
The data fixes that make routing rules work
How to rebuild routing rules in HubSpot and Salesforce
How to add fallbacks, SLAs, and monitoring so it stays fixed
| Symptom | Likely cause | Fix in HubSpot | Fix in Salesforce |
|---|---|---|---|
| Leads sit with no owner | No rule matched and there’s no catch-all | Add a “none met” branch that assigns a default owner | Add a final assignment rule entry with no criteria, sent to a queue |
| Leads land with the wrong rep | Free-text fields (“CA” vs. “California”) break the criteria | Swap routing fields on forms to dropdowns | Use picklists and validation rules on routing fields |
| Customers go to new-business reps | No lead-to-account matching | Route on the associated company owner | Match leads to accounts before assignment rules run |
| Leads stuck with former employees | Rules hard-coded to named reps | Rotate across teams, not named users | Assign to queues, not users |
| Owner flips after every sync | Both systems are assigning owners | Pick one system to route and set the owner field sync rule to match | Same: one owner of record, never two |
Step 1: Audit Where Your Leads Actually Go
Most teams have a mental model of their routing that doesn't match what the CRM is doing. Pull the last 30 days of inbound and compare where each lead should have gone against where it went. You're looking for patterns: unassigned leads, wrong territory, wrong segment, or slow assignment, since each points to a different fix.
Also check for black holes. How many open leads are owned by deactivated users? How many have sat in a queue for weeks with no activity? If you can't answer quickly, that's your first finding.
| What to pull | Where in HubSpot | Where in Salesforce |
|---|---|---|
| Leads with no owner | Contacts view filtered on “Contact owner is unknown” | Lead list view where owner is a queue |
| Leads owned by inactive users | Contacts filtered by deactivated owners | Report on Lead owner where user is inactive |
| Time from creation to assignment | Workflow history plus owner assigned date | Lead field history on Owner |
| Expected vs. actual owner | Export and compare against your routing map | Same, using the assignment rule entries as the map |
Step 2: Fix the Data Your Routing Rules Depend On
Routing logic is only as good as the fields it reads. In Openprise's 2025 State of RevOps survey, 80% of teams reported missing or incomplete data and 75% reported duplicate records. Those are the exact conditions that break routing before a single rule fires.
Start at the form. Any field a rule depends on (State, Industry, Company Size) should be a dropdown, not a text box. Then enrich before you route, not after, and match leads to existing accounts so current customers reach their account owner. Reform suggests aiming for a lead-to-account match rate of 85% or higher.
| Routing field | How it breaks | Fix |
|---|---|---|
| State / Country | “CA,” “Calif,” and “California” all fail the same rule | Dropdown on the form, picklist in the CRM |
| Company size | “~50,” “SMB,” and “fifty” don’t match a 50-employee threshold | Ranges that mirror your segment cutoffs |
| Email domain | Typos and personal emails skip account matching | Validate at capture, then match on domain |
| Industry | Dozens of variations, none exact | Normalize to a fixed list before routing |
Step 3: Rebuild Routing Rules in HubSpot and Salesforce
Most routing rules were built for a sales team that no longer exists. Before you touch configuration, write down your current territories, segments, and specialists, then set an explicit priority order. Account ownership should beat everything, and territory should beat round-robin.
Each platform has its own quirk. In Salesforce, assignment rule entries run top to bottom and the first match wins, so a broad rule placed high quietly swallows everything below it. In HubSpot, one workflow with ordered if/then branches is easier to debug than five workflows racing each other. Either way, test the new rules on a batch of historical leads before they touch live ones.
| Priority | Rule | HubSpot | Salesforce |
|---|---|---|---|
| Priority 1 | Existing account owner | Branch on associated company owner | Match to account, assign to account owner |
| Priority 2 | Intent (demo, pricing) | Branch on form or page, rotate within AE team | Rule entry on lead source, assign to AE queue |
| Priority 3 | Segment or specialty | Branch on size or industry | Rule entry on picklist values |
| Priority 4 | Territory or round-robin | Rotate record to owner within team | Queue plus round-robin logic in Flow |
| Priority 5 | Catch-all | “None met” branch to a default owner | Final entry with no criteria, sent to a review queue |
Step 4: Add Fallbacks, SLAs, and Monitoring So It Stays Fixed
Routing isn't a project you finish. Reps leave, territories shift, and someone adds "just one exception" every quarter. So build the safety net: a backup owner for every territory, an SLA timer that reassigns untouched leads, and a weekly look at the numbers below.
This matters more as routing gets smarter. AI routing agents and intent-based prioritization run on the same CRM data your rules do. As Openprise points out, an agent fed messy records misroutes leads just as confidently as a rule does, only faster. The teams that get value from AI routing next year are the ones fixing their data and ownership logic now.
| Metric | Target | What a miss tells you |
|---|---|---|
| Fallback rate | Under 10% | Your rules have gaps |
| Manual reassignment rate | Under 3% | Rules or form data don’t match reality |
| Lead-to-account match rate | 85%+ | Customers are leaking to new-business reps |
| SLA attainment | Above 80% | Assignment works, follow-up doesn’t |
FAQ
Why are my leads not getting routed in HubSpot?
Usually the workflow never enrolled the contact, because a trigger property was blank or re-enrollment was off. The other common cause is that no branch matched and there's no default. Check the workflow's enrollment history first, then add a "none met" branch with a default owner.
Why isn't my Salesforce lead assignment rule working?
Only one assignment rule can be active, and its entries run in order with the first match winning. Leads from web-to-lead or the API also need assignment rules explicitly triggered, or they'll land with the default lead owner.
Should HubSpot or Salesforce own lead routing?
Pick one. If Salesforce is your sales system of record, route there and let the owner sync back to HubSpot. Two systems assigning owners is how leads end up with a different rep every time the sync runs.
Conclusion
Fixing lead routing comes down to four moves: see where leads actually go, clean the fields your rules read, rebuild the rules around today's team, and add a safety net so nothing sits unowned. None of it requires a new tool, just a clear owner and a regular audit. Get it right now and every lead source, rep, and AI agent you add later inherits a system that works. If you'd rather not untangle it yourself, that's what we're here for.
Get a Lead Routing Audit from Domestique
Sources:
Openprise. "Why Your Lead Routing Process May Be Broken, and How to Fix It." Openprise Blog, July 21, 2026. https://www.openprisetech.com/blog/why-your-lead-routing-process-may-be-broken-and-how-to-fix-it
The Reform Team. "10 Best Practices for Lead Routing in Multi-Channel Campaigns." Reform Blog,.
https://www.reform.app/blog/lead-routing-best-practices-multi-channel-campaigns
Orbit AI Team. "Leads Not Routed to the Right Sales Rep: How to Fix It." Orbit AI Blog, https://orbitforms.ai/blog/leads-not-routed-to-right-sales-rep