Skip to main content

Lead routing in Salesforce: stop letting good leads die in the queue

Jonathan Adams··5 min read
salesforcelead-managementautomation
Share this post

Let me paint you a picture. A prospect fills out a demo request form on your website at 10:14 AM on a Tuesday. They are interested, they have budget, and they are actively evaluating solutions. Your form works great. The lead lands in Salesforce. And then it sits there.

By the time someone picks it up on Thursday afternoon, that prospect has already had two calls with your competitor and is leaning their direction. Not because your product is worse. Because they showed up first.

This is not a people problem. It is a routing problem. And it is fixable.

Why lead routing matters more than you think

Speed to lead is one of the most well-documented factors in conversion rates. The data is clear: responding within five minutes makes you dramatically more likely to connect with a prospect than responding within thirty minutes. And yet most B2B companies measure their response time in hours, not minutes.

The usual culprit is not lazy reps. It is a routing setup that either does not exist or was built three years ago when the team was half the size and the territory map looked completely different.

The three building blocks of solid lead routing

You do not need a PhD in Salesforce administration to get this right. You need three things working together.

1. Assignment rules that reflect your actual sales org

Salesforce lead assignment rules let you route leads based on criteria like geography, company size, industry, product interest, or any field on the lead record. The key is making sure these rules match how your team actually operates today, not how it operated when the rules were first written.

If you have named accounts, route those leads directly to the account owner. If you split by territory, use state or country fields. If you have a BDR team that qualifies before passing to AEs, route to a BDR queue first and build the handoff from there.

The biggest mistake here is trying to get too clever. Start with the primary routing logic that handles 80% of your leads correctly, then layer in exceptions.

2. Automated task creation so follow-up is mandatory

Routing a lead to the right person is only half the battle. You also need to make sure they actually do something with it. That means creating a follow-up task automatically the moment a lead is assigned.

Set the task due date to the same day for high-priority leads. Give it a clear subject line like "New inbound lead - follow up within 1 hour." Make the task visible on the rep's home page so it cannot be missed.

This is not about micromanaging your team. It is about building a system that does not depend on someone remembering to check the lead queue between meetings.

3. Escalation for leads that slip through

Even with good routing and automated tasks, leads will occasionally go untouched. Maybe the assigned rep is out sick. Maybe they are buried in a deal that is about to close. It happens.

What should not happen is that lead sitting there for days with no action. Build an escalation flow that triggers when a lead has not been contacted within your defined SLA. Route it to a manager or a backup rep. Send an alert. Whatever your process needs to be, automate it so nothing falls through the cracks.

A practical example

Here is what a simple but effective lead routing setup looks like for a mid-size B2B company:

  1. Lead comes in from web form, event, or third-party source.
  2. Assignment rule fires based on lead source, geography, and company size. Named account leads go to the account owner. Everything else goes to the BDR team queue.
  3. Round-robin assignment distributes queue leads evenly across available BDRs.
  4. Follow-up task is created with a one-hour due date for demo requests and a same-day due date for content downloads.
  5. Escalation triggers if the task is not completed within four hours, notifying the BDR manager and reassigning if needed.
  6. Qualification handoff moves the lead to the appropriate AE once the BDR confirms it is sales-ready, with a warm introduction task created automatically.

None of this requires custom code. All of it can be built with standard Salesforce tools: assignment rules, Flow, and a bit of thoughtful configuration.

Common mistakes to avoid

Over-routing to managers. If every edge case goes to a sales leader, you have not solved the routing problem. You have just moved the bottleneck.

Ignoring lead source in your logic. A demo request and a whitepaper download should not get the same urgency treatment. Weight your routing and SLAs based on intent signals.

Setting it and forgetting it. Your routing rules need to evolve as your team changes. Add a quarterly review of lead routing to your ops calendar. It takes 30 minutes and prevents months of misrouted leads.

Where to start

If your current setup is "leads go into a queue and someone grabs them eventually," you are already behind. But the fix does not have to be a massive project.

Start with this: map out your current lead flow from form submission to first contact. Time it. Identify where the delays are. Then build the assignment rules and automation to close those gaps.

Your leads are already coming in. Make sure you are giving them somewhere to go.

Need a hand setting this up? Reach out and let's talk through it.

Get new posts in your inbox

No spam, no fluff. Just practical insights on Salesforce and technology.

Your privacy matters. Privacy Policy