Feature · Lead Routing System

A lead routing system that enforces the rules sales ops actually agreed on.

Lead routing fails in a predictable way: the rules get complicated, the exceptions multiply, the SLA on new leads slips, and sales ops ends up rebuilding the system on the fourth Tuesday of every month. Strkr's lead routing system is a visual rules engine with named strategies, scoped overrides, SLA tracking, and an audit trail so the rules do what sales ops agreed they would do.

Start free trial See pricing
What a routing system should do

The decisions a lead faces between capture and assignment.

A lead captured in the CRM has to answer a sequence of questions before it lands with the right rep: who owns the account, what segment is the lead, which rep covers the territory, is that rep available, is there an SLA pressure, is there an exception, what rotation if multiple reps fit. Each question is a decision; the sum of decisions is the routing. A good routing system makes every decision visible and auditable.

Account match first

The lead belongs with the account owner, usually.

The first decision: does this Lead's company match an existing Account. If yes, the account owner is the default routing target regardless of other rules. This single rule prevents the "we sent two reps at the same account" failure that is the biggest routing complaint from AEs.

Segment check

The lead's size determines the territory.

For Leads without an existing account match, the segment check (SMB, Mid-Market, Enterprise, Strategic) runs on firmographic data. Each segment has its own routing team, so the SMB rep does not land an Enterprise logo and an Enterprise rep does not get stuck prospecting SMB.

Territory match

Geography, vertical, product line.

Within a segment, the territory match narrows to the rep: by geography (country, region, state), by vertical (healthcare, financial services), or by product line (CRM, Projects, Flows). The territory rule is per team and per segment; a vertical team can have a different geo split than a horizontal team.

Availability check

The rep has to be present and under cap.

An available rep is one who is not on PTO, not over their lead-count cap for the day, and has the right permissions for the lead type. Flows checks the rep's availability before assignment. A rep on PTO never gets a lead; a rep at cap gets skipped in rotation.

Strategy pick

Round-robin, weighted, first-available, or score-based.

Among the eligible reps, the strategy decides the pick: round-robin for equal distribution, weighted by quota size for revenue-weighted distribution, first-available for speed, or score-based for routing by Lead score. Different teams run different strategies; the strategy is configured per routing rule.

Exception handling

The named-account list, the VIP flag, the override.

Exceptions handle the special cases: a named-account list routes to a rep regardless of the usual rules, a VIP flag triggers an exec-sponsor notification, a manual override lets sales ops reroute specific leads. Exceptions log to the audit trail with the reason captured.

The routing strategies

The four named strategies and when each fits.

Named strategies make the configuration conversation precise. Sales ops picks a strategy per routing rule rather than hand-rolling the distribution logic. The strategies below are the ones production teams run; each has a fit and a failure mode.

Round-robin

Even distribution across eligible reps.

The simplest strategy: assign each new Lead to the next rep in the eligible list, cycling. Produces equal lead counts. Fits teams where every rep has the same quota and similar skills. Fails when reps have different quota sizes or different conversion rates; equal lead counts produce unequal revenue outcomes.

Weighted

Distribution proportional to quota or capacity.

Each rep carries a weight (quota size, capacity, seniority). The strategy assigns Leads proportional to weight: a rep with a 2x quota gets 2x the Leads. Fits teams with varying quota sizes or formalized senior/junior tiers. Requires maintaining the weights as quotas change; stale weights distort distribution.

First-available

The rep online right now gets the lead.

Among eligible reps, the one who is online and under cap now gets the Lead. Fits teams running speed-to-lead motions where the first reply wins. Requires an "available" signal (Slack status, calendar presence, explicit toggle); without the signal, degrades to round-robin.

Score-based

High-score leads to high-performing reps.

Lead score (from the scoring model) picks the rep tier: hot leads to the top-performing rep, warm leads to the senior rep rotation, cold leads to the SDR team. Fits teams with meaningful performance variance and a scored lead population. Requires a trustworthy scoring model; a drifted model routes badly.

Account-ownership

The existing account owner gets any new Lead.

A Lead whose company matches an existing Account routes to that Account's owner regardless of the primary strategy. Prevents double-coverage. The strategy is almost always a layer on top of another strategy rather than used alone.

Hybrid

Combinations of the above with precedence.

Most production teams run a hybrid: account-ownership first, then round-robin within the territory, with a VIP exception layer. The configuration surface composes strategies with explicit precedence rather than nesting conditions. The hybrid pattern is the usual production shape.

SLA and governance

The accountability layer around the routing.

A routing system is only useful if the result is visible and correctable. Teams need to see the routing decision, measure response time, catch rules that are not working, and fix the exceptions. The sections below name the governance surface Strkr ships.

SLA on first touch

The clock starts at routing.

Every Lead carries an SLA timer that starts at routing. The target (15 minutes for hot leads, 2 hours for warm, 24 hours for cold) configures per Lead type. SLA breaches surface on the manager's dashboard and trigger an escalation Flow (notify the manager, auto-reroute, reassign).

Routing audit log

Every decision is replayable.

Every Lead's routing decision writes to the audit log: the rules evaluated, the branches taken, the strategy that picked the rep, the override (if any). A rep claiming "I never got this Lead" opens the audit log to see the exact assignment; sales ops answers the dispute from the log, not from memory.

Routing dashboard

Volume by segment, strategy, and outcome.

The dashboard shows Leads routed per segment per day, Leads per rep per day, SLA attainment, and routing-rule hit rate. Managers see whether a rule is firing more than expected; sales ops sees whether the strategy is producing the intended distribution.

Overrides

The sales ops escape hatch.

Any Lead can be reassigned by a sales ops user with an override. The override requires a reason that writes to the audit log. The pattern catches the edge cases the rules missed; the reason field builds the backlog of improvements for the next rules review.

Rule testing

Dry-run against historical data.

A new routing rule can be dry-run against the last 90 days of Leads to see what would have been different. Sales ops picks the change that produces the intended effect before deploying. The "we deployed the new rule and it routed everything to Jamie" failure is caught in dry-run.

Rule versioning

A rule change is a diff, not a mystery.

Every rule change is a versioned diff: who changed what, when, with what rationale. The current rule set and all historical versions are inspectable. Rolling back to a prior version is one click. The rules do not quietly drift into something nobody owns.

The ops cadence

How a routing system stays healthy over time.

A routing system is not a set-and-forget object. Rules drift as quotas change, reps join and leave, segments evolve, and sales motions shift. The sections below name the cadence that keeps the routing system matching the team's current reality.

Weekly rules review

The exceptions log drives the rules queue.

Every week, sales ops reviews the overrides from the past week. An override reason that appears three or more times is a candidate for a new rule. The weekly cadence catches the drift before it becomes a backlog of exceptions. The review is a 20-minute meeting, not a project.

Monthly SLA review

Breach analysis by segment and rep.

Every month, review the SLA breaches: which segments are breaching, which reps are breaching, what is the root cause. Common patterns: a rep on PTO without a backup rule, a segment's SLA set too tight, a strategy that puts too many Leads on the top-performer. The review feeds the next rules change.

Quarterly strategy review

Does the strategy still fit the team shape.

Every quarter, review whether the strategy still fits. Team hires may have shifted a round-robin team to a weighted need. A product-led growth pivot may have changed the scoring approach. The strategy picker lives on the rule; swapping strategies is a dropdown change, not a rebuild.

New-hire integration

A new rep is in rotation on day one.

A new rep joining a team enters the eligible rep list via their role assignment. The routing rules do not need per-rep edits. A rep leaving is removed from the role, which immediately removes them from routing. The common "the new rep is not getting Leads" failure is a role-provisioning issue, not a routing-rule rebuild.

Territory redraw

A new map re-plays Leads to the new owners.

When a territory redraw happens (common at end of fiscal year), the new map applies to future Leads automatically. The option exists to replay the last 30 days of Leads under the new rules; sales ops picks whether to re-assign or leave historical Leads with their original owner.

Audit for compliance

The audit log is the compliance evidence.

For teams with regulated distribution requirements (fair-lending in financial services, equal-access in some sales categories), the audit log is the compliance evidence. A regulator asking "how do you distribute leads" gets a log export plus the rule set, not a verbal explanation.

A lead routing system that enforces the agreement sales ops made with the team.

Strkr Flows ships the routing engine with named strategies, SLA tracking, audit trail, and dry-run testing on every paid tier. The weekly override review becomes a 20-minute meeting; the rules match the team's shape without a monthly rebuild.

Start free trial See Lead Capture Integration
Common questions

What buyers ask about this feature.

How does the routing system handle existing account relationships?

The account-ownership rule layers on top of any other strategy. A new Lead whose company matches an existing Account routes to that Account's owner regardless of the usual territory or round-robin rules. This single layer prevents the double-coverage failure that is the biggest routing complaint from AEs. For companies that match multiple Accounts (large enterprises with multiple relationships), the rule prefers the most recent owner by default, with a configurable preference for the owner with the most open opportunities.

Can I run different strategies for different teams or segments?

Yes. The strategy is configured per routing rule, and rules are scoped by segment, product line, geography, or any custom field. The SMB team runs round-robin, the Enterprise team runs account-ownership-plus-weighted, the Expansion team runs score-based, and the Partner team runs a named-account strategy, all simultaneously. Each team sees their routing distribution on their own dashboard without the others' noise.

What happens when a rep is on PTO?

The rep's availability flag flips to unavailable (manually, from the Google or Microsoft 365 calendar integration, or from a PTO-tracker integration). The routing rules skip unavailable reps for the duration. On return, the rep flips back automatically. Teams can configure the backup pattern: skip entirely (route to next eligible rep), redistribute to the team (round-robin among available reps), or queue (hold Leads for the returning rep). Most teams redistribute to maintain speed-to-lead.

How is the SLA tracked and enforced?

Every Lead carries an SLA timer that starts at routing. The target configures per Lead type (15 minutes for hot leads, 2 hours for warm, 24 hours for cold). The timer visible on the Lead record counts down; approaching breach triggers a Slack notification to the rep, breach triggers an escalation Flow (notify the manager, auto-reroute, or reassign to a cover rep). The SLA attainment report rolls up to the dashboard by rep and by segment so managers see patterns of breach.

Can I test a new routing rule before deploying it?

Yes. The dry-run option replays the new rule against the last 90 days of Leads and shows what would have been different: which Leads would have gone to a different rep, what the resulting distribution would look like, which SLAs would have been met or missed. Sales ops picks the change that produces the intended effect before deploying. The "we deployed the new rule and it routed everything to Jamie" failure is caught in dry-run. The dry-run runs in minutes and does not affect any live Lead.

How does the audit log support compliance for regulated industries?

The audit log records every routing decision with the rules evaluated, the branches taken, the strategy picked, the rep assigned, the timestamp, and any override with its reason. For regulated distribution requirements (fair-lending in financial services, equal-access requirements in some sales categories), the log is the compliance evidence. A regulator asking "how do you distribute leads" gets a log export plus the current rule set with its version history, not a verbal explanation. The log retains for the configured retention period (default seven years for compliance-heavy workspaces).

Related features

Pair this with...

Automated Lead Routing Lead Capture Integration AI Lead Scoring Lead Scoring Best Practices

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