Business & Revenue OpsFree
Round Robin Lead Assignment Rules
Send your rep list with capacity, hours, and time zones, get a weighted rule table and a load simulation before you turn it on.
River's Round Robin Lead Assignment Rules tool builds the weighted rotation a lead pool should actually run on, not the equal-share default most routing setups start with. Send each rep's capacity weight, working hours, and time zone. It builds a rule table covering the full week: the business-hours overlap, the evening stretch only some reps cover, and the after-hours and weekend backlog every team eventually has to route somewhere. Every rule ships with a load simulation projecting each rep's resulting share before anything goes live.
Most routing platforms already support the configuration half of this. LeanData's own round robin product lets an admin set a weight per rep and skip anyone on vacation, outside working hours, or already at a daily cap, and its distribution dashboard reports fairness only once leads have routed. Neither tells anyone what a specific roster's weights and after-hours default will actually produce before a single lead moves. This tool runs that projection first, against the roster and hours it is given, so a skewed default gets caught as a number, not a rep's complaint.
On a worked run for Corvane Systems, a B2B software company, 5 reps spanning Eastern, Central, and Pacific time split 200 leads a week by a 3:3:3:3:1 capacity weight. Routing the after-hours backlog to whichever rep opened earliest, the naive default, left one rep 15.9% under her target share for the week. Splitting that same backlog by full-team weight instead cut the worst-case deviation to 6.8%, a 57.1% reduction. It pairs with the rule table this feeds into and the account-level ownership question once a lead converts.
What a capacity weight doesn't cover on its own
A capacity weight only describes how big a rep's share should be, not when that rep is actually available to receive it. Weighted round robin itself is a static setting, a human-assigned multiplier that stays fixed until someone changes it. Once coverage gets uneven across a day, whatever rule fills the resulting gaps ends up carrying more of the real skew than the weights do. Most teams tune the weight once and never look twice at the backlog rule sitting underneath it.
On Corvane Systems' roster, the after-hours and weekend bucket alone is 108 of the week's 168 hours and 36 of its 200 weekly leads, and every one of those leads has to land on somebody. Assigning that backlog to whichever of the three earliest-opening reps happened to be online first looked harmless until it was checked against the target. It left one rep at 84.1% of her target share for the week, an eleven-point gap the rest of her rotation never closed on its own.
The fix is not a bigger weight, it is a backlog rule that does not structurally exclude anyone. Splitting the after-hours bucket by the full team's weight instead of just the earliest openers brought the worst-case deviation from 15.9% down to 6.8%. Re-run the same simulation whenever the roster changes: a new rep joining, a time zone shifting, or someone starting a multi-week leave. The leave case alone pushed one rep 10.0% over his own target with no relief on the window he would normally share.
How it works
Send your roster
Each rep's capacity weight, working hours, and time zone, plus your weekly lead volume and arrival pattern.
Build the rule table
A weighted rotation covering business hours, evening overlap, and the after-hours and weekend backlog.
Simulate a week
A full week of lead arrivals run against the rule, projecting each rep's resulting share.
Adjust and re-run
Change the backlog policy or the roster, then simulate again before anything actually ships.
What you get
- The full weighted rule table, covering business hours, evening overlap, and after-hours backlog
- A week-long load simulation projecting each rep's resulting share before the rule goes live
- The naive after-hours default named and measured, instead of discovered after reps complain
- A leave and vacation scenario simulated against the same rule, not handled ad hoc
- Each rep's worst-case deviation from target share, stated as a number before rollout
- A specific after-hours policy fix, with the resulting deviation calculated before you adopt it
Common questions
We already use a routing platform with weighted round robin. Why do we need this?
Configuring a weight is not the same as knowing what it produces. LeanData's own documentation describes setting a weight per rep and skipping anyone on vacation or outside working hours, but its fairness reporting only runs after leads have already routed. This tool projects the resulting split first, against your actual roster and hours, before a single lead moves.
Our reps have different close rates, not just different hours. Does the weight account for that?
Not by default. The weight here is capacity, how much of a rep's available working time can absorb leads, not how well they convert once assigned. If you want conversion history to set that weight instead, say so in the context field and the rule table will build around whichever weighting basis you actually want to run on.
How does the after-hours and weekend backlog actually get assigned?
It gets priced two ways so the difference is visible: routed only to whichever reps happen to open earliest, and split across the full team by weight instead. On the worked example, the first option left one rep 15.9% under her target share; the second cut that to 6.8%. The rule table ships with whichever policy you choose.
What happens to the rule when a rep goes on leave?
The simulation re-runs with that rep's weight removed from the active pool for the affected window, not just deleted from the roster. On the worked example, one remaining rep absorbed an entire evening window alone once the colleague who normally shared it went on leave, ending the week 10.0% over his own target. The rule table can name a standing backup for exactly that case.
Does this replace the routing tool we already have, like Salesforce or HubSpot?
No. It produces the rule table and the simulation behind it, the specific weights, hours, and backlog policy your platform should actually be configured to run. You still implement it in whatever tool currently owns your lead routing rules; this is what checks those settings are correct before you save them.
How is this different from the account assignment pack?
A different layer entirely. This sets the rotation that decides which rep a new lead reaches first. Account assignment governs who owns a company for the long run once it is already a customer or an open opportunity, a separate decision this tool does not make.
Once a lead is assigned, how do we know it's actually getting worked fast?
That's a separate, downstream question, and a deliberate boundary. This tool decides which rep a lead should reach first; a speed to lead audit traces whether that rep, or any rep, actually responds inside the target window once the lead lands with them.
Round Robin Lead Assignment Rules
Fill in the form and your workspace opens with the work already underway.