A hot lead that reaches the wrong rep — or no rep — doesn't file a complaint. It just goes cold. Lead routing is the plumbing between marketing's output and sales' input, and it fails quietly: the lead sits in an unwatched queue, assignment fires to a rep who left last quarter, or two automations fight and the louder one wins. Here's how the routing toolbox actually works and where each tool breaks. If you also run Marketing Cloud Account Engagement (Pardot), the handoff between the two systems is part of the story too.
Salesforce's native assignment rules evaluate a lead against ordered criteria and assign it to a user or queue. They're simple, fast, and right for the majority of orgs: route by territory, by segment, by product interest — top-down through the rule list until one matches.
Where they break: complexity accretion. Rules grow one exception at a time until nobody can predict what a given lead will do. We took over an org running 59 assignment rule entries — layered over years, several referencing departed employees — and replaced them with one flow (that story is on our case studies page). Assignment rules also can't do the things modern routing wants: round-robin distribution, capacity awareness, or looking up related records. When you're forcing those behaviors through rule gymnastics, you've outgrown the tool.
Flow-based routing can do essentially anything: weighted round-robins, matching leads to existing account owners, checking rep capacity, timed escalations, notifications to Slack or email. If assignment rules are a light switch, flows are programmable wiring.
Where they break: ownership. A flow is software — it needs documentation, testing after every org change, and someone who understands it after the builder leaves. Undocumented routing flows are among the most dangerous objects in an org: everyone is afraid to touch them, so exceptions get bolted on around them, and now you have two routing systems disagreeing. Build flows deliberately, name them honestly, document the logic in-line, and delete the assignment rules they replace — running both is how leads get assigned twice or zero times.
Queues hold leads no individual owns yet — fine as a routing destination, dangerous as a routing strategy. A queue without a working agreement (who pulls, how often, what's the SLA) is a place leads go to age. Every queue needs an owner of the queue itself, a response-time expectation, and a report someone actually reads. If a queue's average lead age is measured in days, it's not a buffer — it's a graveyard with a dashboard.
For marketing-sourced leads, routing begins before Salesforce: Marketing Cloud Account Engagement (Pardot) decides when a prospect becomes a lead worth routing, via scoring thresholds and completion actions that create or update the Salesforce record. Two integration rules keep this sane:
Routing exists to compress time-to-response, so measure that, not rule elegance: time from lead creation to first owner assignment (should be minutes) and time from assignment to first sales touch (should be same-day for hot leads). Build both as reports, review weekly for a month after any routing change. Speed-to-lead is one of the few sales metrics where improvement shows up in win rates almost immediately.
Untangling routing — especially the cross-platform kind — is bread-and-butter Salesforce work for us. If nobody at your company can draw the routing diagram from memory, let's talk.
Founder of Thompson Technology. Salesforce and Account Engagement consultant for B2B companies.
Connect on LinkedIn →Want an outside read on where your revenue engine is leaking? That’s a 30-minute conversation — no deck, no obligation.
