Allocator studio
How many agents do you have?
Conventional collections sorts by probability of default and works down the list. The allocator maximises expected recovered value per agent-minute. The gap between them is not a constant. It depends entirely on how scarce your capacity is. Move the slider.
Both strategies converge as capacity approaches full coverage: given enough agents to call everybody, ordering stops mattering. The edge lives where real operations live, at the left of this chart. Reporting only the flattering end of it would be the easy thing to do.
Who each strategy actually calls
Fifty-two accounts from the live queue, at the capacity you set. Highlighted rows are the ones only this strategy funds. The disagreements are the whole argument.
ranked by expected value per agent-minute · — of 52 funded
ranked by probability of worsening · — of 52 funded
The trade, in two accounts
These are real rows from the queue, picked because they are the clearest case of the two strategies disagreeing. Neither is a hypothetical.
Silence is a scored action
The accounts neither strategy funds are not an oversight. Most delinquents self-cure. Contacting them spends the most expensive resource in the business on someone who was already going to pay, and irritates them while doing it. So “do not contact” has a value in the objective, and wins on its merits. Invariant I9 makes this the only component allowed to produce a queue, so no path exists that quietly ranks by probability instead.
One caveat, stated plainly. The uplift shape the objective uses is modelled from published practice rather than measured here, because the servicing data carries no treatment history to measure it from. The logic beating risk-ranking is what this demonstrates. The magnitude stays badged simulated until a control arm produces it.