Salesforce Lead Router with OpenClaw
Two documents do all the work: the routing rules and the team map. The agent has to take an owner from that map by exact name, and to leave a lead unassigned while naming the failing line whenever the two disagree. OpenClaw sits comfortably behind a job specified in two documents, hosted, with no local dependency.
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 OpenClaw
Preselected for this page — connect your OpenClaw 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 OpenClaw for this agent
A mismatch leaves it unassigned
Where the rules point one way and the map names nobody, the correct output is an unassigned lead and a sentence saying which line failed. Guessing an owner is the failure this rule exists to prevent.
Conversion is not wired
No account, contact or opportunity is created by this agent under any circumstances. The write surface is an owner, your routing fields and a note.
Before you fork
A rep leaves and their name is still in the team map. What happens?
Leads keep landing with somebody who is no longer working them, which is the one piece of maintenance this agent has. Update the map with the Salesforce usernames or queue names as your org spells them and the next lead routes correctly. Pointing a segment at a queue rather than a person is the version of this that survives staff changes.
Run it with a different agent
Put Salesforce Lead Router to work on OpenClaw
Free to start. Guided setup, a test run against staged conversations, and it's live.