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.
