Routage de leads Salesforce : le blueprint RevOps pour le speed-to-lead

The single highest-ROI RevOps investment for most mid-market B2B teams is not AI, it is lead routing. Response time under 5 minutes triples the odds of qualification versus under 1 hour, and yet the median B2B response time in 2026 remains 42 hours. Here is the RevOps blueprint we deploy in Salesforce to close that gap.

The routing decision tree

Every inbound lead answers three questions before it gets a rep: Who is this account (ICP match)? What action did they take (lead source and intent)? Which rep owns them (existing coverage or new)?

• ICP fit: enrichment on submit determines fit. High-fit leads go to AE round-robin. Low-fit go to SDR pool or automated nurture.
• Existing account coverage: if the account is already owned, the lead goes to the account owner regardless of ICP score.
• Territory rules: geo, industry, employee count and revenue thresholds route to the right pod.

Speed matters more than perfect matching

Response time	Odds of qualification
Under 5 minutes	21x vs 30+ minutes
Under 1 hour	7x vs 24 hours
Under 24 hours	3x vs 48 hours

Design for speed first, precision second. A same-day human on a good-fit lead beats a perfectly matched lead sitting for 48 hours.

Native Salesforce Flow vs LeanData vs Distribution Engine

Option	Best for	Watch out
Native Flow + Assignment Rules	Under 20 reps, simple routing	Round-robin logic gets ugly fast, no full audit trail
LeanData BookIt / Router	20+ reps, complex account matching	License cost, but pays back in weeks at scale
Distribution Engine	Round-robin at scale, PTO handling	Add-on, not a full router

The 6 routing rules that never break

1. Enrichment happens before routing: route on complete data, not on form data.
2. Existing account lookup runs first: avoid the "who owns this?" fight later.
3. PTO handling is automatic: a rep on PTO drops out of round-robin, no manual overrides.
4. SLA timers are logged: the moment a lead is assigned, a countdown starts. Missed SLAs trigger escalation.
5. Round-robin is capped: a rep who is over daily lead cap does not receive more, even if it is their turn.
6. Every route is auditable: a Route History object logs why a lead landed where it did. Non-negotiable.

Common routing failure modes we fix

• Round-robin without cap: one rep gets 40 leads on Monday, checks out by Thursday.
• Web form data used raw: no enrichment means no ICP scoring means bad routing.
• SLA measured but not acted on: dashboards are decoration if no manager reviews them Monday morning.
• Hot inbound routed through SDR triage: adds hours to response time on the leads that matter most.

Implementation timeline

Typical mid-market rollout: 4 weeks in native Flow for a first version, or 3 weeks with LeanData. Add 2 weeks for enrichment integration. Full lead-to-book flow, from web submission to meeting on the calendar, ships in 6 to 8 weeks. See our RevOps service for how we scope it.

Frequently asked questions

Do we need LeanData under 20 reps?

Usually not. Native Flow with Assignment Rules covers most cases. Cross the LeanData threshold when routing complexity, cross-team handoffs and account matching get painful to maintain in Flow.

How do we route without enrichment?

You cannot, well. If you refuse enrichment tooling, at minimum require company name and email domain on submit, and normalize on save. The routing will be blunter but functional.

What is a good speed-to-lead SLA?

5 minutes for high-intent inbound (demo requests, pricing pages). 30 minutes for mid-intent (content download, webinar). 24 hours for low-intent.

How do we handle inbound outside business hours?

Auto-reply plus a scheduled call-back queue by rep timezone. Do not let global inbound sit until 9am Monday, LeanData BookIt or Chili Piper resolve this cleanly.