Help center Cases and collaboration Configure queue auto-assignment and understand round-robin eligibility Updated Wednesday, October 28, 2026 · Marcel Gravelle Queue auto-assignment helps a team distribute open case work using configured eligibility and ordering rules. It is useful when a shared intake queue needs an explicit assignment process. The result depends on more than the round-robin switch: agent/team membership, status, working hours, capacity, queue hours and asset eligibility can all affect who receives work. Test the combination that matches your operating model. At a glanceFor: queue administrators, support operations leads and supervisors. Applies to: Supportbench Core.Start here: Settings → Organization → Queues → Auto-Assignment Define the coverage model before enabling assignment · Choose the availability rule deliberately · Understand the independent options · Configure and save the queue · Verify a service pass and the final owner · Example: a specialist equipment queue · Troubleshoot assignment results Define the coverage model before enabling assignment Decide which queue is responsible for which work, who may receive it, and how the team handles times when nobody is eligible. Confirm the selected agents or team members are active and suitable for the cases. Keep a supervisor view for work that remains unassigned or receives an unexpected owner.Use a controlled queue or approved training cases for initial validation. Enabling assignment on a busy production queue is an operational change, not merely a display preference. Agree a review window and who can correct assignment if the configuration does not behave as intended.Open cases can be reconsideredThe current assignment processor considers open Cases in an active round-robin-enabled queue, including cases that already have an owner. Do not describe this as a one-time operation that only fills empty ownership. Check existing open work and verify final owners after service processing. Choose the availability rule deliberately Availability ruleWhat the mode checksOperational implicationJust working hoursThe agent’s configured working day/hours. The mode does not use online/offline status as its eligibility gate.An agent within working hours can pass this mode even if their current status would not pass an availability-based mode.AvailabilityThe agent’s qualifying availability status, without checking their working hours in this mode.Do not assume the agent’s work schedule prevents assignment. Away is nonzero and can remain eligible.Availability and working hoursBoth the availability-status gate and the agent’s working day/hours.Use when both conditions fit the staffing model, and test an in-hours and out-of-hours example.Other eligibility requirements still apply: the agent must be active/nondeleted, eligible for round-robin case routing and within applicable capacity rules. Selecting a mode does not override every other gate. A status label by itself is not a complete statement of assignment eligibility. Understand the independent options OptionWhat to considerRound-robin agents and teamsThe candidate population. Selected teams expand to their members; review current membership and individual eligibility.Use Case loadChanges candidate ordering to consider the implementation’s case-load measure. It does not guarantee equal total workload or equal effort per agent.Use queue hoursAdds the queue’s own local working-window gate. It is separate from agent working hours in the availability mode.Use asset ownerRequires a compatible assigned asset/category relationship for a candidate. It is not a guarantee of an automatic fallback owner.With Use Case load, ordering considers currently owned cases created within the relevant window: the configured queue shift start when available, otherwise a rolling 24-hour UTC window. Tie-breaking also considers profile start time and assignment history. Without it, ordering primarily follows last assignment and profile start time. Treat this as an assignment heuristic, not a measure of case complexity or all outstanding effort.With Use asset owner enabled, a case without an asset can stop that agent-search pass, and a case with no compatible candidate does not receive a fallback merely because the option is enabled. Review asset/category assignments and your process for missing asset information before relying on asset-directed distribution. Configure and save the queue Open Settings → Organization → Queues with permission to administer queues. Open the queue whose assignment process you are changing.Review the queue’s active state, working hours and existing open work. Confirm this is the intended intake or work queue.Open Auto-Assignment and enable Enable round robin.Select Round-robin agents and teams. Check current team membership and individual routing/capacity eligibility.Choose Availability rule: Just working hours, Availability, or Availability and working hours. Use the distinctions above rather than assuming every mode excludes Away or Offline.Choose Use Case load, Use queue hours and Use asset owner only when each option matches your process. They are independent choices.Save the queue through the editor’s save action and reopen it to confirm the stored selections. Then run a controlled assignment check. Verify a service pass and the final owner Assignment is processed by the service; saving the queue does not promise immediate assignment. The current service duty uses a 90-second cadence, but scheduling, processing time and eligibility can affect when a particular case changes. Avoid a customer-facing promise that assignment always occurs within exactly 90 seconds.Record the test case’s queue, status, current owner and asset. Include an already-owned open case when checking the impact on existing work.Confirm a selected agent’s status, working hours, capacity and assigned asset/category relationships for the chosen mode.Allow the assignment service to process the queue, then inspect the final owner and case history.Test a case with no eligible candidate, an out-of-hours situation when applicable, and a missing/unmatched asset when using asset routing.Observe another pass when testing already-owned work. Confirm that repeated processing fits the intended ownership model.Review other workflows that may change the owner or queue afterward. Keep the supervisor view and correction process available. Example: a specialist equipment queue A supplier’s support team wants equipment cases handled by agents with the relevant asset/category assignment. The queue administrator selects the appropriate team, chooses the availability rule that fits staffing and enables asset-based eligibility only after confirming the relationships.Testing includes a known supported asset, a missing asset and an asset with no eligible specialist. The team agrees who reviews exceptions rather than assuming the service will always find someone. Cases already being investigated also receive explicit review because open queue cases can be considered again. This protects continuity while using automation for the work it can actually classify. Troubleshoot assignment results SymptomCheck and correctionNo agent receives the caseReview queue active state, service processing, selected candidates, agent active/routing status, capacity and each hours gate.An Away agent receives workAway can pass the availability gate. Review the actual mode and your staffing convention.An out-of-hours agent receives workAvailability mode does not itself check agent hours. Review the mode and independent queue-hours option.Asset routing leaves work behindCheck the case asset and assigned asset/category overlap. There is no guaranteed fallback for missing or unmatched assets.Work is not evenly distributedCase-load ordering is not a total-effort balancing promise. Compare eligibility, the counting window and existing workload.An existing owner changesThe processor includes already-owned open queue cases. Review whether that queue is appropriate for work that should retain a stable owner. Continue learning Configure queues and assignment settingsCreate a supervisor view for open workMaintain assets and customer relationshipsUnderstand Division scopePreserve ownership through escalation handoffs Was this article helpful? Yes No Thank you for your feedback.