Routing needs two decisions: which eligible ticket goes next and which eligible agent receives it. The supported model orders eligible tickets by priority and then creation time. Spare-capacity assignment then prefers available space, while round-robin advances its configured agent order. Keep these decisions separate when investigating a surprising assignment. An older ineligible request should not block newer eligible work, and a queue’s saved definition does not itself create assignment evidence.
Check candidate tickets and eligible agents separately, then run local routing. Later requests vary capacity or queue conditions so an earlier assignment cannot be assumed. The workspace models selected queue behavior and never changes a real agent account. Use the resulting saved owner as the final assignment evidence.
Worked example: assignment methods and order.