When reassignment volume signals a design problem

Reassignment counts are easy to extract from most support apps and easy to misuse. A spike can look like handlers avoiding hard work. In many Malaysian contact centres we review, the spike tracks ambiguous ownership: two queues claim the same product variant, or escalations bounce because the next team’s entry criteria changed last quarter and nobody updated the handler guide.

Before coaching individuals, chart reassignments by reason if your tools allow — wrong queue, need specialist, customer changed product, duplicate ticket. If “wrong queue” dominates, the fix is naming and routing, not motivation posters.

Walk a sample of reassigned tickets with a senior handler and a specialist from the receiving team. Ask each where they would have sent the case on day one. Disagreement is useful; it shows the boundary language that reports cannot invent.

Small wording changes on queue descriptions often cut reassignments more than new automation. Pair those changes with a two-week watch on handle time for the affected queues. If handle time rises while reassignments fall, you may have concentrated harder work without adding capacity — another finding worth putting in front of leadership early.