Skip to content
Help Center
Submit a request Sign in

Configure queues and automatic assignment

Queues organize incoming work and can distribute cases and chats to eligible agents. Scope, schedules, membership and round-robin rules work together, so configure the whole route rather than treating the queue name as sufficient.

Applies to: Supportbench Core. Location: Settings → Organization → Queues. Editing requires Administer queues.

Before you begin

  • Decide who should see and handle the queue’s work, its actual service hours, and whether Case and Chat routing should differ.
  • Review existing child queues and membership before changing a parent. Parent changes can reset direct children to root; inspect the resulting hierarchy.

Configure and verify

  1. Open Settings → Organization → Queues and choose New Queue or the existing queue. Enter Name and Description and review Active, Parent queue and Display order.
  2. Choose Global queue or the appropriate Team. Enabling Global clears Team; confirm the intended audience after changing it.
  3. Configure Timezone, Working days and Working hours. Enable off-day hours only when those hours genuinely provide service.
  4. Review Assigned Agents separately from Round-robin agents and teams. Membership alone does not make an agent an automatic-assignment participant.
  5. If using automatic Case distribution, enable round robin and choose the appropriate Availability rule, queue-hours behavior and other assignment controls. Read each option in the reference below.
  6. Review Chat queue and the separate Chat routing policy. A widget also has its own selected queue and outside-hours behavior.
  7. Choose Save Changes, reopen and verify the settings. Run controlled routing checks during coverage, outside coverage and with an unavailable participant. Confirm Case and Chat results separately.

Settings reference

Queue profile and visibility

SettingWhat it controlsHow to choose
NameThe name shown in selectors and lists.Choose a distinct operational name.
DescriptionExplains the intended purpose and audience.Describe ownership and when to use it.
ActiveControls whether the item is available for normal use.Review existing references before deactivation.
Parent queuePlaces a queue in a hierarchy. Changing the parent resets direct children to root.Review the whole branch before moving it.
Display orderControls list order.Keep commonly used queues easy to find.
Global queue / TeamMakes the queue global or restricts it to a selected team. Enabling Global clears the team selection.Choose an explicit audience; Team or Global is required.
Chat queueMakes the queue available for chat use.Check the associated widget and agent coverage before using it.

Schedule

SettingWhat it controlsHow to choose
TimezoneThe timezone used with the queue’s working days and hours for business-hour SLA calculations.Use the schedule’s local timezone and review daylight-saving transitions.
Working daysDays included in the normal working schedule.Match actual service coverage.
Working hoursThe ordinary business-hour window used for the queue’s SLA calculations.Use agreed service hours rather than an individual’s temporary availability.
Enable off-day hours / Off-day hoursAllows a separate hours window for days outside the ordinary working-day selection.Enable only when those days really have coverage.
Core queue Availability showing Los Angeles time zone, Monday to Friday selected, and working hours from 9 AM to 5 PM.
Review the queue’s local time zone, working days and service window together. This demo uses Los Angeles time and Monday–Friday, 9 AM–5 PM; these are example settings, not universal defaults. Assignment eligibility and off-day hours require their separate checks.

Auto-Assignment

SettingWhat it controlsHow to choose
Enable round robinEnables automatic distribution through the configured round-robin rules.Confirm eligible agents and membership before enabling.
Availability ruleAvailability, Just working hours, or Availability and working hours.Choose whether real-time presence, schedule, or both should gate assignment.
Use queue hoursUses the queue’s working schedule in assignment decisions.Keep queue hours aligned with the chosen availability rule.
Use asset ownerUses asset ownership where supported by the assignment logic.Review cases with and without a relevant asset owner.
Use case loadUses case load in assignment decisions.Verify the distribution with realistic test workloads.
Round-robin agents and teamsDefines participants in automatic assignment.Use active eligible participants; do not assume all assigned agents participate automatically.
Assigned AgentsAdds or removes queue membership.Keep membership and round-robin participants deliberately aligned.

Chat routing policy

SettingWhat it controlsHow to choose
Route chats using chat workload onlyUses chat workload for routing, counting concurrent chats across queues and applying the agent’s maximum simultaneous chat limit. Availability rules still apply.Enable when case workload should not determine chat assignment.
Reassign unanswered chats afterReassignment interval for unanswered chats; Off disables automatic reassignment.Allow a realistic pickup period and test a controlled unanswered chat.

Behavior to know

  • Changing hierarchy, membership, or assignment settings can affect newly routed work.
  • A widget uses its selected queue and its own fallback rules; the queue alone does not define the full outside-hours experience.
  • Cases can be assigned to a queue manually or by a workflow. Automatic round-robin distribution runs only for queues with round robin enabled and eligible participants under the configured availability rules.

Recommended use

  • Use terminology that agents and customers already understand. Explain the intended meaning in the description.
  • Keep the initial configuration small enough for people to choose consistently. Add options when they represent a real operational difference.
  • Review existing references before renaming, changing scope, or deleting. Where supported, deactivate an obsolete option before considering permanent deletion.

Worked example

  1. Create a Technical Support queue and choose its team or global scope.
  2. Set the actual service hours and timezone.
  3. Add the intended agents and choose round-robin participants.
  4. Choose Availability and working hours if both conditions should apply.
  5. Save and test routing during coverage, outside coverage, and with an unavailable agent.

Troubleshooting

ProblemWhat to check
A member never receives round-robin CasesCheck Enable round robin, explicit participants, availability rule, hours and the agent’s status. Queue membership alone is insufficient.
The queue appears to the wrong groupReview Global queue versus Team and the current user’s access. Global clears the Team choice.
Chat behavior differs from CasesInspect Chat queue, Chat policy, widget queue/fallback, agent presence and Chat eligibility independently of Case round robin.
Children moved after changing a parentInspect the hierarchy and restore intended direct-child placement through the normal controls.
After-hours assignment is unexpectedCompare queue timezone, working/off-day hours and the configured availability rule.
I cannot change the queueCheck Administer queues.
  • Organization → Configure teams and SLA availability
  • Organization → Configure agent statuses
  • Email configuration → Configure inbound email routes
  • Self-Service → Configure a chat widget

Was this article helpful?