FIGR / UI TEMPLATE

Customer Asset History

Inspect an installed customer asset with service history, warranty, parts replaced, telemetry, recurring faults, and upcoming maintenance.

This detail reference covers field service & customer operations. Its sample screen includes Compressor replaced and Pressure sensor calibrated and the Create service job action. Adapt its workflow to your product and design system.

Customer Asset History

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Detail

Primary action

Create service job

Pattern

Customer asset history

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

The customer asset history screen supports “Create service job” while keeping overview and service history in view. It should show the current state even when data is missing or access is restricted.

What to look for

  • Primary action: Create service job
  • Main area: Overview brings the user to the relevant workflow
  • Related area: Service history keeps nearby context accessible
  • Asset age: 4.2y in the sample screen
  • Visits: 11 in the sample screen
  • Example 1: Compressor replaced
  • Example 2: Pressure sensor calibrated

States to consider

  • Default: Show the main workflow and its available next step
  • Loading: Preserve the page structure and explain what is still loading
  • Empty: Say why there are no records and offer a clear first action
  • Error: Explain what failed, keep entered work, and allow retry
  • Access: Show which actions require a role or permission
  • Success: Confirm the result after Create service job and say what happens next

Where it fits

Overview → Service history → Create service job → Review result

Patterns in this screen

Customer asset history, Overview, Service history, permission handling, error recovery

UX choices to review

Keep the primary record and next action visible while people explore details

In this example, Compressor replaced is one of the records worth checking. Keep the sample data clearly separate from a live system.

Place ownership, progress, and related information beside the current task

Show the history and permission context that explain a change

Try a similar screen in Figr

Design a customer asset history screen for an existing field service & customer operations product. Use our actual design system, components, and content rules. Cover Overview and Service history, include believable records such as Compressor replaced, and make "Create service job" easy to find. Map empty, loading, error, permission, and success states. Keep the result editable in Figma.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗