Lead routing made simple

Set up in minutes. Extend with agents. Experiment without headaches.

Run inbound directly from Claude

Answer the routing questions your dashboard can’t. What changed, why it happened, what would’ve happened instead.

Claude·rift routing

Why did the Atlassian lead get routed to Sarah instead of enterprise?

Replaying that decision now.

rift·routing.explain

lead: "atlassian.com"

at: "2026-04-22 14:03 UTC"

Matched "US Mid-Market" under policy v4.2 → Sarah

The Enterprise rule required employees > 10,000, but HubSpot has Atlassian at 9,800 — it came within 200 of matching.

Who no-showed this week and which ones should we chase?

Most no-shows never re-book

You see a no-show or a ghost; rift re-books them. No chasing required.

Today — Wednesday, Apr 2

9:00 AM

Alex Morgan· Acme Corp

Discovery Call

Done

10:00 AM

Chase Reed· Beacon Labs

Demo

11:30 AM

Jordan Li· Mosaic Inc

Follow-up

1:00 PM

Sam Patel· Kova Systems

Discovery Call

No-show detected

Chase Reed missed the 10:00 AM demo

Give your top leads the VIP treatment

Spot high-value prospects, route them to the right rep, hold your best calendar slots, and alert the team.

Lead routing

New form submission

Chase Reed · chase@beaconlabs.io

Lead created

Synced to HubSpot

Lead enriched

Apollo · 240 employees · $28M ARR

High-value ICP detected

Matched rule: Revenue > $10M

Routed to midmarket team

Assigned to Sarah Chen

Full calendar unlocked

6 slots available (vs 2 standard)

Team notified via Slack

#sales-alerts · Chase Reed booked Mon 9 AM

01
Capture
Build custom forms that capture inbound leads with the fields that matter to your routing logic.
02
Route
Validate, enrich and route every lead to the right team member based on your rules.
03
Schedule
Present a calendar for immediate booking or add to a waitlist when the timing isn't right yet.
04
Automate
Every step emits signals. Trigger workflows from them with rift's agents or connect your own — recover no-shows, research high-intent leads, anything else your playbook needs.

How it works

Get every inbound from form submit to a completed discovery call.

Beta

Change routing rules with confidence

Version every routing change and know its impact before it goes live.

routing.configmain

fil
Enterprise threshold: 1,000 → 500 employees
Backtest complete
Backtest passed: +2 enterprise leads, no routing regressions
matt, using Claude
SMB owner unavailable → round-robin fallback

rule.match → Enterprise route

Matched 3 of 4 conditions

rep.assign → sdr-3

score.icp_fit → 87

ICP fit · high

enrich.clearbit

12 fields added

form.submit

+0ms · accepted

See exactly what happened to every lead

Every signal, every rule match, every decision. Trace any lead end to end and answer "why did this one route here?" in seconds.

Per-lead trace
Every event with timestamp and latency, end to end.
Decision replay
Expand any rule match to see which conditions fired and why.
Live signals
Watch leads move through the system in real time.

Hook into your existing stack

Every event in the lead lifecycle emits a signal. Wire it into your CRM, messaging tools, or agentic workflows — or build your own integrations via webhooks.

HubSpot