How Are RevOps Teams Handling Lead Routing with Multiple Eligible Reps? Experiences with Predictive Tools Like Signal...

·Aug 19, 2026 06:18 PM(edited)·

Hi everyone, question for the RevOps / Sales Ops folks here: How are you guys handling lead routing when multiple reps are technically eligible for the same lead? There are tools that instead of rules, use historical conversion data an AI to decide which rep is the best fit. Has anyone here tried Lithium Six (Isotopelabs.com) or another predictive lead-routing tool? Would love to hear what worked / didn’t work. Augusto

3 comments

· Sorted by Oldest

Jason M.
·
·
Round robin?
👍1
ian.mcpherson
·
·
I'll 2nd round robin. Its simple and fair. Isotope seems cool but I would guess the usefulness really depends on what you sell, the volume of leads, number of reps, and whether you value tenure or churn through new reps often. For example, their scoring seems to be focused on consumer and home services. And if you're not rolling out active, parallel training & enablement, as well as monitoring and correcting for the mix of leads, I would worry that you're going to create a secret disadvantaged class of reps who will then be on unfair comp plans.
Augusto B.
·
·
Hi ian.mcpherson, thanks for the insight. Yeah, I think the enablement/fairness point is legit. To my understanding, Isotope doen't force the routing decision. It adds a predicted close rate to each eligible rep, so the person managing distribution has another data point for deciding where to send the lead. This means that I could still disregard the recommendation and assign a lead to an underperforming rep, someone on a coaching plan, or someone who has other strategic value to the business. So my understanding is that it's more of an informed distribution layer on top of the existing rules rather than replacing them. That said, I'm still digging into it. I'm interested in the broader question of predictive routing, so I'll look at Lithium Six and some other solutions and see how they handle exactly these concerns. TY!