NPS Feedback

Read score movement alongside verbatim feedback, account segments, follow-up status, and recurring themes. The screen connects Overview and Responses so support agents can find the “New survey” action while checking nps and responses.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Ease of use · 68% positive and Reporting gaps · 24% negative, rather than an empty visual shell.

NPS Feedback
Use this template in Figr

Template facts

Screen

Analytics

Primary action

New survey

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 “New survey” action without losing sight of nps, responses and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: New survey is clearly available where the task happens.
  • Main view: Overview keeps the starting point obvious.
  • Connected view: Responses supplies nearby context.
  • Metric: NPS is visible with a meaningful value.
  • Another signal: Responses helps people judge what to do next.
  • Representative record: Ease of use · 68% positive makes the example specific.
  • Second record: Reporting gaps · 24% negative 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 responses; clarify who can continue.
  • Success after choosing New survey; 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 → Responses → New survey → Review outcome

Patterns used

Analytics, Overview, Responses, Themes, 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 Ease of use · 68% positive with Reporting gaps · 24% negative. Make nps clear, then use responses 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 “New survey” action. The happy path alone is not enough.

Related UI examples: Customer Health, Knowledge Base, Help Center Admin.

Start from this in Figr

Design a nps feedback screen for our existing software product. Use our real design-system tokens, components and product language. Show Overview and Responses, include believable records such as Ease of use · 68% positive, and make new survey easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr