Customer Health Score: What It Is and How it is Calculated

A customer health score helps customer success teams assess account health using signals such as product adoption, satisfaction, support activity, and renewal readiness. It brings those signals together so teams can see where customers are doing well and where they may need help.

A score is only as useful as the data behind it. If the model rewards frequent logins but ignores poor customer feedback, it can label an unhappy account as healthy. This blog explores how to choose the right customer health score metrics, build a reliable scoring model, and use the results to guide customer success actions.

Key Takeaways

• A customer health score shows whether customers are adopting your product, getting value, and likely to renew.
• Customer health score calculation combines metrics such as product usage, satisfaction, support issues, and renewal engagement.
• A customer health score combines weighted metrics into a single score out of 100.
• Use a customer health score template to apply scoring rules consistently and track follow-up actions.
• Customer health score software can connect customer data, scoring, alerts, and workflows.
• Customer health scoring helps teams spot risks and prioritize accounts, while a customer success health score should support, not replace direct conversations with customers.

What Does a Customer Health Score Tell You?

A customer health score summarizes how well a customer is adopting a product, receiving value, and maintaining a healthy relationship with the business. Companies usually combine several indicators into one score, then review the individual metrics to understand what drives the result.

For example, a customer may log in every day but use only one basic feature. Another may log in less often but rely on the product for a critical business process. The second customer could be healthier despite having fewer sessions.

This is why customer health scoring needs to reflect actual customer outcomes, not just activity. SurveyVista’s Salesforce customer success guide explains how customer success teams can use account data, health indicators, and automated workflows to manage relationships.

Which Customer Health Score Metrics Belong in Your Model?

The right customer health score metrics depend on your product, customer lifecycle, and business model. Choose signals that help explain adoption, satisfaction, and renewal risk.

Product adoption and usage

Look at how many people use the product, which features they use, and whether that usage has changed. If a customer stops using a feature they relied on every week, find out what happened. They may have switched to another tool, run into a problem, or no longer need that feature.

Satisfaction and relationship feedback

Usage data won’t tell you the whole story. Customers may keep using a product because their team depends on it, even when they’re unhappy with the experience. Use CSAT, NPS, or CES to hear what they think. SurveyVista’s guide to measuring satisfaction at customer touchpoints covers these measures and what they reveal.

Support and service quality

Track unresolved tickets, repeat complaints, and resolution times. If customers keep complaining about the same issue, then you need to check if the team has fixed it. Unresolved issues are a stronger sign of an unhealthy account.

Renewal and account engagement

Make sure you monitor renewal dates, account review attendance, and changes in spending. In case a customer stops attending meetings or responding to your team as renewal approaches, contact them to understand the issue. Record the reason before changing their customer health score.

How to Calculate Customer Health Score Using a Weighted Formula

A weighted model is a practical way to calculate a customer health score because it lets you give greater importance to the metrics that matter most to your business.

Step 1: Score each metric from 0 to 100

Score each metric against what you see in the account. A customer who uses the main features regularly should score well on usage. If serious support issues are still unresolved, lower the support score. For overdue cases, give lower scores to accounts with more outstanding issues.

Step 2: Assign a weight to each metric

For a subscription software business, you might assign 30% to product adoption, 20% to product usage, 20% to customer satisfaction and loyalty, 15% to support health, and 15% to renewal engagement. The weights must total 100%. Use your own customer data to decide whether these proportions make sense for your business.

Step 3: Apply the customer health score formula

Use this customer health score formula:

Customer Health Score = (Adoption × 0.30) + (Usage × 0.20) + (Satisfaction × 0.20) + (Support × 0.15) + (Renewal Engagement × 0.15)

For example, a customer scores 75 in adoption, 85 in usage, 60 in satisfaction, 70 in support health, and 50 in renewal engagement. After applying the weights, the scores add up to 69.5 out of 100.

Step 4: Decide what each score means

Start with 80–100 for healthy accounts, 50–79 for accounts that need attention, and below 50 for at-risk accounts. Test these cutoffs against your renewal and churn records to see if they flag the right customers. Check the scores for each metric before deciding how to follow up.

SurveyVista’s customer assessment tools page discusses how customer assessments can combine feedback, analysis, and workflows to support follow-up.

How to Build a Customer Health Score Template

A customer health score template should record each account’s metrics, weighted score, current health status, and next action. Customer health scoring helps teams decide where they need to investigate first. 

Include these fields:

• Account name and customer segment
• Product usage and adoption scores
• Customer satisfaction or NPS score
• Support issue score
• Renewal engagement score
• Weight assigned to each metric
• Overall customer health score
• Health category
• Change since the last review
• Person responsible for follow-up, next action, and due date

Define how to score each metric in the template. For example, specify what counts as regular product usage and how unresolved support cases affect the score. This keeps different account managers from scoring the same situation differently.

Update the template when you change the scoring formula or add new metrics. Review whether the scores match actual renewals and churn, then adjust the model if they don’t.

SurveyVista’s Feedback Foundations Guide covers onboarding, support satisfaction, and relationship surveys that can provide useful inputs for customer health assessments.

What to Look for in Customer Health Score Software

Customer health score software should let your team combine customer data, calculate scores, and flag accounts that need attention. You may want to check whether the tool supports these features:

• Data connections: Can it pull the customer data your scoring model needs?
• Flexible scoring: Can you set your own metrics, weights, and score thresholds?
• Automated updates: Do scores change when customer or account data changes?
• Alerts and routing: Can it notify the right person when an account’s score drops?
• Reporting: Can you track score changes and compare customer segments?
• Action tracking: Can your team record follow-ups and track their outcomes?

If your team works in Salesforce, check how the scoring model fits your existing account records and workflows. SurveyVista is a Salesforce-native feedback platform that can map survey responses to Salesforce fields and support automated follow-up. Your organization can use Salesforce data and configuration to build a health scoring model around those inputs.

For example, SurveyVista’s NPS survey template can help gather loyalty feedback, while its CSAT and NPS response mapping guide explains how survey scores can be mapped to Salesforce record fields.

Customer Success Health Score: Turning Signals Into Follow-Up

A customer success health score should help the team decide what to do next. A score without an owner or action plan only describes a situation; it does not improve it.

Match the response to the problem:

• Low adoption: Offer targeted training or review the customer’s implementation.
• Declining satisfaction: Contact the customer and investigate the reason.
• Repeated support problems: Assign an owner to review the unresolved or recurring issues.
• Renewal concerns: Arrange an account review and agree on next steps.
• A sudden score drop: Check the underlying data before deciding whether to escalate.

It is important to monitor the outcome of each intervention. If training improves adoption or resolving a support issue raises satisfaction, record the change and use it to refine your model.

Connect Health Scores to Customer Feedback

A health score helps teams identify accounts that need attention. Customer feedback helps explain why. SurveyVista lets Salesforce teams collect feedback, map responses to customer records, and automate follow-up based on what customers report. Book a demo with SurveyVista to see how its solution can connect customer feedback with Salesforce workflows.

FAQs 

Should revenue be part of a customer health score?

Yes. Revenue shows the financial impact of losing an account, but it doesn’t tell you whether the customer is satisfied or getting value from your product. Combine revenue with usage, satisfaction, and renewal data.

What should you do when customer usage is high but satisfaction is low?

Find out what’s frustrating the customer. Review their feedback and support history, then ask what needs to improve. High usage doesn’t mean they’re happy with the product.

How do you stop a customer health score from fluctuating every week?

You must use consistent measurement periods and avoid overreacting to one-off events. If the score drops sharply, check which metrics changed before flagging the account as at risk.

Can you compare customer health scores across different segments?

Yes, if you account for differences in how each segment uses your product. Set separate benchmarks where needed, so you don’t judge a small account by the same usage expectations as a large enterprise customer.