Salesforce Lead Router

Salesforce assignment rules match a picklist and nothing more. They cannot read the sentence where a buyer says they need this before an October audit, and they cannot notice that the person filling in your form works at an account you have served for two years. This agent reads the lead the way a sales manager would, queries the org for anybody who already knows that company, sets a real owner, and writes down why. Junk keeps its unassigned status and gets a note explaining itself.

What people use it for

• Ownership, not a suggestion - Setting the owner puts the record into the list views and queues where that rep already works. Nobody has to spot a message and remember to claim something afterwards.
• Two objects, one duplicate check - Leads and contacts are both queried before a score exists, so the fourth person from a customer you already serve is routed as an existing relationship instead of pitched cold by somebody new.
• Routing a picklist cannot do - Territory by field value breaks the moment intent lives in free text. Rules written in English let a lead be routed on what they actually asked for, including a deadline mentioned in passing.
• Every route is auditable - Each assignment leaves a note naming the rule, the values behind it and the duplicate ids found. A disputed route gets settled by reading the record rather than by arguing at pipeline review.

Before you fork

What does it need inside Salesforce?

A connection allowed to read the Lead object, run SOQL across leads and contacts, update the owner and your routing fields, and create notes. You then write two things: the routing rules, and a team map naming real Salesforce users or queues, spelled the way your org spells them, since it assigns to whatever you wrote. Everything runs on standard objects, so nothing is installed.

Can it convert a lead or overwrite what a rep entered?

Neither one. Conversion is not among its tools, so no account, contact or opportunity is ever created by it. It writes the owner plus the routing fields you named, and leaves status, rating, source, campaign and free text alone. A value that looks wrong gets described in the note rather than corrected.

Our campaigns dump leads in bursts, what does that look like?

Every lead landing is one short run, so a 400 row list import is 400 runs on the day you import it. Point the trigger at the sources people actually work, and load purchased or scraped lists somewhere it is not watching. Disqualified leads finish early because they stop at the note and never reach Slack.