Customer health
Never a number without a reason.
Every state names its evidence: which cases, which feedback, which promise, which date. An account owner should be able to read it in ten seconds and know what to do.
Named records, openable
Case 1842, case 1861, the negative feedback from the 14th, the renewal date. Each one clicks through.
Ordered by what is fixable
An unresolved complaint you can act on today comes above a renewal date you cannot change. The list is ordered for action.
Disagreement is recorded
An account owner who knows the context can override the state with a reason. That override is itself a signal, and repeated overrides mean the model is wrong.
Customer health
The rest of this area.
Three explainable states, each with the evidence that produced it.
The three states
Healthy, needs attention, at risk — and nothing in between.
The signals
What actually feeds the state, and what deliberately does not.
Renewal risk
Service history set against the renewal date.
Alerts
Being told when a relationship turns, not when a ticket arrives.
Across the customer base
Patterns in health, not just individual accounts.
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]