Assigning a lead is the easy part
Most routing tools stop at assignment. Gradient Works handles account scoring, lead matching, routing and follow-up analysis.
01The problem
Assigned isn’t the same as worked
The lead fires. The assignment lands. And then nothing happens.
- Leads route to a rep who has no relationship with the account.
- Matching fails on subsidiaries, free-mail domains and inconsistent company names.
- Routing rules break and nobody can explain why.
- There is no record of why a record went where it went.
02The approach
Route every signal, inside Salesforce
Match the lead to the right account, send it to the rep who already owns that relationship, and keep a full audit trail — all in Flow, where your admin can actually inspect it.
Routing is judged on the wrong metric. Time-to-assignment is easy to measure and easy to optimise; whether the assigned rep was the right one, and whether anything happened afterwards, is the part that shows up in pipeline.
03End to end
How it works
- 01
Match
Lead-to-account matching that handles the messy cases rather than failing on them.
- 02
Route
Round robin, weighted assignment, load balancing or territory assignment, on any object.
- 03
Assign
Ownership lands with the rep who already knows the account.
Learn about Routing - 04
Audit
Assignment Histories record every ownership change, queue-based or direct.
04Proof
What customers say
We’ve automated our MQL distribution process with Gradient Works, which has been instrumental to scaling our sales organization for the next stage of our company’s growth.
Each AE shouldn’t have more than 100 accounts in their name. More than that takes away our ability to work them.
05Questions
Frequently asked
Why does routing break so often?
Because it usually lives outside the CRM, which means the person who owns the CRM cannot see the logic. Keeping routing in Flow with a full assignment history makes a broken rule a five-minute investigation rather than a support ticket.
What about lead-to-account matching?
Subsidiaries, free-mail domains and inconsistent company names are the normal case, and matching is built for them. Genuinely ambiguous records get flagged rather than silently assigned.
Can it route objects other than leads?
Yes — leads, accounts, opportunities and custom objects.
Can I debug an assignment from an AI agent?
Yes, and it is the fastest-paying use of the MCP: ask why a record was assigned the way it was and get the matching logic, the rule and the history in one answer.
Learn about the MCPMake every handoff explainable
Show us your current routing setup and we’ll tell you what we’d do about it.