Blog › Lead Routing

The 4 Salesforce Lead Routing Mistakes That Kill Speed-to-Lead

Speed-to-lead is one of the highest-leverage metrics in B2B sales. Here's where the routing usually breaks — and what to do about it.

Max
Max · Soleil Consulting Group
August 18, 2026

Why speed-to-lead still matters

The research on this is consistent: reaching a lead within five minutes of form submission makes you 9x more likely to connect than waiting 30 minutes. Most B2B teams know this. Most B2B teams also have routing setups that make five-minute contact structurally impossible.

Mistake #1: Round-robin that doesn't account for availability

Pure round-robin assigns leads evenly by rep. It doesn't account for whether the rep is on PTO, in a deal review, or in a different timezone than the lead. A lead that routes to someone in London at 4pm Eastern will sit until morning.

The fix: weighted assignment with availability rules. OOO records suppress the rep from the rotation. Timezone-aware routing sends East Coast leads to East Coast reps during business hours.

Mistake #2: Routing before enrichment

Routing a lead before you know company size, industry, or fit score means the wrong rep may own it from the start. An enterprise AE shouldn't be working a 3-person startup inbound — but without enrichment, the router has nothing to work with.

The fix: enrich first (Clearbit, Apollo, or the agent equivalent), route after. The latency is seconds. The assignment accuracy is dramatically better.

Mistake #3: No SLA enforcement

A lead assigned to a rep is not a lead being worked. Without a hard SLA (contact within X minutes, visible to leadership) and enforcement (escalation after Y minutes), leads sit. Reps are busy. Inbound gets deprioritized for outbound. The lead goes cold.

The fix: SLA timestamps on every lead at assignment. Automated escalation to manager after 15 minutes without a touch. Visibility in the weekly digest: which reps are beating SLA, which aren't.

Mistake #4: No re-routing on inactivity

A rep gets a lead, sends one email, and moves on. The lead replies three days later. Nobody's watching. It sits unread for a week.

The fix: inbound reply detection with re-alert. If a lead replies and the assigned rep doesn't log activity within 30 minutes, escalate. The pipeline agent monitors this automatically — it's not a rep accountability problem, it's a visibility problem.

Free offer

Free Pipeline Hygiene Audit

Read-only access, findings within days. No install, no commitment.

Get my free audit
Related reading
The Pipeline Hygiene Playbook →Full-Time Admin vs. Fractional vs. AI Agents →Fractional Salesforce Admin vs Full-Time Hire →
Ready to start? Book a Free Call