SLA Monitor

Surface tickets approaching breach, show response-time trends, and make ownership gaps visible before customers feel them. The screen connects SLA and Queues so support agents can find the “Review risks” action while checking at risk and breached.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Enterprise P1 · 82% and Enterprise P2 · 94%, rather than an empty visual shell.

SLA Monitor
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Review risks

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Support agents need a clear “Review risks” action without losing sight of at risk, breached and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Review risks is clearly available where the task happens.
  • Main view: SLA keeps the starting point obvious.
  • Connected view: Queues supplies nearby context.
  • Metric: At risk is visible with a meaningful value.
  • Another signal: Breached helps people judge what to do next.
  • Representative record: Enterprise P1 · 82% makes the example specific.
  • Second record: Enterprise P2 · 94% shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading sla without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for queues; clarify who can continue.
  • Success after choosing Review risks; 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

SLA → Queues → Review risks → Review outcome

Patterns used

Analytics, SLA, Queues, Policies, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare Enterprise P1 · 82% with Enterprise P2 · 94%. Make at risk clear, then use breached 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 “Review risks” action. The happy path alone is not enough.

Related UI examples: Ticket Detail, Help Center Admin, Support Inbox.

Start from this in Figr

Design a sla monitor screen for our existing software product. Use our real design-system tokens, components and product language. Show SLA and Queues, include believable records such as Enterprise P1 · 82%, and make review risks easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr