Feature · Automated Lead Routing

Inbound lead to assigned AE in forty-two seconds, fairly.

The routing engine evaluates territory, firmographic fit, capacity, timezone, and vacation state in one pass. Round-robin fairness math logs every assignment to the audit trail. SLA breaches on first-touch escalate automatically without a manager hunting through Slack.

Start free trial See pricing
The routing primitives

Six variables that produce one assignment.

Lead routing in practice is not a single-field assignment rule. The real engine evaluates six variables in one pass: territory match, firmographic fit, capacity remaining, timezone overlap, vacation state, and tie-break fairness. The output is one assignment with a logged rationale. The six-variable framing is what prevents the common failure mode where the ops lead cannot explain why the lead landed on Steve instead of Priya.

Territory

Country, state, industry, or custom shape.

Territory rules support country, US state, ANZ state, EMEA sub-region, industry (NAICS or custom), company size band, and any custom field combination. The admin maps territories once as named rule sets; the routing engine evaluates. A rep covers "US-West plus mid-market SaaS" and the engine knows what counts. No duplicate rules in six places.

Firmographic fit

Enrichment-driven ICP scoring.

A fit score from the ICP scoring model (configured in the Strkr AI module) weights the match. A lead that matches territory but scores low on fit routes to the SDR queue instead of straight to the AE. A high-fit lead jumps the AE queue even if territory is a near-miss. Fit beats geography on fit-first teams; geography beats fit on territory-first teams; the policy is tenant-configured.

Capacity

Open-deal count and pipeline weight caps.

Each rep carries a configurable capacity: a max open-deal count, a max weighted pipeline value, or a max new-lead-per-week quota. A rep at cap drops out of the pool for new assignments until the cap clears. Capacity is a floor against the common "star AE drowns in leads while rookie AE sits dry" pathology.

Timezone

Business-hours overlap during routing.

A lead with a Sydney phone number routes to an AE whose business hours overlap the Sydney workday, not to the Chicago rep who will miss the first-touch window by seven hours. Business hours and work calendars live on the user record. Routing respects them automatically without an ops lead building a timezone matrix.

Vacation

OOO ranges drop reps from the pool.

The rep OOO date ranges from the capacity module drop the rep from the routing pool for the configured interval. The AE on PTO Monday through Friday never gets a Monday-morning inbound. The handoff is clean, not a reassignment the Tuesday-morning rep untangles.

Fairness tie-break

Round-robin on the recent-assignment count.

When two reps match equally on the first five variables, the tie-break goes to the rep with the fewest assignments in the trailing window (configurable, defaults to 14 days). This is the audit-defensible fairness math. The log shows the recent-count comparison, so a rep asking "why did Steve get the last three?" gets a answer from the log.

Audit log

Every assignment writes a rationale.

Each assignment writes an audit record: the input variables (territory, fit, capacity, timezone, vacation state, recent counts), the eligible rep set, the tie-break outcome, and the final assignee. The log answers "why did this lead go here" in one query, which closes the loop with the AEs asking the question.

Pool overflow

No eligible rep triggers a defined fallback.

If no rep matches the full rule set (common for exotic territories like Lichtenstein-based SaaS at 400 FTE), the engine routes to the configured overflow queue instead of silently losing the lead. The overflow queue is reviewed daily; the rule set evolves to catch the missed patterns. Nothing falls through the cracks.

The SLA layer

From assignment to first touch, with escalation.

Assignment is step one. The second-order metric is time-to-first-touch, and most inbound teams silently fail that metric because the SLA layer lives in an ops lead's head rather than in the engine. Strkr tracks the SLA from assignment to first touch on every lead and escalates breaches automatically.

SLA target

Five minutes for high-fit, 24 hours for low.

SLA targets configure per lead segment. High-fit inbound demos target 5-minute first touch (the number that drops qualify rate off a cliff after 10 minutes). Low-fit cold inbound targets 24 hours. The target lives in the routing rule; every assignment carries its own clock.

First-touch definition

Email, call attempt, or meeting booked.

First touch counts as a sent email, a logged call attempt (connected or not), or a booked meeting from the lead self-serve calendar. The event sources connect to the standard CRM activity log, so the engine never miscounts a Slack internal thread as a touch. The definition is strict, which keeps the metric honest.

Breach escalation

Four tiers from Slack ping to reassignment.

A 50-percent-elapsed breach pings the AE in Slack. A 100-percent-elapsed breach pings the AE manager. A 150-percent-elapsed breach raises the lead to a visible dashboard alert. A 200-percent-elapsed breach reassigns the lead to the next-eligible rep automatically. Each tier is configurable; teams tune the ladder to their inbound tempo.

Dashboard view

Live SLA state across the team.

The routing dashboard shows live SLA state for every rep: green under 50%, yellow 50-100%, red over 100%, dark red reassigned. Managers glance at the dashboard before standup to see who is drowning and who is dry. The dashboard replaces the Monday-morning "who has leads sitting cold" email that nobody opens.

Weighted priority

High-value leads jump the queue.

A high-ICP-fit high-ARR-potential lead carries weighted priority in the SLA ladder: shorter target, faster escalation, visible on the manager dashboard first. Weighted priority prevents the common failure mode where a $400k opportunity sits in the queue behind a dozen SMB inbounds for seven hours.

SLA audit

Breach history by rep and by segment.

The SLA audit view aggregates breach rate per rep, per segment, per week. Managers see which reps consistently miss which segments and have a data-driven coaching conversation instead of a vibes-driven one. Patterns like "West team misses US-East inbounds" surface quickly because the audit covers both the breach and the territory shape.

What this replaces

LeanData, Chili Piper, and the ops lead who hates both.

Teams running mid-market inbound at scale typically run LeanData for routing and Chili Piper for scheduling, with an ops lead stitching the handoff. Strkr runs routing and scheduling inside the record, so the stitching layer disappears. The comparison below sticks to specifics instead of positioning.

LeanData

The routing-only standalone.

LeanData is a strong routing engine; the issue is that it sits beside the CRM and syncs state back. The sync lag drives the common failure mode where a rep sees a lead in the CRM a minute before LeanData sees it and starts manual triage. Strkr runs routing inside the record. The sync lag is zero because the engine and the record share state.

Chili Piper

The booking-only standalone.

Chili Piper handles the self-serve booking after routing. Strkr includes self-serve booking inside the record (team calendars, booking links, Google Meet or Teams auto-attach). The combined savings versus Chili Piper plus LeanData runs around $14 per user per month on a mid-market team.

HubSpot workflows

Fine for a single-rep team, not scale.

HubSpot workflow routing is adequate for a two or three-rep team. The failure mode is the capacity math, the SLA escalation, and the fairness tie-break. Teams building a 12-plus rep inbound motion graduate out of HubSpot workflows quickly. Strkr covers the scale cases without the standalone add-on.

Salesforce assignment rules

Not built for fairness or SLA.

Salesforce assignment rules are a 1998-era primitive that assign on a single rule hit. Fairness, capacity, SLA, vacation, timezone are all extensions you build with Apex or buy a standalone. Teams migrating off Salesforce often cite the assignment rule limitations as a pain point; our Salesforce migration path imports leads cleanly and the routing engine takes over on day one.

Not Zapier

Middleware does not do fairness math.

A Zapier zap that routes leads based on territory is a two-field decision tree. It cannot do capacity, SLA, fairness, or vacation. Teams start on Zapier for the first ten leads and then outgrow it. We do not recommend a middleware tier for routing at mid-market scale.

Open API

Vertical lead sources integrate as code.

A vertical lead source (DemandGen partner, co-marketing webhook, outbound SDR tool) wires via inbound webhook. The engine ingests, routes, and books. Partners build inside the record; no middleware console in the path. We ship an OpenAPI 3.1 spec and an SDK; vertical integrations ship as first-class native code.

The real numbers

Fourteen customer measurements on routing impact.

Across fourteen mid-market B2B teams running Strkr automated routing in production, the measured impact landed in a narrow band. The numbers below are the median outcome, with the tightest and loosest customers in each metric noted. Routing is one of the smallest-code highest-impact changes an inbound team ships.

Time to assignment

Eleven hours became forty-two seconds.

Median time from form submit to AE assignment fell from eleven hours in the manual flow to forty-two seconds in the automated flow. Savings came from eliminating the ops-lead triage step and the manager assignment review. Fastest customer runs 18 seconds; slowest runs 2 minutes (held by a condition awaiting an enrichment payload).

Time to first touch

Nineteen hours became ninety-seven minutes.

Median time from assignment to first touch fell from 19 hours to 97 minutes. The SLA ladder plus the dashboard visibility drives this; AEs see their own SLA state and no one wants their name in red before noon. The tightest customer runs 23 minutes median; the loosest runs 4 hours.

Fairness drift

From 3.4x to 1.2x within-team assignment ratio.

Pre-routing, the heaviest-loaded AE on the team was receiving 3.4x the leads of the lightest-loaded AE. Round-robin plus capacity caps brought the ratio to 1.2x within the first quarter. The two-tenths variance tracks real territory and fit differences, not scheduling luck.

Qualify rate

Up six points across the sample.

Median qualified-lead rate rose six percentage points after routing deployment. The lift came from faster first-touch (the five-minute magic window), better fit matching (high-ICP leads landed on reps who close them), and visible SLA pressure. Six points on a 24-point baseline is a 25-percent improvement at the top of funnel.

Cold-queue depth

From 240 leads to under 15.

The cold queue (unassigned leads older than 24 hours) averaged 240 pre-deployment and settled at under 15 after six weeks. The overflow queue plus the daily review surface the rule gaps quickly; the ops lead refines rules week by week until the cold queue flattens.

Rep retention

AE churn down 11 points year over year.

One mid-market customer measured AE retention before and after routing. Pre-routing, three AEs quit in 2024 citing unfair lead distribution. Post-routing, zero AEs quit for distribution reasons in the first full year. The fairness math reduces the quiet-quit pattern that was draining the team.

Three ways routing goes wrong

The failure modes we hardened against.

Routing deployments fail predictably. Across the ninety-one teams we onboarded, three failure patterns recurred. The engine ships with defenses for each. Teams that follow the deploy checklist dodge all three; teams that skip the checklist usually hit at least one in week two.

Failure one

Capacity cap too high.

Ops lead sets rep capacity at 40 open deals thinking "nobody has 40 open deals" and the capacity cap never bites. Result: fairness math falls back to pure round-robin and the star AE still drowns. Defense: the deploy checklist sets cap at 1.3x the current median open-deal count, which bites quickly on the heaviest rep.

Failure two

SLA target too generous.

Ops lead sets SLA target at 24 hours for all segments because "we have never missed 24 hours." Result: no AE feels urgency and the five-minute magic window on high-ICP leads passes without notice. Defense: the deploy checklist tiers SLA by segment, with high-ICP at 15 minutes.

Failure three

Overflow queue never reviewed.

Overflow queue fills with 60 leads over three weeks because nobody is reviewing it. Result: real pipeline value sits unassigned. Defense: the deploy checklist builds a daily digest of overflow queue entries that pings the ops lead. Three days of overflow is a signal to add a new rule.

Rule drift

Territory boundaries hand-edited over months.

Classic drift: the ops lead edits a territory rule for a escalation, forgets it is there, and the one-off becomes permanent. The audit log on routing rule edits plus the quarterly rule-review digest surface drift. The ops lead sees "this rule has 2 live instances and 11 edits in the last 90 days" and makes the fix.

Enrichment gaps

Firmographic fit missing on no-domain leads.

A lead that submits without a work email has no company domain and no firmographic enrichment. The engine falls back to a configurable low-fit score plus a routing-held state while an SDR enriches. The lead does not sit idle; the SDR queue gets the assignment with the enrichment ask.

Transfer context

Reassignment preserves the audit trail.

When routing reassigns a lead on SLA breach, the new assignee sees the breach history, the prior AE comments, and the original assignment rationale. Context transfers with the record. The new AE does not restart from scratch.

See lead routing fire on a live inbound in under thirty seconds.

Live walkthrough from form submission to AE assignment to first-touch SLA start. Bring your routing rules; we will configure them on screen.

Book a walkthrough See all routing features
Common questions

What buyers ask about this feature.

Can routing rules handle a sixteen-territory org without a spaghetti rule set?

Yes. Territory rules compose from reusable primitives (country, state, industry band, employee band) stored as named sets. A sixteen-territory org defines sixteen named territory shapes once and the routing engine evaluates. The admin UI shows the territory map visually and flags overlaps or gaps. The common 42-row spreadsheet with sixteen conflicting rules becomes a readable visual with explicit precedence; new ops leads onboard in an hour instead of a week.

What happens if the routing engine assigns to someone who should not have gotten the lead?

The audit log captures the exact variable state that led to the assignment: territory match, fit score, capacity remaining, timezone, vacation state, recent-count tie-break. The ops lead reviews the log entry, identifies which variable produced the surprise (often a stale OOO or a mis-set capacity), and edits the rule or the input data. The next similar lead routes correctly. The engine never produces an unexplainable assignment.

Does routing work for outbound-generated leads too?

Yes. The engine triggers on lead creation regardless of source (inbound form, outbound SDR enrichment, imported batch, API webhook). The source carries metadata that routing rules can read (lead.source, lead.campaign, lead.channel). Teams often route inbound and outbound through separate rule sets because the capacity math and SLA budgets differ; the engine handles both paths within one engine.

Can we hold leads for a brief enrichment window before routing?

Yes. A hold step in the routing rule waits for a configured enrichment payload (Clearbit, ZoomInfo, custom) before evaluation. The hold has a timeout: if enrichment does not arrive in 60 seconds, routing proceeds with the fallback low-fit score. The pattern catches the common case where routing fires faster than the enrichment webhook and lands high-fit leads on the SDR queue by accident.

How does this interact with the self-serve booking link we send?

The booking link routes the booked meeting to the assigned AE automatically. The booking link preserves the assignment made at routing time, so a lead that routed to Priya and clicks the link three hours later books with Priya, not with whoever is first-available. The exception: Priya is OOO at the booking window, in which case the booking surface shows the backup AE per the delegation rule.

Is HIPAA covered for lead routing in healthcare?

Healthcare teams routing patient inbound (demos from clinics, referral partner intake) run under the BAA with per-tenant encryption on the lead data and the routing audit chain. PHI fields on the lead inherit the tenant encryption key. SOC 2 Type II attestation is in progress for 2026-Q4. GDPR and CCPA data-subject requests cover routed leads on the standard SAR workflow.

Related features

Pair this with...

Lead Routing Software Lead Routing Rules Automated Lead Scoring Lead Management Lead Capture Sales Automation B2B Lead Scoring

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing