Health Scoring
Part of Customer health scoring
Explaining a health score to an account owner
Explain what changed in a customer health score, where the evidence is limited and what the account owner should verify next.
Explain a health score as a dated summary of particular observations and the question they raise for the account. Show what moved, what data is missing and what the owner can verify next. A colour or total on its own gives too little information for a sound customer conversation.
Prepare the account view
Before speaking with the owner, confirm which customer entity the score covers and when each component was updated. Check whether the owner is looking at a company, division or contract relationship.
Inspect the underlying measures and any manual assessment; a changed total may reflect a changed component, a revised weight or unavailable data.
Bring a compact explanation:
- Current view:the total or category, its date and the account unit it covers.
- Main drivers:the components that most affect the result or have changed since the previous comparable view.
- Evidence and limits:the period, population, source and any missing or stale input.
- Question:what account fact would confirm or challenge the interpretation?
- Next step:who will check it and when the finding will be reviewed.
If the scoring definition changed between snapshots, say so before describing a trend. Movement caused by a revised weight is different from a change in the customer’s behaviour.
Top Drivers of Health Score Change
- Relationship AssessmentNeutral (outdated)
- Support Ticket VolumeLow (no recent tickets)
Translate the score into an account question
Suppose a hypothetical approvals customer has a lower health category this month. Eligible managers completed fewer recorded approvals, while the relationship assessment has not been refreshed. Explain that recorded workflow completion fell in the stated period and the relationship view is old.
Ask the owner to check whether eligible requests arose and whether the process owner says the route is still working. It would be premature to say the customer plans to leave.
Use plain language when a component is subjective. State who assessed the relationship, what they observed and what remains their judgement.
If a customer contact reported a problem, distinguish that report from the team’s view of its commercial impact. Invite the account owner to correct the record with a source and date.
Handle disagreement openly
The owner may know that the customer deliberately paused the workflow or that an integration stopped sending events. Ask for the evidence and update the affected component or expected-use rule through the agreed process.
Do not quietly edit the total to match intuition. Equally, favourable usage should not dismiss a documented concern from the person who owns the customer outcome.
When an account is new or a component is unavailable, describe the score as a partial view. In some scorecards, an NA component changes the weights applied to the remaining components; Gainsight NXT documents this behaviour.
State the effect if it applies to the system in use. Do not compare totals as though they came from identical evidence when they did not.
Interpreting the Score: Key Considerations
- Pros
- Score reflects actual usage patterns; highlights stale data and potential risk areas
- Cons
- Outdated relationship assessment may skew interpretation; new accounts lack full data coverage
Agree what the owner will do
End with a decision. The owner might verify an event feed, ask the customer a specific question, bring in a service owner or monitor the next task cycle. Record the observation, the check needed, the responsible person and the review date.
If the customer confirms a serious problem, the appropriate risk or service workflow should own the response.
Next Steps for Account Owner
- Verify event feed from workflow systemConfirm data is flowing correctly
- Contact process owner at client siteCheck if approvals are paused intentionally
- Update relationship assessmentSchedule review by end of next week
- Review in 7 daysReassess score with updated inputs
