Your Leads Are Being Routed to the Wrong Reps. The Data Is Why.

Emily Goh · 2026-05-06

The lead came in. It went to the wrong rep. Nobody knows.

A VP of Operations at a 600-person logistics company fills out your demo request form on a Wednesday morning.

Your routing logic says: company domain → match to existing account → assign to account owner.

The domain matches. There is an account in Salesforce. The account owner is Sarah.

Sarah left the company in February. Nobody reassigned her 184 open accounts.

The lead sits in Sarah's queue for 8 days. Nobody follows up. The VP books a demo with your competitor on Friday.

Your CRM says the lead was "contacted." The task was auto-created. But Sarah's login has been deactivated and the task was never worked.

You never knew.

Why this happens more than you think

Lead routing rules are only as good as the data they route against.

The logic seems clean: match the incoming lead to an existing account by domain, assign to the account owner, set a follow-up task, done. But the logic breaks whenever the underlying data is wrong. And the underlying data is almost always wrong in at least one of these ways:

Account owner is inactive. The rep left, the account was never reassigned, and the routing rule still points to them. Sales reps waste 27.3% of their time on invalid or misrouted leads -- about 500 hours per rep per year. At $80K fully-loaded, that is $32K per rep in salary spent on dead ends.

The domain field is missing. Your routing rule matches on company domain. 30-40% of account records in most CRMs have no domain field populated, or it is wrong. These accounts cannot be matched. The lead gets routed to a default queue -- or to the last rep alphabetically.

The account is a duplicate. The incoming lead matches two records: "Acme Corp" and "Acme Inc." One is in enterprise. One is in mid-market. The routing rule picks one at random. The rep who gets it may not be the right fit.

The territory assignment is stale. Territory reassignments happen annually during planning. But reps change, accounts shift, companies get acquired. The account says "Northeast Mid-Market" but the territory was restructured in January and nobody updated the records.

The lead source does not match the routing rule. Your logic was built when you had two segments: SMB and Enterprise. Now you have four. The rules have not been updated. Every inbound lead from a company with 500-1000 employees falls into a catch-all bucket.

What it looks like on a Tuesday

It is a Tuesday morning QBR review.

Marketing presents the lead numbers: 240 inbound leads this month, 180 routed to sales. Good volume. On target.

Sales reports that they worked 90 of the 180. The other 90 were stale, misassigned, or in territories with no active rep.

Marketing asks why 60 leads came in but were not routed. The answer is: no matching account in Salesforce. Those 60 leads were form fills from companies that do not exist as accounts yet -- which means the routing rule had nothing to match against, and they went to the default queue.

The default queue has 847 leads in it. The last one was worked in March.

Marketing's cost per lead is $180. Those 60 leads cost $10,800. They evaporated.

Nobody noticed until the QBR.

The downstream cost nobody tracks

Speed to lead. The benchmark for inbound demos is contact within 5 minutes. Most companies measure this against the timestamp of when the task was created -- not when it was actually worked. A task auto-created for an inactive rep looks like a contact attempt. It was not.

Pipeline gap. The pipeline report shows 180 leads routed to sales. The rep report shows 90 worked. The 90-lead gap is invisible unless someone manually reconciles the two reports. Most do not.

Wrong rep for the account. Even when the lead is routed correctly by territory, it may not be correct by account fit. A fintech company routed to a rep whose entire book is healthcare produces a worse first conversation and a lower close rate. Nobody can see why in the data.

Rep productivity distorted. If half a rep's assigned leads are wrong-fit or unworkable, their conversion rate looks bad. They go on a PIP. The actual problem was the routing, not the rep.

What clean lead routing actually requires

Domain coverage. Every account record needs a company domain. Without it, inbound leads cannot be matched. This is an audit -- you have to find every account with a blank or wrong domain field and fill it in.

Active owner check. Every account routing rule should validate that the assigned owner has been active in the past 30 days. Inactive reps should have their accounts automatically flagged for reassignment.

Duplicate account resolution. When an inbound lead matches two or more accounts, the routing rule needs documented, consistent tiebreaker logic. Not random. Read HSBC Is in Your CRM 4 Times for how duplicates compound the routing problem.

Territory currency. After every rep change, territory update, or segment redefinition, the account records need to reflect it. If the map changes and the data does not, the routing is wrong from day one of the new structure.

None of this requires a new CRM. It requires knowing what is in the one you already have -- continuously, not at the end of a quarter. For how this feeds into the broader reconciliation problem, read What Your RevOps Team Is Actually Doing on the Last Tuesday of the Month.

Gohvio is free to try -- gohvio.io