Routing leads from intent signals to reps is the operational chokepoint where most B2B intent programmes break. Per Forrester research, the median time from a high-intent signal firing to a sales rep taking a meaningful action is 11 to 14 days at the under-100M-ARR band, by which point the buying window has often closed. This is the routing playbook that compresses that 11 days to under 48 hours: the rules, the SLAs, the queue design, and the breach dashboard that keeps it honest.
Full disclosure: Abmatic AI ships an intent-to-rep routing layer, so we have a financial interest in fast intent routing. The framework here works whether you route inside Salesforce, HubSpot, Outreach, or a dedicated routing tool like LeanData or Chili Piper. The principles do not change.
Route leads from intent signals in five steps: filter signals to ICP plus tier-1-or-2 accounts only, match the signal to an existing CRM owner or assign to the BDR queue if no owner exists, attach a context packet plus a recommended first action, set an SLA of 24 hours to acknowledge and 48 hours to act, and run a breach dashboard reviewed weekly by sales leadership. Per public customer reports, teams that build this pipeline compress signal-to-action time to under 48 hours and double meeting-booking rates against the same intent volume.
The default failure mode looks like this: marketing buys an intent platform, the platform fires hundreds of signals weekly, marketing forwards a digest to sales, sales ignores 95 percent of the digest, marketing concludes sales does not value intent, the platform contract gets cut at renewal. Per public customer reports, this pattern is dominant at the under-100M-ARR band.
The structural reasons:
The five-step routing pipeline below addresses each leak directly.
| Step | Output | Owner | Time to build |
|---|---|---|---|
| 1. Signal filter | Filtered stream of 5 to 20 signals per rep per week | Marketing plus RevOps | 1 to 2 weeks |
| 2. Owner match | Signal lands on named rep within 60 minutes | RevOps | 1 week |
| 3. Context packet | Structured payload with account history plus recommended action | Marketing plus PMM | 2 to 3 weeks |
| 4. SLA enforcement | Acknowledge in 24 hours, act in 48 hours | Sales leadership | 1 week |
| 5. Breach dashboard | Weekly visibility on missed SLAs and outcomes | RevOps plus sales leadership | 1 week |
The filter has four layers, applied in order:
Post-filter, expect 5 to 20 signals per rep per week. More means the filter is too loose and reps will ignore the queue. Less means the filter is too tight or the intent platform is mistuned.
The signal lands on a named rep within 60 minutes, not 60 hours. Three rules cover the cases:
The 60-minute target requires automation. A weekly digest is the wrong cadence. A real-time webhook into CRM is the right cadence.
A signal without context is noise. The packet contains:
The recommended action is the load-bearing element. Per public customer reports, packets with a recommended action lift rep action rates by 30 to 60 percent over packets without one.
Two SLAs, both visible:
For tier-1 accounts, both SLAs are non-negotiable. For tier-2, 72 hours to act is acceptable. Tier-3 moves to a weekly batch review.
The dashboard is the discipline. It shows, weekly:
Sales leadership reviews the dashboard weekly. Reps see their own numbers. Without the dashboard, the SLAs decay quickly.
Ship the v1 in four to six weeks. Iterate the recommended-action templates monthly based on outcome data.
The routing rules need to handle ten scenarios at minimum. The defensible defaults:
Marketing-forwards-the-weekly-digest is the dominant failure mode. A digest of 80 signals is a polite way of telling sales to ignore the data. Per-account routing with named ownership is the only pattern that scales.
Without enforced SLAs, signals decay before reps act. Twenty-four hours to acknowledge plus 48 hours to act, reviewed weekly, is the floor.
A signal without a recommended action puts the cognitive load on the rep, who often defaults to acting later. Bake the recommendation into the packet.
Treating tier-1 and tier-3 signals identically wastes rep cycles. Tier-aware rules keep reps focused on the named-account list.
Routing customer accounts to new-business sales produces awkward emails and customer-success conflicts. Always check account status first.
Routing sits between identity resolution and rep action. Identity resolves who the account is; routing gets the signal to the right rep with context. The rep takes action, logs the outcome, and the outcome data feeds back to tune the filter.
For supporting frameworks, see how to use intent data, closing the loop from intent to rep action, merging first and third party intent, and account tiering.
Twenty-four hours to acknowledge and 48 hours to act for tier-1. Tier-2 can accept 72 hours to act. Tier-3 moves to a weekly batch. Anything longer than 72 hours on tier-1 misses the buying window for most signals.
Salesforce native flow rules plus LeanData or Chili Piper handle most cases. HubSpot workflows plus Inbound for HubSpot handle simpler cases. Dedicated ABM platforms (Demandbase, 6sense, Abmatic) ship routing layers natively. The build-versus-buy call depends on signal volume and team capacity.
Per public customer reports, 5 to 20 signals per rep per week is the actionable band. Below 5 the queue feels empty and reps stop checking. Above 20 reps batch-process and quality drops.
Two enablers. First, the recommended action embedded in the packet, removing cognitive load. Second, weekly meeting-booking-rate visibility on signal-driven actions versus baseline outbound; reps who see signal-driven actions converting at two to four times baseline adopt fast. If both are in place and adoption still lags, the filter is too loose or the recommended actions are weak.
Tier-3 signals route to a weekly batch review, not the real-time loop. Marketing reviews the batch, picks the top 20 percent, upgrades them to tier-2 for the period, and routes via the standard pipeline. The remainder go to nurture campaigns, not direct rep action.
Every routed signal that produces a meeting or opportunity feeds the ABM influence model. See how to prove pipeline influence from ABM for the cohort-comparison framework.
Routing leads from intent signals to reps is an engineering job, not a content job. The teams that build the five-step pipeline compress signal-to-action time from 11 days to under 48 hours and double meeting-booking rates on the same intent volume. The teams that forward digests and hope sales acts produce no pipeline. Build the pipeline, enforce the SLAs, review the dashboard.