Skip to content
Help Center
Submit a request Sign in

Configure escalation and de-escalation types

Escalation types provide reusable context when an agent escalates or de-escalates a case. Scope and template controls help teams record consistent impact, mitigation, and handover information.

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

Before you begin

  • You need permission to edit this configuration. Ask an administrator if the page is available but its editing controls are not.
  • Review the current configuration and where it is used before making a change. Available choices depend on your account, enabled modules, division access and role.
  • Use a test record or a controlled test account for behavior checks. Do not change production routing or send customer messages just to try an example.

Configure and verify

  1. Open Settings → Cases → Escalation types.
  2. Find the item in the list and open it, or choose the page’s new-item action.
  3. Enter a clear name and description. Set the fields below, including any scope, hierarchy, visibility or availability controls.
  4. Save the item and resolve any validation message. Reopen it to confirm the saved values.
  5. Check the relevant selection list or form using a user with the intended access. Repeat for an excluded user or division when scope is restricted.

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.
ActiveControls 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.
IssuesRestricts where the escalation choice is available. An empty selection allows all issues.Use issue-specific types only where the process differs.
TypeEscalation or De-Escalation.Choose the action the template documents.
TemplateFormatted content inserted when an agent uses this option.Ask for the impact, scope, current findings, and next action.
AI templateWhere enabled, AI uses accessible case/customer/custom-field context to prepare a draft.Review the generated draft before using it. Do not assume it has verified every fact.

Behavior to know

  • This is an agent action template. Automated escalation conditions are configured in Workflows.
  • AI template controls appear only when supported by the account.

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 an Escalation type for incidents requiring specialist support.
  2. Restrict it to the relevant division and issue classes.
  3. Write a template asking for impact, affected users, checks completed, and mitigation.
  4. Save and use it on a test case to inspect the draft and available choices.
  5. Create a separate De-Escalation type if the team needs a consistent resolution handback.

Troubleshooting

ProblemWhat to check
The item is missing from a picker.Check Active, division access, parent hierarchy, enabled modules, and the user’s role. Reopen the consuming form after saving.
The form rejects a save.Read the displayed validation message. Check required values, text limits and permitted scope; do not change unrelated settings to bypass validation.
An existing record still shows an old value.A configuration change and a record change are different operations. Inspect the record and relevant references before assuming the save failed.
  • Configuration → Configure workflows and automation
  • Cases → Configure case issues
  • Cases → Configure case templates and chat shortcuts

Return an escalation to the previous agent

Open the authorized case in Case View and choose Escalate. The available actions also depend on the agent’s escalation permission and the case’s current escalation history. Administrative access to Escalation types is separate from permission to perform this case action.

Escalate uses the existing escalation workflow. When an eligible previous escalation owner is available, Escalate back to [name] returns the case directly to that agent. With no type selected, it offers the most recent eligible previous escalation and reuses its type. Selecting a type limits the recipient to that type’s history. This action restores escalation state, assigns the named person and records the internal activity and audit without evaluating or running Escalated-specific workflows. General case-update, ownership, watcher and template workflow handling continue, with the named owner protected from competing routing. The existing Details and attachments are retained when the historical type is selected for this return.

Both the ordinary action and the named return remain available when the named agent already owns the case. Choose the named action to keep that agent as owner while the applicable general update and template handling runs. A first escalation without a recorded eligible previous owner offers only the ordinary Escalate action.

Supportbench remembers the owner immediately before de-escalation, separately for each escalation type. It does not use general Last Owner transfer history. Earlier de-escalations without this recorded owner do not offer the return action.

De-escalate to [name] is the primary action and returns the case to the agent who initiated the current escalation. De-escalate keeps the current owner before any configured de-escalation workflows run. Both retain the supplied handoff notes. If the named recipient has changed or become unavailable, the draft is kept and the dialog must be reopened to refresh the choice.

Was this article helpful?