Salesforce Lead Router with Claude Code
A lead lands and four things happen in order: read every field the rules mention including the free text, run two SOQL queries, score against the rules, then set an owner. Setting that owner is a real write, since the record appears in somebody's queue the moment it happens. Claude Code works through a fixed sequence like that without dropping the step that comes before the write.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Web - Request Pricing
Marta Kjeldsen, Nordhavn Logistik A/S
EmailUnassigned Leads queue
NoteTitle: Director of Warehouse Operations. Country: Denmark. Employees: 1,200. Industry: Transportation and Logistics. Email: m.kjeldsen@nordhavnlogistik.dk, phone supplied. Message: nine distribution centres report out of three separate systems and we want one layer across all of them before the Q1 stock freeze. Budget signed at 900,000 DKK, procurement runs a vendor security review first, and I am the person who signs.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Salesforce
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Routing rules
What separates a lead worth a rep's morning from one worth nothing - the industries, sizes, countries, titles and signals you route on, the fields the agent may set, and what disqualifies somebody outright.
Team map
Who takes which kind of lead, written with the Salesforce usernames or queue names exactly as they appear in your org, so the agent assigns to a real owner rather than to a nickname.
Runs on Claude Code
Preselected for this page — connect your Claude Code account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Claude Code for this agent
Both objects, then a score
One query over Lead and one over Contact, both finished before any scoring starts. Somebody already sitting under an account is not a fresh lead, and learning that afterwards is worth nothing.
Free text is a field too
A deadline mentioned in a message box changes the routing and is invisible to an assignment rule. Reading the whole record is the part of this job picklists were never going to cover.
Before you fork
Can it take a lead that already belongs to one of our reps?
No. An open lead owned by another rep stays theirs, which is what the Lead query is for, and the agent writes the owner plus the routing fields you named and nothing else. Status, rating, source, campaign and anything a rep typed are outside its reach. A route you disagree with is one owner field to change.
Run it with a different agent
Put Salesforce Lead Router to work on Claude Code
Free to start. Guided setup, a test run against staged conversations, and it's live.