A customer health score is a single number, often on a 0 to 100 scale or a red, yellow, green band, that summarizes the overall state of an account. It rolls many underlying signals into one figure a team can scan, sort, and act on, so a CSM with a large book of business knows where to spend attention without reading every system by hand.
What goes into a health score
- Product usage: adoption, engagement, and stickiness trends, especially among power users.
- Sentiment: the tone of support tickets, emails, and meeting notes, read through sentiment analysis.
- Relationship: whether the champion is active and how many stakeholders are engaged.
- Commercial: billing health, support load, and proximity to renewal.
- Survey inputs: NPS and CSAT responses where available.
The point is to be predictive, not descriptive
A good health score leads churn rather than lagging it. The score should fall while there is still time to intervene, turning a future cancellation into a present at-risk account that a playbook can address. A score that only confirms what already happened is a dashboard decoration, not a tool.
The hard part is that the inputs live in a dozen different systems and change constantly. Merrily computes a live health score per account by reading Slack, email, meeting notes, product events, billing, and contracts directly, so the number reflects everything that has actually happened across the relationship, refreshed as it happens rather than re-keyed once a quarter.