Feature · Lead routing

Routing that survives Q4.

Round-robin queues that respect PTO. Rule-based assignment by region, industry, deal size. Capacity guards so nobody drowns. Audit logs on every routing decision. The kind of routing that doesn't break the day someone goes on parental leave.

What real routing looks like

The features your last CRM hand-waved.

Most CRMs ship 'round-robin' as a checkbox and call it done. Strkr's routing engine handles the edge cases your team hits every Monday: someone's out, the queue is uneven, the rule conflicts with another, the lead is a strategic-tier whale that shouldn't go to a junior.

Queues

Round-robin with weights.

Assign 2x leads to senior reps, half-weight a new hire, set weekly capacity per rep. The queue self-balances based on assignment history. Skip pause-states automatically. Resume picks up where it left off, no manual queue editing.

Rules

Match by any field. Including custom.

If industry = healthcare AND region = west AND amount > $50K, route to Sarah. Rule precedence is explicit, evaluated top-to-bottom, first-match wins. No more silent overrides where two rules quietly fight each other for the same lead.

Capacity guards

Don't drown your top performer.

Cap weekly assignments per rep. Pause routing for OOO. Restart when they're back. The queue picks up where it left off, no manual rebalancing required. The 'I'm out next Tuesday' Slack message becomes a one-click PTO entry.

Multi-channel

Web forms, webhooks, manual create.

Every lead source flows through the same router. The routing decision doesn't change based on where the lead came from. Form submissions, partner referrals, manually-created leads, CSV imports, all routed identically.

Slack notifications

The new lead pings the assignee.

Configure once. Every routed lead notifies the owner in Slack with a one-line preview and a 'View in Strkr' link. No more 'I didn't see the email' three days later. Owners can acknowledge from Slack.

Audit trail

Every decision is logged.

Who got the lead, which rule fired, what the alternative would have been, the timestamp. Settle the 'why did I get this' arguments in seconds. Compliance teams use it for territory-dispute resolution.

The routing engine your CRO redesigns every quarter, built once.

Lead routing ships on Pro. No 'Sales Engagement Cloud' add-on. No per-rule pricing. No outage-during-quarterly-comp-plan-changes. Build the rules once, tune them weekly.

The arguments lead routing usually causes

Three problems Strkr solves before they happen.

The 'I'm on PTO' lead

Auto-skipped, not auto-assigned.

Reps mark themselves out from the home page widget. The router skips them. No re-routing emails. No 'didn't see this for a week' lost-deal post-mortem.

The territory dispute

Audit log ends it in 30 seconds.

Two reps both think they should have gotten the same lead. Open the audit row, see which rule fired and why. Decision logged, dispute closed, both reps see the same trail.

The Q4 reshuffle

Rule changes take effect on next-fired-lead.

No mid-flight reassignments. No 'we changed the rules but the queue still uses the old ones' surprises. Past assignments stay, future assignments use the new rules. Comp-plan changes don't cause routing chaos.

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.