The Three Lead Routing Mistakes That Kill Pipeline

Lead routing is one of those problems that looks solved until you look closely. Most CRM instances have routing rules. Most of those rules are wrong.

Here are the three mistakes I see most often — and how to fix them.

---

Mistake 1: Round-Robin Everything

Round-robin is fair. It's also dumb. A £500K enterprise opportunity and a free-trial signup shouldn't go through the same assignment logic. But in most CRMs, they do.

What happens: Your best reps waste time on low-value leads. High-value leads get assigned to whoever's next in the queue, regardless of skill, territory, or account history.

The fix: Priority-based routing. Score leads on fit (firmographic) and engagement (behavioural). Route high-priority leads to senior reps with relevant experience. Use round-robin only within priority tiers.

---

Mistake 2: No Fallback Chain

What happens when the assigned rep is on holiday? In most CRMs: nothing. The lead sits in their queue until they return. By then, the prospect has bought from a competitor.

What happens: Leads go cold. Speed-to-lead metrics look fine on average but hide catastrophic outliers — 10% of leads wait 72+ hours.

The fix: Fallback chains with escalation timers. If the primary owner doesn't engage within 2 hours, auto-reassign to the backup. If the backup doesn't engage within 4 hours, escalate to the manager. Document the chain and enforce it with automation.

---

Mistake 3: No SLA Tracking

If you don't measure response time, you can't improve it. Most companies track "average speed to lead" but that average hides enormous variance.

What happens: The average is 4 hours. But 20% of leads wait 24+ hours and nobody notices because the metric looks OK.

The fix: SLA enforcement with alerts. Define response time targets by lead priority tier. Track compliance per rep, per day. Alert managers when SLAs are breached, not when the monthly report comes out.

---

The Compound Effect

These three mistakes compound. Round-robin assigns a high-value lead to the wrong rep. The wrong rep is busy so the lead sits (no fallback). Nobody notices because there's no SLA tracking. A week later, the prospect has signed with a competitor.

Fix all three together. The routing logic is one system, not three independent settings.

---

Related

• Fix Routing — Rebuild lead routing with priority, fallbacks, and SLAs
• Pipeline Audit — Diagnose where pipeline is leaking
• For RevOps Teams — Operational support for revenue operations teams

→ Book a Consultation — Let's audit your routing and find the leaks.