How to choose lead routing software

What lead routing software does

A routing tool sits between the moment a record is created and the moment a human is expected to act on it. It does four jobs. It matches the record to something already in the CRM, usually an account, a territory or an existing owner. It assigns an owner using rules you write. It notifies that owner through Slack, email or a task, often with an acceptance timer. And it records what happened, so you can answer why a specific lead went to a specific rep six weeks later. Some products add a fifth job, booking the meeting inside the form experience before the visitor leaves the page. Routing is not scoring, and the two get confused in demos. Scoring decides whether a record is worth a rep's time. Routing decides whose time. A tool that does both can hide a weak scoring model behind fast assignment. Ask the vendor to show the two as separate steps. The objects being routed matter more than most buyers expect. Routing leads only is the cheap case. Routing leads, contacts, accounts, opportunities and cases is a different product and usually a different price tier. Write down your list before the first call, because vendors quote against routed objects and record volume. The category page for the tools we track sits in our lead routing software directory, and the definition of the record type most teams start with is in our glossary entry on the marketing qualified lead.

Speed to lead math

Speed to lead is the reason most teams start shopping, and it is the easiest number to fake. Vendors quote the time between record creation and assignment. What buyers care about is the time between form submission and a human conversation. Those are different numbers and the gap is where the money goes. Break the clock into five pieces and measure each one today, before you buy anything. Form submit to record creation in the CRM. Record creation to enrichment returning a company match. Enrichment to assignment. Assignment to a notification the rep actually sees. Notification to first dial or first reply. Most teams find their worst delay is not assignment at all. It is enrichment waiting on a third-party lookup, or a rep who gets 40 Slack notifications a day and stopped reading them. Routing software fixes the middle of that chain and does nothing for the ends. Harvard Business Review's 2011 article The Short Life of Online Sales Leads, by James Oldroyd, Kristina McElheran and David Elkington, is the study most vendors cite for the claim that responding within an hour beats responding the next day. Read it yourself instead of the slide, then decide what response target your own team can staff. A one-minute routing rule is worthless if nobody is at a desk. Teams that want the rules written down before they shop can start from our lead routing rules template. If the bottleneck turns out to be the form itself, a scheduling-first product such as RevenueHero will move the number faster than a matching engine will.

Round robin versus account matching

Round robin distributes records evenly across a pool. Account matching sends a record to whoever already owns the related account. Nearly every argument about routing inside a sales team is really an argument about which of these two wins when they disagree. Round robin is fair and simple. It also breaks the moment two people from the same company fill out a form in the same week and get two different reps, who then both call. Account matching prevents that, but it needs a reliable link between the lead and an account record, and fuzzy company names, free email domains and subsidiaries all break that link. Ask any vendor exactly how matching works. Domain match only, or normalized company name, or a data provider lookup, or all three with a confidence threshold you control? What happens at low confidence, a fallback to round robin or a manual queue? LeanData built its reputation on this problem and prices accordingly. LeadAngel sells two-way lead-to-account matching as its core feature with routing layered on top. A practical answer for most teams is a hierarchy, not a choice. Match to an open opportunity owner first, then to the account owner, then to a territory, then round robin the remainder. Enterprise motions lean toward matching because named ownership is the whole point, and the rules usually mirror the territory planning work already done for the year. High-volume self-serve motions lean toward round robin because the accounts are new and there is nothing to match against. Write the hierarchy down before demos, then make each vendor build it in front of you.

CRM native versus dedicated tools

Every CRM can route. The question is what it costs you in admin time and in your ability to change a rule on a Tuesday. Salesforce Flow has no separate license and ships inside Sales Cloud editions, with Salesforce Platform Starter at $25 per user per month and Platform Plus at $100 per user per month billed annually as of September 2026 for people who need automation without full CRM. That looks free next to a $15,000 platform fee. The real cost is elsewhere. Routing built in Flow lives in admin tooling, not in an ops tool. Changing a territory means editing a flow, testing it in a sandbox and deploying it. Every change is a ticket. Flows also hit governor limits at volume, and debugging a failed assignment means reading error logs. Teams with one Salesforce admin and stable territories do fine. Teams that change routing weekly do not. Dedicated tools sell you a rule builder a RevOps person can read, a visual trace of why a record went where it went, and someone to call when it breaks. Distribution Engine is the cheapest serious version of that for Salesforce shops, with published pricing of $20, $35 and $55 per user per month billed annually across Starter, Advanced and Unlimited, a five-license minimum, and a separate Booking Engine from $10 per user per month. A useful test before you buy anything: count how many routing changes your team requested in the last six months and how long each took. If the answer is two changes and a day each, keep the CRM. If it is twenty changes and two weeks each, the tool pays for itself in admin time alone.

Named tools and prices

Prices below are as of September 2026 and come from vendor pricing pages except where noted. Chili Piper publishes platform pricing: Routing and Scheduling at $15,000 a year with 15 seats included and extra seats at $45 per seat per month, Experiences at $42,000 a year with 30 seats, and ChiliCal standalone scheduling at $12 per user per month with a 200-seat minimum. Both platform plans are annual only, so a ten-rep team still pays the full $15,000. Default lists Growth at $15,000 a year and Scale at $36,000 a year, with rep seats added on top at $540 per user per year for routing plus scheduling, or $240 per user per year for scheduling only. LeanData does not publish prices; Vendr's marketplace data, based on 318 transactions, puts the median contract at $23,100 a year with a range of $7,056 to $78,960. LeadAngel and Qualified are both quoted rather than listed, and that vendor is now owned by Salesforce, which completed the acquisition in April 2026 according to Salesforce's Form 10-Q. At the low end, Calendly routing needs the Teams plan at $16 per seat per month billed annually before you get routing forms, round robin or CRM routing, and routing by Salesforce ownership requires Enterprise, which starts at $15,000 a year with a 50-seat minimum. The same limit applies if you are shopping purely for a round robin scheduler. RevenueHero charges a $79 per month platform fee plus $25 per user per month on yearly billing for Inbound Essentials. The spread is wide because these are not the same product. Anything under $10,000 a year is a distribution and booking tool. Anything over $20,000 a year is sold as matching and governance infrastructure.

Holdouts and fairness rules

A holdout is any rule that stops a record reaching the rep the base logic picked. Vendors rarely demo them, and they cause most of the post-launch arguments. The common ones are worth listing so you can ask for each by name. Out-of-office and vacation holds, so a rep on leave stops receiving inbound. Capacity caps, so a rep who already has 40 open leads stops receiving more until they work them. Ramp weighting, so a new hire gets a third of a full share for their first month. Working-hours windows, so a lead at 2am waits for the morning rather than sitting unread. Acceptance timers with automatic reassignment, so an unclaimed lead moves after ten minutes instead of dying. Named-account holdouts, so strategic accounts skip the pool entirely. Suppression rules, so existing customers, competitors, students and job applicants never enter the pool at all. Ask how each of these is configured, who can change it, and whether changing it requires a deploy. Then ask the harder question: does the tool rebalance after a holdout? If a rep is skipped while on vacation, do they get extra volume on return, or is the shortfall permanent? Reps notice, and a routing system reps believe is unfair gets worked around within a quarter. Fairness also depends on agreement about what counts as a routable record in the first place, which is a lifecycle question instead of a routing one. Settle it first using our lead lifecycle stage definitions, then write the holdouts. Doing it the other way round produces rules that describe exceptions to a definition nobody wrote.

What breaks after rollout

Routing tools fail quietly. Nothing throws an error, records just end up in the wrong place and nobody notices for a month. Duplicates are the first problem. Two records for the same person route twice, to two reps, who both call. The tool did exactly what you asked. The fix is deduplication upstream, not a routing rule, and it is worth settling with a documented set of CRM deduplication rules before go-live rather than after the first complaint. Enrichment failures are the second. Matching that depends on a data provider inherits that provider's coverage gaps, so records from small companies, personal email domains and non-English company names fall through to whatever fallback you set. Check the size of that fallback bucket weekly for the first quarter. Rule sprawl is the third and the most expensive. A clean set of eight rules becomes 60 over two years because every exception gets its own branch and nobody deletes anything. Order matters in most rule engines, so a rule added at position three silently changes what rules four through 60 ever see. Put a quarterly review on the calendar and delete rules that fired zero times. Ownership drift is the fourth. Territories change in January, the account owner field updates, and routing rules that reference a hardcoded user ID keep sending leads to someone who moved teams. Reference roles or queues rather than named users wherever the tool allows it. Last, watch the audit trail. If you cannot answer why a specific lead went to a specific rep, you will lose every dispute by default, and disputes are how routing systems lose credibility.

What to test in a demo

Bring your own data. A vendor demo on vendor data proves nothing about your matching rates. Export 200 real inbound records from the last quarter, including the messy ones, and ask each vendor to run them through their matching logic and report how many matched an existing account, how many matched at low confidence and how many fell through. Compare that number across vendors and you have the only benchmark that matters. Then ask for four things to be built in front of you rather than described. Your full ownership hierarchy, from opportunity owner down to round robin fallback. One holdout, such as a capacity cap with rebalancing. One mid-quarter change, such as splitting a territory, timed from request to live. And one failure case, such as an enrichment timeout, so you can see what the system does when a dependency is down. Ask who can make each change. If the answer is a Salesforce admin, you have bought a CRM-native tool with a subscription attached. Ask for the audit view on a single record and read it out loud. If you cannot explain the path to a rep from that screen, the tool will not settle disputes. Finally, ask about total cost at next year's volume, not this year's, because renewals climb with routed records and seats rather than with value delivered. Two head-to-heads cover the common finalist pairs: the Chili Piper and LeanData comparison for teams weighing scheduling against matching, and the Default and Qualified comparison for teams routing high-intent website traffic.

When not to buy

Several situations look like a routing problem and are not. If inbound volume is under a few hundred records a month and one person triages them, a shared queue and a documented rule work fine and cost nothing. Routing software pays off when volume exceeds human attention or when ownership rules are contested, and neither is true at that size. If your CRM data is bad, routing on top of it just distributes the mess faster, with an audit trail that makes the mess visible to more people. Fix duplicates, company name normalization and account ownership first. A routing rollout on dirty data usually ends with the tool blamed for decisions the data caused. If reps are not working the leads they already have, faster assignment changes nothing. Check the number of inbound records assigned in the last 30 days with no logged activity. If that number is high, the problem is capacity or incentive, not distribution. If marketing and sales disagree about what qualifies, routing will make the disagreement worse by forcing an automated answer to a question nobody settled. And if you are shopping because one deal went to the wrong rep, wait. Single incidents are cheap to fix manually. The case for buying is a pattern: repeated ownership disputes, a measured response-time gap you can size in pipeline, or a change backlog your admin cannot clear. Bring one of those three to the budget conversation, or expect to lose it.

Buyer checklist

• List every object you need routed (leads, contacts, accounts, opportunities, cases) before any vendor call, since quotes are built on that list.
• Measure your current speed to lead in five segments, from form submit to first dial, and find which segment is actually slow.
• Write your ownership hierarchy on one page: opportunity owner, account owner, territory, then round robin fallback.
• Ask each vendor how lead-to-account matching works and what happens below the confidence threshold.
• Run 200 of your own past inbound records through each vendor's matching and compare match rates.
• Request holdouts by name: vacation holds, capacity caps, ramp weighting, working hours, acceptance timers, named-account skips.
• Time one mid-quarter routing change from request to live, and confirm who is allowed to make it.
• Count routing changes requested in the last six months to decide between CRM-native automation and a dedicated tool.
• Fix duplicates and account ownership in the CRM before go-live, not after the first double-call complaint.
• Get a written price at next year's record volume and seat count, not the numbers you have today.

Related