Support Analytics

Understand volume, resolution, CSAT, queue mix, and the support topics creating repeat work. The screen connects Overview and Queues so support agents can find the “Create report” action while checking tickets and resolution.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Billing · 24% and Access · 18%, rather than an empty visual shell.

Support Analytics
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Create report

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 “Create report” action without losing sight of tickets, resolution and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Create report is clearly available where the task happens.
  • Main view: Overview keeps the starting point obvious.
  • Connected view: Queues supplies nearby context.
  • Metric: Tickets is visible with a meaningful value.
  • Another signal: Resolution helps people judge what to do next.
  • Representative record: Billing · 24% makes the example specific.
  • Second record: Access · 18% 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 overview 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 Create report; 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

Overview → Queues → Create report → Review outcome

Patterns used

Analytics, Overview, Queues, Topics, 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 Billing · 24% with Access · 18%. Make tickets clear, then use resolution 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 “Create report” action. The happy path alone is not enough.

Related UI examples: Escalation Center, Knowledge Base, NPS Feedback.

Start from this in Figr

Design a support analytics screen for our existing software product. Use our real design-system tokens, components and product language. Show Overview and Queues, include believable records such as Billing · 24%, and make create report easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr