Customer Health

Combine product usage, support signals, renewal timing, and relationship context into an actionable customer-health view. The screen connects Accounts and Health so support agents can find the “Create plan” action while checking healthy and at risk.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Northstar Labs · Healthy and Kinetic Cloud · Watch, rather than an empty visual shell.

Use this template in Figr

Template facts

Screen

Workspace

Primary action

Create plan

Pattern

Workspace

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 plan” action without losing sight of healthy, at risk and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

Primary action: Create plan is clearly available where the task happens.
Main view: Accounts keeps the starting point obvious.
Connected view: Health supplies nearby context.
Metric: Healthy is visible with a meaningful value.
Another signal: At risk helps people judge what to do next.
Representative record: Northstar Labs · Healthy makes the example specific.
Second record: Kinetic Cloud · Watch shows the pattern works beyond one item.

States worth designing

First-use workspace; show what people can do instead of leaving a blank panel.
Loading accounts without changing the layout unexpectedly.
Unavailable or restricted panel; explain the problem and preserve work.
Permission denied for health; clarify who can continue.
Success after choosing Create plan; 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

Accounts → Health → Create plan → Review outcome

Patterns used

Workspace, Accounts, Health, Renewals, accessible states, contextual actions

Why these choices work

Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.

In this design, people should be able to compare Northstar Labs · Healthy with Kinetic Cloud · Watch. Make healthy clear, then use at risk 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 plan” action. The happy path alone is not enough.

Related UI examples: Help Center Admin, NPS Feedback, SLA Monitor.

Start from this in Figr

Design a customer health screen for our existing software product. Use our real design-system tokens, components and product language. Show Accounts and Health, include believable records such as Northstar Labs · Healthy, and make create plan easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr