The problem it solves
An expensive portal lead assigned to an agent who is mid viewing, on leave, or simply at capacity, sits there. Nobody is at fault and nothing is wrong with the assignment, but the lead goes cold while a colleague with time available never sees it. Manual reallocation solves this only when a manager happens to notice.
Make the rule impersonal
The reason repooling causes friction in some brokerages is that it feels like a judgement on the agent. It stops feeling that way when the condition is written down, applies to everybody, and fires without anybody deciding. A lead returns to the pool because the response window passed with no qualifying activity, not because somebody decided the agent was slow.
- Response window defined per pipeline stage
- Qualifying activity defined by the workspace, for example a call, a message or a note
- The same rule for every agent
- It fires automatically rather than being triggered by a manager
Define qualifying activity carefully
This is the setting that determines whether repooling helps or becomes a game. If opening the record counts as activity, everybody opens records. If a logged call or message counts, the rule measures what you actually wanted.
Preserve the history
Redistribution without an audit trail is just losing track of who had a lead. Every assignment, claim, release and breach should stay on the record, so that a lead that has passed through three agents can still answer who held it, for how long, and what they did.
- Immutable assignment history
- Reason recorded for each change of owner
- Claim recorded with claimant and timestamp
- Reportable by agent, team and branch
Start conservative
A window nobody can meet produces constant repooling and a team that stops trusting the system. Start with a target the team can actually hit during business hours, watch the breach rate, then tighten.
How Clix handles it
A lead enters the Clix pool by direct routing, by a timed claim expiring, or by passing its response SLA without qualifying activity. Eligible agents claim from the pool and a fresh response window starts, the claim is recorded with claimant and time, and the assignment history is immutable.