Rep-level distribution caps based on configurable criteria
under review
Taylor Jennings
Distribution caps in Distro apply uniformly and don't account for rep-level conditions. There's no way to dynamically adjust how many records a rep receives based on their current state, such as how many open leads they already own, or to set different caps based on record attributes like ARR or product line.
Admins should be able to configure dynamic distribution caps at the rep level using criteria they define. For example, stop routing to a rep when they already own more than 100 open leads, or limit a rep to 5 enterprise accounts per week while allowing unlimited SMB. Caps should adjust automatically as conditions change, without manual intervention.
Teams scaling outbound operations at high volume can't trust flat daily caps to manage rep capacity accurately. A rep who works through leads quickly gets starved; a rep with a backlog keeps receiving records they can't action. Dynamic criteria-based caps would let routing reflect actual rep workload in real time.
Taylor Jennings
Merged in a post:
Route records to a rep only when their current account count falls below a configured threshold
J
Jaime Stilwell
Distro has no way to condition assignment on how many accounts a rep currently owns. Teams running account replenishment motions, where reps receive new accounts only when their active count drops below a target, have to monitor and reassign manually.
Admins should be able to set a minimum account count threshold per rep. When a rep is at or above the threshold they're skipped in routing; when they drop below it they become eligible again.
This is the floor equivalent of Distro's existing cap, and the two together would give admins full control over both ends of a rep's assignment range.
Taylor Jennings
Merged in a post:
Capacity and workload-based routing
Taylor Jennings
Admins have no way to factor in a rep's current workload when routing records. Round-robin and rules-based routing treat all reps as equally available regardless of how many open records they're already carrying.
Requested behavior: Allow admins to set capacity limits per owner in Distributions. When a rep hits their cap, records route to the next available owner or a fallback Team.
Why it matters: Prevents rep overload during high-volume periods, supports tiered capacity models, and ensures fair distribution without manual intervention.
Taylor Jennings
updated the status to
under review
Taylor Jennings
updated the status to
planned (next)
Taylor Jennings
Allow admins to set maximum record limits per owner in Distro rules. When an owner reaches their cap, records would be routed to the next available owner or a fallback queue. Use cases include: balancing workload across reps, preventing rep overload during high-volume periods, and supporting tiered capacity models.