Skip to content
Help Center
Submit a request Sign in

Configure case priorities

Case priorities describe urgency so agents can triage consistently and workflows can apply the appropriate response targets. A clear definition for each priority improves routing, reporting, and expectations.

Applies to: Supportbench Core. Location: Settings → Cases → Priorities. Access and available controls depend on your role and account capabilities.

Before you begin

  • You need permission to administer Case priorities and access to the intended Division scope.
  • Agree observable urgency/impact criteria before adding a label. Creating a Priority alone does not create SLA or routing rules.
  • Review the saved result and a controlled example in the consuming workflow. Configuration, customer access and actual delivery or processing are separate checks.

Configure and verify

  1. Open Settings → Cases → Priorities and choose New Priority or open an existing choice.
  2. Enter Name and Description, review Display order, Active priority, Divisions and Display color. There is no parent-priority hierarchy on this form.
  3. Where AI description is offered, describe recognizable circumstances rather than a desired score or unverified promise.
  4. Choose Save Changes and reopen the Priority. Verify its saved scope and availability.
  5. Use a controlled Case with an intended agent to inspect the picker. Separately test any workflow that uses this Priority for routing or service targets.

Settings reference

Details and availability

SettingWhat it controlsHow to choose
NameThe label people select. Required; up to 50 characters.Use a short, distinct label that describes its purpose.
DescriptionAdministrative explanation; up to 250 characters.Explain when to choose this option, including an example if useful.
Display orderAn integer from 0 to 25; lower numbers appear first and ties sort by name.Put commonly used choices first without changing their operational meaning.
Active priorityControls availability in standard selection lists. Inactive items remain saved.Deactivate obsolete options when you need to retain their configuration and existing references.
DivisionsRestricts the option to selected divisions. Global scope is available only when your access allows it.Choose the intended divisions. Do not assume an empty selection is permitted for every administrator.
Display colorThe visual indicator used when displaying the option.Use a consistent palette and meaningful labels; color alone should not carry meaning.
AI descriptionWhen available, up to 1,000 characters explaining how AI should recognize this priority.Describe observable impact and urgency. Availability depends on the account’s AI capabilities.

Behavior to know

  • New priorities start active with display order 0. Division selection may be prefilled from the administrator’s accessible division; review it before saving.
  • Color is a presentation setting. Priority-based SLA or routing behavior belongs to the consuming workflows.

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 priority called Critical for an agreed production-impact condition.
  2. Describe that condition and distinguish it from routine questions.
  3. Set the relevant division scope, a prominent display order, and an identifiable color.
  4. Save and check that an agent in the intended division can select it.
  5. Separately review workflows that use priority to determine SLA targets; creating the priority does not create those rules.

Troubleshooting

ProblemWhat to check
Priority is missingCheck Active priority, permitted Divisions and the current Case/agent context.
The new Priority created no SLA targetConfigure and test the consuming workflow/service rules separately. A label alone does not establish a commitment.
AI chooses the wrong PriorityCheck the applicable AI configuration and precise descriptions, then compare representative cases.
A save is rejectedReview text limits, order and allowed Division selection in the field reference.
  • Configuration → Configure workflows and automation
  • Cases → Configure case forms and chat customer details with policies
  • Account → Configure AI policies and case assistance

Was this article helpful?