Customer health
Know who needs attention before they leave.
Healthy, needs attention, at risk — and every state shows exactly why. No mysterious score out of a hundred, because a number nobody can explain is a number nobody acts on.
States, not scores
"At risk: an unresolved complaint, negative feedback, and a renewal in 28 days." That produces action. "Health score: 64" produces a shrug.
Built from things that happened
Cases, repeat contact, unresolved complaints, negative feedback, broken promises, renewal proximity. Every input is a record somebody can check.
It is about the relationship, not the person
Health describes how the account is going, never how the customer behaves. The product will not characterise a customer, and the acceptable use policy makes that a rule.
In this area
6 pages under Customer health.
Each one is its own surface in the product, and each one is here because it does something the others do not.
The three states
Healthy, needs attention, at risk — and nothing in between.
ReadWhy this state
The specific reasons, always shown.
ReadThe signals
What actually feeds the state, and what deliberately does not.
ReadRenewal risk
Service history set against the renewal date.
ReadAlerts
Being told when a relationship turns, not when a ticket arrives.
ReadAcross the customer base
Patterns in health, not just individual accounts.
ReadThe rest of Resolivo
This is one part of one loop.
Take better care of every customer.
Give your team the context, knowledge and AI they need to resolve problems properly — and know who needs attention before they ask.
Keep the mailbox you already use · The AI is never metered · [email protected]