Escalation Center

Coordinate high-risk customer issues with ownership, severity, incident links, executive visibility, and response timing. The screen connects Escalations and Incidents so support agents can find the “Escalate” action while checking open and critical.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Northstar · data export blocked and Kinetic · SSO outage, rather than an empty visual shell.

Escalation Center
Use this template in Figr

Template facts

Screen

Inbox

Primary action

Escalate

Pattern

Inbox

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Support agents need a clear “Escalate” action without losing sight of open, critical and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Escalate is clearly available where the task happens.
  • Main view: Escalations keeps the starting point obvious.
  • Connected view: Incidents supplies nearby context.
  • Metric: Open is visible with a meaningful value.
  • Another signal: Critical helps people judge what to do next.
  • Representative record: Northstar · data export blocked makes the example specific.
  • Second record: Kinetic · SSO outage shows the pattern works beyond one item.

States worth designing

  • Inbox empty after filters; show what people can do instead of leaving a blank panel.
  • Loading escalations without changing the layout unexpectedly.
  • Attachment or reply failed; explain the problem and preserve work.
  • Permission denied for incidents; clarify who can continue.
  • Success after choosing Escalate; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Escalations → Incidents → Escalate → Review outcome

Patterns used

Inbox, Escalations, Incidents, Accounts, accessible states, contextual actions

Why these choices work

Keep the active record close to its history, owner and status. Make urgent items easy to find without hiding the rest.

In this design, people should be able to compare Northstar · data export blocked with Kinetic · SSO outage. Make open clear, then use critical to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Escalate” action. The happy path alone is not enough.

Related UI examples: Knowledge Base, Support Analytics, NPS Feedback.

Start from this in Figr

Design a escalation center screen for our existing software product. Use our real design-system tokens, components and product language. Show Escalations and Incidents, include believable records such as Northstar · data export blocked, and make escalate easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr