Skip to content

Sample report

A customer health score, with the evidence behind it.

Follow Northwind Labs from setup friction to confident use. Start with the customer overview, then read the sessions and context behind its recommended action.

Fictional customer data.

Northwind Labs

Health 7.6 / 10 · Low churn risk · Power user

Northwind recovered from repeated authentication setup errors, completed its first multi-step workflow, then adopted batch operations and export.

Recommended action

Clarify the authentication setup instructions. Session 01 included five retries before the customer found the right setting and completed the connection.

Explore sessions and conversations

Reading the report

What changed across the sessions?

These session summaries show both the initial friction and the later recovery. They explain why a healthy customer can still reveal something worth fixing.

  1. Session 01 · Setup

    Authentication errors, then recovery

    The customer tried the same setup step five times before finding the right setting and completing the connection. The repeated retries point to an opportunity to clarify the instructions.

    Goal achieved · Integration connected

  2. Session 02 · Exploration

    A use case beyond the product’s scope

    The customer tested an adjacent use case and was unsure what output to expect. Some confusion remained at the end of the session.

    Goal partially achieved · Scope questions remain

  3. Session 03 · First workflow

    The first multi-step workflow succeeds

    The customer completed a workflow without getting stuck. Requests were more precise than in the first session, and the customer expressed delight with the result.

    Goal achieved · Confidence growing

  4. Session 04 · Expansion

    Moving into batch operations and export

    The customer tried both features, worked through a question independently, and discovered saved views.

    Goal achieved · Broader feature use

Why the recommendation matters

Northwind recovered, but the repeated setup errors still deserve attention. The report recommends clarifying that step for the next customer. Your team can review the session and decide what to change.

Usage context

Put the customer’s experience alongside their activity.

The customer page pairs analysis with operational metrics from synced usage data. These example totals describe usage, including automated calls; they do not count human messages alone.

Total requests
1,284
Total tokens
9.4M
Total spend
$47.10

In the application, Vitals also compares customer metrics with the workspace’s 10th percentile, median, and 90th percentile. Use that context to understand the scale of an account alongside its experience.

Behavior and adoption

Look for progress beyond the score.

The behavioral profile and feature-adoption analysis describe how a customer’s use develops. For Northwind, the sessions show increasing confidence and a broader range of workflows.

Engagement depth
Deep. Returns to multi-step work and builds on earlier sessions.
Sophistication trend
Increasing. Requests become more specific as the customer gains experience.
Expansion pattern
Broadening. Moves from integration setup to batch operations and export.

Analysis scope

Read the findings in context.

This example follows four sessions. In your workspace, check the report’s analysis window and date to understand which history it covers. The usage chart’s date range is separate from the report’s analysis window.

The health score and churn-risk tier help prioritize investigation. They are based on structured analysis signals; a risk tier is not a measured probability that a customer will leave.

How health and risk are calculated

What could your customer conversations tell you?

Explore how the analysis works, or request an invitation to use LiteLedger with your own logs.

Request access How it works