Lead routing rules that assign the right owner, start the SLA clock, and re-route when nobody picks up.
Strkr routing is not a single-dropdown "assign to owner" field. It is a rules engine with round-robin, weighted distribution, territory maps, product-line maps, availability awareness, SLA timers, no-touch re-route, overflow queues, and a complete audit log of every assignment decision. Combined with Strkr Flows, routing is where leads land, get owners, start their first-touch clock, and get escalated when the clock runs out. One rules engine, one audit trail, every paid tier.
What a lead routing rule should actually do in 2026
The gap between the diagram on the whiteboard and the owner on the lead.
Every CRM vendor claims lead routing. The useful question is which routing shapes survive contact with a real inbound funnel, a real on-call schedule, a real territory map, and a real SLA promise written into a signed MSA. In 2026, the bar for a credible lead routing rules engine is a specific list of behaviors: round-robin with skip-on-away, weighted distribution by capacity, territory maps that honor priority order, product-line routing, availability awareness that reads the rep's calendar, SLA timers that start on assignment and escalate on breach, no-touch re-route that moves a stuck lead to a backup owner before the prospect goes cold, overflow queues for after-hours volume, and a complete audit log that answers "who got this lead, when, and why" for every single assignment event. If the rules engine can do these without a professional-services engagement and without a seven-figure contract, it earns the seat. If every rule shape is a separate add-on or a bespoke script, the routing story is marketing, not product. The checklist below is the one buyers should walk every vendor through before signing. Strkr ships all nine on every paid tier.
Round-robin assignment
The fairest distribution shape, done correctly.
A fresh lead enters the queue. The rules engine picks the next rep in the rotation, skipping anyone on PTO, anyone marked away in the availability panel, anyone over their daily cap, and anyone outside the matching segment. The rep gets the lead, the clock starts, and the pointer advances. The rotation is not a dumb mod-N index. It is a stateful queue that respects every exclusion filter and persists across restarts, so a Monday-morning deploy does not reset the sequence and double-assign the first ten leads of the week.
Weighted distribution
Rotations that match rep capacity.
Not every rep carries the same load. A senior AE on strategic accounts closes larger deals and needs fewer inbound. A new SDR building a book should get a disproportionate share of the top-of-funnel. Strkr routing supports per-rep weight (0.0 to 10.0, admin-configured) that scales the probability of selection without breaking the round-robin fairness over the long run. A rep at weight 2.0 gets roughly twice the flow of a rep at weight 1.0, enforced over a rolling 100-lead window so short-run streaks do not distort the ratio.
Territory-based routing
Geography that respects priority order.
Territory maps run as a priority-ordered rule set. The first rule that matches a lead's state, country, ZIP range, or custom-geography-field wins. Overlapping definitions do not fight each other because the admin controls the order. A "New England named-account" rule can sit above a general "Northeast territory" rule and claim the right subset without duplicating logic. The map handles state-level, metro-level, and ZIP-range precision in a single ruleset, and the audit log notes which specific rule claimed each lead so a disputed assignment resolves in one click.
Product-line routing
The right specialist on the right product.
A product-led signup for the Marketing module should land with an AE who sells Marketing. A product-led signup for the Service module should land with the Service specialist. Strkr routing reads product-line fields from the lead (or from the UTM, or from the form submission, or from any admin-mapped source) and routes to the matching specialist pool. The rule stacks under territory, so a Marketing lead from New England routes to the Marketing specialist in the Northeast territory, not to a generalist who will have to hand off twice before the first call.
Availability awareness
The rules engine reads the calendar.
A rep in a two-hour training block should not get an inbound hot lead with a thirty-minute SLA. Strkr routing reads the rep's connected calendar and skips assignments to anyone in a busy block that would blow the SLA on first-touch. The rules check the rep's next free slot, compare it against the SLA deadline, and skip if the gap is too wide. A rep marked out-of-office on their calendar is skipped automatically without a separate PTO toggle in the CRM.
SLA timers
The clock that starts when the lead lands.
Every rule can attach an SLA target: time to first touch, time to qualification, time to first meeting booked. The timer starts the moment the lead is assigned. At the warning threshold (default 50 percent of the SLA), the owner gets a Slack ping. At the breach threshold, the lead escalates: either to the manager, to a backup owner, or into an overflow queue. The SLA is not a KPI you report on after the fact. It is an active timer that moves the lead if the owner stalls.
No-touch re-route
Leads do not sit in a dead rep's queue.
A lead assigned at 9 AM Monday with no activity by 11 AM Monday is not going to magically get worked. Strkr routing can re-route any lead that stays untouched past a configurable window (15 minutes to 48 hours) to a backup owner, a round-robin pool, or an overflow queue. The re-route is explicit: the audit log notes the original owner, the no-touch duration, the backup owner, and the reason. The old owner sees why the lead left their queue, and the new owner sees why it landed in theirs.
Overflow queue
The safety net under the rotation.
Spikes happen. A webinar fires fifty leads into the queue in ten minutes. The round-robin runs out of available reps. The territory map has a gap. The overflow queue catches every lead that no primary rule can claim, holds it in a visible admin surface, and surfaces an unassigned-leads report to the sales manager every morning. No lead ever vanishes into a routing dead end. Overflow leads can be bulk-claimed, bulk-reassigned, or manually routed with a one-click override.
Audit log
Every assignment decision, with reasoning.
The lead's activity log notes every routing event: initial assignment with the matching rule name, SLA warnings, SLA breaches, no-touch re-routes, manual overrides, overflow catches. A disputed assignment ("why did I get this lead") resolves in one click because the audit shows which specific rule won, which specific exclusions applied, and which specific weight ratios drove the pick. The log is also exportable, so sales ops can review a quarter of routing decisions in a single CSV.
How Strkr routing works with Flows
The rules engine is one half of a bigger product.
Lead routing in isolation is a toy. In production, routing is the first step of a workflow: the lead lands, the rule picks an owner, the SLA clock starts, and then a Strkr Flow fires to create the first-touch task, send a Slack ping to the owner, drop a welcome email to the prospect, update the pipeline stage, and enrich the record from the data provider. Routing and Flows run on the same engine, share the same audit log, and are built in the same admin surface. The combination is where lead handling actually becomes operational, not just configurable.
One engine
Routing is a Flow trigger, not a separate product.
When a lead is created, the "lead.created" trigger fires. The flow's first step is a Routing action that evaluates the configured rules and assigns the owner. From there, downstream steps run in the same flow context: create task, send Slack, send email, update field, enrich from data provider, write audit note. The admin does not switch between a routing tool and an automation tool. Both live in one builder with one audit shape.
Shared audit trail
Routing events and flow events in one log.
The lead's activity timeline shows every event in time order: assignment at 9:02 AM, task created at 9:02 AM, Slack ping sent at 9:02 AM, enrichment completed at 9:03 AM, first-touch recorded at 9:17 AM, SLA met. Reviewing a lead's handling means scrolling one timeline, not reconciling three vendor logs. A sales ops lead can answer "what happened to this lead" in thirty seconds, not thirty minutes.
SLA as a flow step
The timer is a first-class action.
The SLA timer is not a hardcoded CRM feature. It is a Flow step: "start timer with 30-minute threshold, on breach fire sub-flow X." That sub-flow can escalate to the manager, re-route to a backup, drop a Slack warning, or do all three. The admin writes the escalation logic in the same place they write the routing logic, so the full lifecycle of a lead sits in one visible, versioned, auditable artifact.
Enrichment inline
The lead gets context before the rep opens it.
Between the assignment step and the Slack-ping step, a flow can call out to a data provider, fetch firmographic context, resolve the company, pull the LinkedIn profile, and write it onto the record. By the time the rep opens the lead, the enrichment is done, the ICP match is scored, and the account owner (if any) is cross-linked. The rep spends ninety seconds reading context instead of five minutes gathering it.
Permission-aware
The flow runs under a scoped service identity.
Flows execute under a scoped service identity with explicit permissions. A flow that reassigns leads has the lead-write permission. A flow that touches deals needs the deal-write permission. The admin cannot accidentally grant a routing flow more surface than it needs, because the permissions are enumerated per flow. The security review for a new routing rule is a one-paragraph attestation of what the flow is allowed to touch.
Versioned
Every flow change is a new revision.
Routing rules evolve. A new territory, a new specialist pool, a tightened SLA. Every edit to a flow (including the routing step) is a new revision with the editor, the timestamp, and the diff preserved. Rolling back a bad change is a one-click revert to the last-good revision. An audit of "what changed in routing this quarter" is a single query against the flow-revisions table, not a reconstruction from Slack screenshots.
Test harness
Rules are testable before they go live.
Before publishing a routing flow, the admin can run it against a sample of historical leads and see the simulated assignments: which rep each lead would have gotten, which SLA would have fired, which no-touch re-routes would have triggered. A proposed rule change is validated against last month's inbound before it ever touches a live lead. Mistakes that would have cost a week of distorted routing are caught in the staging dialog.
Observable
A dashboard answers "is routing healthy right now."
The routing dashboard tracks assignment latency, SLA breach rate, no-touch re-route rate, overflow queue depth, and per-rep load distribution over the last 24 hours, 7 days, and 30 days. If a rule is broken, the dashboard shows it before the sales manager hears about it in standup. Alerts fire when any metric drifts beyond its configured threshold, so the fix lands the hour the problem appears.
Everywhere
Routing shows up on every object, not just leads.
The same rules engine handles case routing, opportunity routing, renewal routing, task routing, and contact routing. The admin writes the rules once per object, and the shape is identical. A support team can configure a case-routing flow with the same builder a sales team uses for lead routing, which collapses the training burden and keeps the audit log consistent across every object a tenant operates on.
Lead routing feature maturity, an honest look
The checkbox versus the rule engine that holds up on Monday.
Every CRM has a "lead assignment" field. Fewer have a routing rules engine that handles territory overlaps, availability-aware skipping, SLA timers, no-touch re-routes, and a full audit log. The honest grading of lead routing is a maturity curve. Here is how the common claims hold up on the way from the pricing page to a production floor.
Owner assignment
Mature when the rule shows its reasoning.
An "owner" field is table stakes. A rule that notes "assigned by rule 'Northeast MM Round-Robin', skipped reps A and B for calendar conflict, picked rep C at weight 1.0, SLA 30 minutes active" is actually mature. Strkr audit logs ship that shape. Several competitors ship the owner-change event alone and leave the sales ops lead to guess what matched. A rule you cannot audit is a rule nobody trusts, and rules nobody trusts get overridden manually inside two weeks.
Round-robin
Mature when it survives PTO and overrides.
Everyone can ship a round-robin pointer. The hard part is making the pointer skip reps on PTO, skip reps over their daily cap, skip reps outside the matching segment, and still maintain fairness over a rolling window. Strkr routing does all four. Products that ship a naive mod-N round-robin accidentally double-assign leads the first time a rep is on vacation and burn trust the day the sales manager spots the pattern.
Territory routing
Mature when priority order is explicit.
Territory maps where every rule is "exclusive" produce gaps and overlaps the sales ops team spends a week debugging. Strkr routing runs priority-ordered rules where the first match wins. The admin controls the order explicitly. Overlapping rules do not fight each other, which is the only shape that holds up when a named-account rule needs to sit above a general geographic rule.
SLA timers
Mature when the breach does something.
A timer that logs an SLA breach but does not move the lead is a reporting feature pretending to be a routing feature. Strkr routing escalates on breach: notify the manager, re-route to a backup, drop into the overflow queue, or any combination. The breach is actionable in real time, not a Q4 retrospective slide. Several competitors report breaches without doing anything about them, which turns the SLA into a vanity metric.
No-touch re-route
Mature when the window is configurable per rule.
A global "re-route after 24 hours" setting is a blunt instrument. Strkr routing lets each rule carry its own no-touch window: 15 minutes on hot inbound, 48 hours on cold outbound-cadence seeds. The window matches the actual urgency of the lead type, which is the only way the re-route stops moving leads that should have stayed put and starts moving leads that were about to go cold.
Overflow queue
Mature when the queue is visible and bulk-actionable.
"Unassigned" as a filter on the leads list is not an overflow queue. A real overflow queue is a dedicated surface with its own dashboard, its own alert, its own bulk-reassign tooling, and its own report that lands in the sales manager's inbox every morning. Strkr ships that surface. Products that ship a bare "unassigned" filter lose leads to the void every weekend.
Audit log
Mature when it ties routing to the activity timeline.
A routing audit log that lives in a separate admin tool is not actually useful. Strkr routing writes the assignment reasoning onto the lead's activity timeline alongside every other event, so a rep or manager reviewing the lead sees why it landed with the current owner in context. The audit is where the lead already lives, not a separate pane the sales ops lead opens once a quarter.
Rules builder UX
Mature when a non-admin can read the rule.
A rule written in a scripting language is a rule only one person in the company can maintain. Strkr rules are visual: match conditions, exclusions, weight, SLA, escalation, no-touch. A sales manager who did not write the rule can still read it and understand why it fires. The bus factor on routing drops from one to the whole admin team, which is the shape every ops leader wants.
The routing-pricing trap
How vendors turn an assignment field into a six-figure line item.
The routing pricing problem is not the sticker. It is the structure. Add-on packages for Advanced Routing, Enterprise Territory Management, SLA Add-Ons, and per-rule license fees turn a capability that should ship with the seat into a budgetary surprise six months in. The Strkr pattern is the opposite shape. Full routing rules, SLA timers, no-touch re-route, overflow queues, and audit logs ship on every paid tier. There is no "Routing Starter" versus "Routing Enterprise" tiering. There is no add-on SKU for territory management. The seat price is the routing price.
Add-on SKUs
Advanced routing hidden behind a sales call.
Several competitors ship a basic owner-assignment field in their mid-tier plan and gate real routing (territories, round-robin, SLA, re-route) behind a separate add-on package quoted per user per month. The sticker price on the pricing page is the opening bid. Strkr routing is on the public page, included in the seat price, every tier, with no bespoke upsell path.
Per-rule licensing
A pricing model that punishes complexity.
Some vendors meter routing rules per month. The admin learns at renewal that the twenty-rule territory map is now costing more than the CRM itself. Strkr routing has no per-rule meter. Write ten rules or write a thousand, the price is the same, which is how you want the pricing shape to point if you care about operational accuracy over invoice-engineering.
Enterprise Territory Management
The six-figure precondition.
Salesforce Enterprise Territory Management is a separate module with its own license, its own admin certification requirement, and its own professional-services engagement to configure. The total cost of running a real territory map on Salesforce is the ETM license plus the admin salary plus the integrator engagement. Strkr territory routing is included, no module, no cert, no integrator required.
SLA Add-On
A timer sold as a separate SKU.
Several vendors sell SLA tracking as an add-on to the routing module. The buyer pays once for routing, once for SLA, and once for the escalation workflow. Strkr ships SLA timers, breach alerts, and escalation actions inside the standard flow builder, included with the seat.
LeanData
Specialist tool that bolts onto the CRM.
LeanData is a credible routing specialist that bolts onto Salesforce or HubSpot and adds a visual rules builder, SLA tracking, and matching logic the base CRM cannot do natively. For teams at 500+ reps with complex account-matching needs, LeanData remains a reasonable addition. For teams under 500 reps, native Strkr routing covers the same ground inside the seat price, with one less vendor to procure and one less audit log to reconcile.
Chili Piper
Scheduler-plus-router for inbound-heavy teams.
Chili Piper combines calendar scheduling with inbound routing, which is a powerful combination for teams that convert fast-moving demo requests. The buyer's math is whether to pay the specialist plus the CRM, or ship both the scheduling and the routing capability inside the CRM at the seat price. Strkr ships both. Chili Piper remains the better fit for the specific case of embedded web-form-to-meeting flows at very high volume.
HubSpot Workflows
Good enough, until the SLA breach does nothing.
HubSpot Workflows handle basic lead routing with branching logic, and work well for teams under 50 reps running simple assignment patterns. The gaps show up on SLA timers that need to escalate, on territory maps that need priority ordering, and on no-touch re-routes that need per-rule windows. For a growing team hitting the ceiling, Strkr routing is the drop-in that keeps the operational shape without a vendor migration twelve months later.
Three routing patterns in production
What the rules engine looks like on a real sales floor.
The product demo shows a rule being edited in the builder. The product in production looks like three specific patterns that teams run every day. These are not aspirational screenshots. These are the three Strkr routing configurations that save teams the most time per week by a wide margin.
Inbound hot-lead rotation
Web form to owner in under sixty seconds.
A fresh demo-request form submission arrives at 2:14 PM. The flow fires: lead created, Routing step evaluates the rule stack. "Enterprise segment Northeast" rule wins. The round-robin pointer skips rep A (PTO), skips rep B (calendar block), picks rep C. SLA timer starts at 30 minutes. Enrichment step pulls firmographic context. Task created on rep C. Slack ping sent. Welcome email drafted. By 2:14:47 PM, rep C has a Slack notification, a task, a fully enriched lead, and 29 minutes 13 seconds on the SLA clock. First touch happens at 2:21 PM. The lead's activity timeline shows the full handling in a single scrollable column.
No-touch Monday recovery
Weekend overflow re-routed by 9:15 AM Monday.
A Friday-afternoon webinar fires 47 leads into the queue between 3 and 5 PM. Twelve go to reps who are already end-of-day heads-down. The no-touch window on the hot-webinar rule is 60 minutes. By Monday 9 AM, those twelve leads are untouched. The rules engine re-routes them to the "Monday Recovery" overflow pool, which is a fresh round-robin across reps who were off Friday afternoon and are back Monday morning. The audit log notes each re-route with the original owner, the duration, and the reason. By 9:15 AM Monday, all 47 leads have an owner who was online when they landed in their queue.
Territory handoff with product specialist
Marketing lead to Marketing AE, not to a generalist.
A product-led signup for the Marketing module arrives from a prospect in New England. The rule stack evaluates: product-line rule "Marketing specialist pool" sits above geographic rule "Northeast general territory." The Marketing-specialist rule wins, routes to the Marketing AE in the Northeast specialist pool. The generalist AE who would have otherwise claimed the lead sees the audit log entry and understands why. No hand-off from generalist to specialist is required because the lead landed in the right hands on the first assignment, which is the whole point of a priority-ordered rule stack.
Lead routing rules on every paid tier. No add-on SKU, no per-rule meter, no professional-services engagement.
Starter includes round-robin, territory routing, and basic SLA timers. Pro adds weighted distribution, availability awareness, no-touch re-route, overflow queues, and audit logs. Scale and Enterprise unlock multi-object routing (cases, opportunities, renewals) and advanced escalation patterns. The seat price is the routing price, every tier, every month. Open a trial and ship your first routing rule before lunch.
Does Strkr charge extra for advanced routing rules?
No. Lead routing rules ship on every paid tier at no additional charge. There is no per-rule meter, no Advanced Routing add-on, no Enterprise Territory Management module, and no SLA Add-On SKU. The seat price listed on the pricing page is the full price. Starter includes round-robin, territory routing, and basic SLA timers. Pro adds weighted distribution, availability awareness, no-touch re-route, overflow queues, and audit logs. Scale and Enterprise unlock multi-object routing (cases, opportunities, renewals, tasks, contacts) and advanced escalation patterns. Write ten rules or write a thousand, the price is the same.
How does Strkr routing compare to Salesforce Lead Assignment Rules?
Salesforce ships basic Lead Assignment Rules with its standard editions, but real territory routing requires Enterprise Territory Management, which is a separate module with its own license, its own admin certification requirement, and typically a professional-services engagement to configure. Round-robin, weighted distribution, SLA escalation, and no-touch re-route each require either custom Apex, a third-party package, or a specialist tool like LeanData bolted on top. The total cost of running production-grade routing on Salesforce is the ETM license plus the specialist tool plus the admin salary plus the integrator engagement. Strkr routing covers all of these shapes inside the seat price with no additional modules.
How does Strkr routing compare to HubSpot Workflows?
HubSpot Workflows handle basic lead routing with branching logic and work well for teams under 50 reps running simple assignment patterns. For a team with territory maps that need priority ordering, SLA timers that need to escalate, no-touch re-routes that need per-rule windows, or availability-aware skipping that reads the rep's calendar, the HubSpot ceiling shows up quickly. Strkr routing supports all of these shapes natively on every paid tier. The pricing is also structurally different: HubSpot gates higher-complexity automation behind Professional and Enterprise tiers with their own feature cutoffs, while Strkr ships the full routing surface on every paid tier.
Do we need LeanData or Chili Piper on top of Strkr?
For teams under 500 reps, no. Native Strkr routing covers the territory maps, round-robin rotation, SLA timers, no-touch re-route, and overflow queue shapes that drive teams to LeanData on top of Salesforce or HubSpot. For teams at 500+ reps with extremely complex account-matching logic that spans multiple business units, LeanData remains a reasonable addition. For inbound-heavy teams that want embedded web-form-to-meeting scheduling flows at very high volume, Chili Piper remains a strong specialist. Strkr integrates with both when a specialist is the right call.
How does the SLA timer actually work?
When a routing rule assigns a lead to an owner, the attached SLA timer starts counting down. The timer has a configurable warning threshold (default 50 percent of the SLA window) and a breach threshold (100 percent). At the warning threshold, the owner gets a Slack ping with a direct link to the lead. At the breach threshold, the lead escalates to one of three configured actions: notify the manager, re-route to a backup owner, or drop into the overflow queue. The admin can configure any combination of the three. The timer accounts for business hours when configured to do so, so an SLA that starts at 4:55 PM on Friday does not breach at 5:25 PM if the tenant's business hours end at 5:00 PM.
What is the no-touch re-route, and when does it fire?
The no-touch re-route moves a lead to a backup owner (or pool, or overflow queue) when the primary owner has not logged any activity within a configurable window. The window is set per rule, not globally, so a hot inbound rule can carry a 15-minute no-touch window while a cold outbound-cadence rule carries a 48-hour window. Activity is defined as any logged touch: call, email, meeting, note, stage change. If the window expires without activity, the re-route fires, writes an audit log entry with the original owner, duration, and reason, and the new owner takes ownership. The old owner is notified so they know why the lead left their queue, and the new owner is notified with the full context.
Can we test routing changes before they go live?
Yes. Before publishing a routing flow, the admin can run it against a sample of historical leads (last 7 days, last 30 days, or a custom date range) and see the simulated assignments: which rep each lead would have gotten, which SLA would have fired, which no-touch re-routes would have triggered, which overflow catches would have occurred. The simulation does not touch live records. Proposed rule changes are validated against last month's inbound before they ever touch a live lead. Rolling back a bad change is a one-click revert to the last-good revision because every flow edit is versioned with the editor, timestamp, and diff preserved.
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.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
