Why letting agents pick tickets fails
In many teams, agents choose what to work on from the queue. It feels flexible, but quick and easy tickets get picked first, awkward ones sink to the bottom, and the oldest customers wait longest. Response times look fine on average while some customers wait days.
Assigning tickets automatically fixes this, but the method matters.
Round-robin assignment
Round-robin hands new tickets to agents in turn: first to A, then B, then C, then back to A. It is simple to understand and spreads the count of tickets evenly.
Its weakness is that it ignores how much work each agent already holds. An agent stuck on three long investigations still receives the next ticket, while a colleague who has cleared their queue waits.
Load-based assignment with a cap
Load-based assignment sends each new ticket to the available agent holding the fewest open tickets. Add a ceiling, such as 15 open tickets per agent, and nobody is buried while others sit idle. When everyone is at the cap, new tickets wait in the team queue until someone has room.
This is how auto-assign capping works in M-Reply. Team leaders set the ceiling, and the live floor dashboard shows how many tickets each agent holds against it and who is on a break.
Route by team first
Before choosing an agent, choose the team. Billing questions should not land with the technical team, and bookings should not land with accounts. Map each mailbox or type of request to a team, then assign within the team.
- Give each team its own email signature, so customers see who is helping them.
- Let agents transfer a ticket to another team when it was routed wrongly, with an internal note explaining why.
- Use bulk assign and transfer to rebalance the queue after a holiday or a sudden spike.
Which method to use
Round-robin suits small teams where most tickets take about the same effort. Load-based assignment with a cap suits teams of five or more, or any team where some tickets take minutes and others take days. Whichever you pick, check the result weekly: if one agent always holds the oldest tickets, the rules need adjusting.