Use caserevops & sales

Leads routed while they're still warm.

Speed-to-lead dies in the gaps: the form fill that sat overnight, the duplicate account that split the history, the round-robin that skipped the rep who was actually on. An agent closes those gaps in minutes — and asks first when a judgment call could rewrite your CRM.

// the manual version

You know this week already.

The overnight lead

The demo request lands at 6pm Friday and gets its first touch Tuesday. Nobody chose that; the routing rules just didn't cover it.

Duplicate hell

jane@acme.com and j.doe@acme.co are the same buyer with two histories. Rules-based dedupe either misses them or merges the wrong ones.

Routing rules nobody trusts

The territory logic lives in a workflow builder three admins ago. Reps escalate around it because they've been burned by it.

// describe it

The whole build is a brief.

No canvas, no nodes. You write instructions the way you'd brief a teammate; the lines marked with a shield pause for a human before anything irreversible happens.

Example brief — illustrative, write yours in your own words

·When a new lead arrives from the website, ads, or the shared inbox, enrich it.

·Check the CRM for existing accounts and contacts that look like a match.

If it's clearly a duplicate, link it; if it's ambiguous, ask before merging.

·Score against our ICP notes and route: named accounts to their owner, else round-robin.

·Draft the intro email in the owner's voice from our templates.

Before reassigning an account away from a rep, wait for the sales manager's approval.

·Post a daily routing digest — what came in, where it went, what stalled — to #revops.

// how it runs

Autonomous on the routine. Supervised on the rest.

What starts it

A new-lead event from your forms, ad platforms, or CRM.
An inbound email to the shared sales inbox.
A nightly sweep that catches anything the event stream missed.

What waits for a human

Ambiguous merges — the agent proposes, a human confirms, histories stay intact.
Account reassignments — nothing moves off a rep's book without a manager's yes.
First-touch emails, if you want them held — or let templates run and gate only exceptions.

What the trace keeps

Why each lead was routed where it was — enrichment, score, and rule, in plain terms.
Every merge and reassignment, with who approved it.
A digest trail RevOps can audit when a rep asks 'why did I get this one?'

// common questions

How is this different from CRM workflow rules?

Rules match fields; the agent reads context. 'Same buyer, different email domain' or 'this note says they asked for Dana specifically' are judgment calls a rules engine can't encode — and exactly where the agent asks instead of guessing when it isn't sure.

Can it break our CRM?

The destructive operations — merges it isn't certain about, reassignments — are gated behind human approval, and every change is in the run trace. The blast radius of a bad guess is a question waiting for you, not a rewritten book of business.

Which CRMs does it work with?

Salesforce, HubSpot, Pipedrive, Attio and the rest of the 1,284-tool catalog, plus anything internal via OpenAPI.

What about speed-to-lead SLAs?

Runs start from events, not polling schedules, so routing begins when the lead arrives — including 6pm Friday. We won't quote a minutes number until design partners give us a real one to quote.

Hand off the lead routing.

Join the waitlist and describe it in a sentence — or ask about white glove and our team will build and run it with you.

Early access · we'll email when your workspace is ready