
Customer Health Score shows whether a customer relationship is healthy, at risk, or ready for growth. It is a composite metric that combines multiple signals, such as satisfaction, loyalty, activity, product or service usage, customer service history, complaints, payments, qualitative feedback, sentiment, and churn risk.
Customer Health Score is not a single satisfaction metric. It is a relationship health model based on multiple customer signals. NPS, CSAT, and CES can be part of the model, but they do not replace a complete view of customer health.
A good Customer Health Score should combine what customers say with what customers do. Declared satisfaction is not enough if the customer stops using the product, stops responding to account outreach, or reduces the scope of cooperation. Behavioral data alone is also not enough if the company lacks the context behind the customer experience.
The greatest value of Customer Health Score is that it helps detect churn risk before the customer officially leaves. This allows the company to act proactively: trigger account outreach, offer additional support, improve a process, or identify an opportunity to expand the relationship.
Customer Health Score is a composite metric that evaluates the health of a customer relationship based on data about satisfaction, activity, engagement, contact history, payments, and churn risk.
In practice, CHS helps answer a simple but important question: which customers are in good health, which require attention, and which may soon reduce their engagement or churn?
This is especially important for companies managing a large customer portfolio. Without a structured model, it is difficult to quickly assess where real risk appears and where there is potential for further growth.
Customer Health Score helps answer the question: is a given customer relationship healthy, at risk, or ready for expansion?
CHS is most often used to:
In a well-designed CX and Customer Success program, Customer Health Score should not be just a colored status in the CRM. It should help teams make decisions: whom to contact, where to launch a recovery plan, who needs additional support, and where there is potential to expand the relationship.
Customer Health Score is a customer relationship health model that combines multiple data points related to customer experience, behavior, engagement, value, and churn risk.
In its simplest form, CHS can be represented as a status:
In a more advanced version, Customer Health Score can be a numerical score, for example from 0 to 100. This score can be updated automatically based on data from various sources: CRM, customer service platforms, Voice of Customer tools, product analytics, billing systems, CX surveys, and account manager notes.
The most important point is that Customer Health Score should not be treated as a “nice-to-have report.” Its role is to support business decisions. A good CHS helps teams understand where the customer relationship is stable, where it needs support, and where risk or growth potential is emerging.
In many organizations, customer knowledge is fragmented. Sales teams know the purchase history. Customer Success understands the relationship context. Customer service sees tickets, complaints, and escalations. Marketing tracks communication engagement. Product teams monitor user activity. CX teams collect NPS, CSAT, CES, and customer comments.
Each of these perspectives is valuable, but none of them shows the full picture of the customer relationship on its own.
A customer may have a high NPS but use the product less and less. They may pay invoices on time but submit more and more support tickets. They may use the product heavily but express negative sentiment in open comments. They may also have a low CSAT after one interaction while still remaining a stable and loyal customer.
Customer Health Score helps combine these signals into one interpretive model. As a result, the company can see more quickly whether the customer relationship is healthy, deteriorating, in need of intervention, or ready for further growth.
A well-designed CHS supports several areas:
One of the most important applications of Customer Health Score is early churn risk detection. Customers rarely leave without prior warning signs. Before they churn, there are often indicators that the relationship is weakening.
These may include:
Customer Health Score helps identify these signals earlier and combine them into one view. This means the team does not have to wait until the customer formally cancels, stops buying, or reduces the scope of cooperation.
Example: a SaaS customer actively used the product during the first few months, invited additional users, and participated in onboarding. Later, the number of logins drops, contact with the Customer Success Manager weakens, and support tickets start to show recurring configuration issues. NPS may not yet indicate a crisis, but Customer Health Score should already show a decline in relationship health.
Churn risk rarely comes from a single event. More often, it is the result of several overlapping signals that together show that the relationship is weakening.
The most important warning signals include:
This is why Customer Health Score should combine different types of data. A single signal may be accidental. Several signals appearing at the same time may indicate real risk.
There is no single mandatory data set that should always be included in Customer Health Score. The choice of components depends on what truly indicates a healthy customer relationship in a given business.
However, it is useful to think about CHS as a combination of several types of signals.
This includes survey and feedback data such as NPS, CSAT, CES, post-interaction ratings, open-ended comments, and feedback collected after key customer journey stages.
These data points show how the customer evaluates the experience. They are important, but they should not be the only source used to assess relationship health.
This includes information about customer activity: logins, purchase frequency, feature usage, app activity, number of users, visits, limit usage, or time since last activity.
Behavioral data often reveals risk earlier than survey responses. The customer may not yet say they are dissatisfied, but their behavior may already show declining engagement.
This includes support tickets, complaints, escalations, response time, resolution status, number of contacts about the same issue, delivery delays, process errors, or recurring problems.
Operational data helps identify whether the customer is experiencing real friction.
This includes customer value, payments, overdue invoices, purchase history, renewals, declining basket value, reduced contract scope, budget usage, or expansion potential.
Financial data is especially important in B2B, SaaS, subscription-based services, and renewal-driven business models.
This includes the number of meetings, contact with the account manager, decision-maker involvement, participation in QBRs, responses to communication, and the strength of relationships with users and business sponsors.
In B2B, lack of access to a decision-maker may be as important a risk signal as a decline in NPS.
| Data category | Example metrics | What do they show? | Possible interpretation |
|---|---|---|---|
| Satisfaction and loyalty | NPS, CSAT, CES | How the customer evaluates the experience, relationship, or ease of getting things done | A decline in scores may indicate weakening relationship health |
| Customer activity | logins, visits, usage frequency, time since last activity | Whether the customer is actively using the product or service | Declining activity may signal churn risk |
| Product adoption | usage of key features, number of active users, limit usage | Whether the customer is receiving the value they are paying for | Low adoption may indicate weak value realization |
| Customer service | number of tickets, resolution time, recurring issues, escalations | How often the customer experiences problems and how the company resolves them | An increase in tickets may indicate frustration |
| Complaints | number of complaints, complaint types, status, recurrence | Whether the customer experiences problems with the product, service, or process | Recurring complaints reduce relationship health |
| Purchase history | purchase frequency, basket value, last purchase, product categories | How customer purchasing behavior changes over time | Declining purchases may indicate weakening engagement |
| Financial data | payments, overdue invoices, customer value, renewals | Business stability and commercial potential | Payment delays may signal risk |
| Communication engagement | email opens, clicks, meeting attendance, responses to outreach | Whether the customer remains engaged in dialogue | Lack of response may indicate distance or declining interest |
| Qualitative feedback | comments, open-ended responses, recurring topics | Why the customer evaluates the relationship in a certain way | Comments help explain the reasons behind the score |
| Sentiment | positive, neutral, or negative tone in comments | Emotional tone of the relationship | Negative sentiment may precede declining numeric scores |
| Account relationship | contact with account manager, QBRs, meetings, decision-maker involvement | Strength of the business relationship | Lack of decision-maker engagement may increase risk |
| Growth potential | feature usage, inquiries, interest in add-ons, user expansion | Upsell or cross-sell opportunities | High CHS may indicate expansion potential |
Customer Health Score should not be confused with individual CX metrics. NPS, CSAT, and CES are valuable, but they measure selected aspects of the customer experience.
NPS shows likelihood to recommend.
CSAT measures satisfaction with a product, service, or specific experience.
CES measures how easy it was for the customer to get something done.
Customer Health Score combines multiple signals to evaluate the overall health of the customer relationship.
| Metric | What does it measure? | Role in CHS |
|---|---|---|
| NPS | Likelihood to recommend | May indicate loyalty and overall customer attitude |
| CSAT | Satisfaction with a product, service, or interaction | May indicate the quality of specific experiences |
| CES | Ease of getting something done | May reveal friction in processes |
| Customer Health Score | Overall customer relationship health | Combines multiple signals into one relationship health model |
The key difference is simple: NPS, CSAT, and CES can be components of Customer Health Score, but they do not replace the full model.
A customer may have a high NPS because they like the brand, but at the same time they may be using the product less and less. They may have a good CSAT after the latest support interaction but have overdue payments. They may rate one process as difficult while still maintaining a stable business relationship with the company.
This is why a good Customer Health Score should combine declarative data with behavioral, operational, financial, and qualitative data.
NPS is an important metric, but it does not show the full health of the customer relationship. It measures declared likelihood to recommend — whether the customer would be willing to recommend the company, product, or service.
Customer Health Score answers a broader question: is the customer relationship stable, at risk, or ready for growth?
Example: a customer may give a high NPS because they like the brand and have had a positive history with the company. At the same time, they may be using the product less often, not adopting new features, not responding to CSM outreach, and having an overdue invoice. In this case, NPS looks good, but Customer Health Score should indicate risk.
That is why NPS should be treated as one component of the model, not as a full diagnosis of the relationship.
The model below is an example, not a universal formula. Each company should adapt the components and weights to its own business.
| Component | Example weight |
|---|---|
| NPS / CSAT / CES | 20% |
| Customer activity | 20% |
| Product or service adoption | 20% |
| Customer service and complaints | 15% |
| Financial and payment data | 10% |
| Qualitative feedback and sentiment | 10% |
| Account relationship / B2B engagement | 5% |
In this model, the customer can receive a score from 0 to 100.
| CHS score | Customer status | Interpretation |
|---|---|---|
| 0–39 | At-risk customer | High churn risk or serious relationship issues |
| 40–69 | Customer requiring attention | The relationship is unstable or requires deeper analysis |
| 70–100 | Healthy customer | The relationship is stable and may have growth potential |
Weights should not be based only on intuition. Ideally, they should be validated against historical data to check which signals actually preceded churn, non-renewal, declining purchases, complaints, or reduced cooperation.
At the beginning, there is no need to build an advanced predictive model. In many companies, a simple and understandable model based on a few key signals works better.
A first version of the model may include:
At first, such a model can even be managed manually or semi-automatically, for example in a CRM, spreadsheet, or BI dashboard. What matters is defining what low, medium, and high scores mean — and what actions each status should trigger.
Only after testing a simple model is it worth adding more components, automation, weighted scoring, and system integrations.
Customer Health Score should be interpreted in the context of the current score, trend, customer segment, relationship stage, and business context.
A low CHS means that the customer relationship requires immediate attention. It may indicate churn risk, lack of activity, negative feedback, recurring complaints, service issues, overdue payments, or lack of access to decision-makers.
Recommended actions:
A medium score means that the relationship is not yet critical, but it requires monitoring. The customer may be neutral, partially engaged, or unstable.
Recommended actions:
A high CHS means the relationship is in good condition. The customer is active, stable, satisfied, and likely sees value in the cooperation.
Recommended actions:
A decline in Customer Health Score does not always mean a crisis, but it should always trigger analysis. The worst response is to ignore the trend and wait until the customer reports a problem.
The first step is to identify which component caused the decline. A drop in activity requires a different response than an increase in complaints or a negative comment after a support interaction.
Example actions:
Customer Health Score should lead to action. The score itself will not improve the relationship unless it is connected to ownership, a playbook, and a clear response process.
A single Customer Health Score can be misleading. A customer with a CHS of 72 may seem safe, but if they had 88 a month earlier, the decline should draw attention. On the other hand, a customer with a CHS of 55 may be improving if they had 35 a few weeks earlier.
That is why Customer Health Score should be analyzed as a trend. The most important questions are:
A good CHS dashboard should show not only the score, but also the reasons behind it.
Segmenting customers by Customer Health Score helps tailor actions more effectively. Not every customer requires the same response.
These are customers with a low CHS, declining activity, negative feedback, frequent issues, or churn risk.
Recommended actions:
These customers are not yet in crisis, but the relationship is not strong enough.
Recommended actions:
These are customers with high CHS, stable activity, positive feedback, and potential for further growth.
Recommended actions:
In SaaS, Customer Health Score is often based on user activity, adoption of key features, number of active accounts, support tickets, NPS, renewals, and contact with a Customer Success Manager.
Example: a customer has a high NPS but uses the platform less often and has not adopted key features. CHS should show declining relationship health, even though the declarative score still looks good.
In B2B services, satisfaction scores are important, but so are quality of cooperation, regular contact, decision-maker involvement, payment timeliness, business review outcomes, and project feedback.
Example: a customer pays invoices on time but does not attend meetings, stops responding to communication, and reduces the scope of cooperation. Customer Health Score may reveal weakening relationship health earlier than financial data alone.
In e-commerce, CHS can include purchase history, transaction frequency, basket value, returns, complaints, post-purchase NPS, CSAT after customer service contact, and reactions to marketing communication.
Example: a customer bought regularly for a year, but in recent months has not made any purchase, stopped opening emails, and gave a negative rating after delivery. This indicates a weakening relationship.
In financial services, Customer Health Score can combine trust, digital channel activity, number of call center contacts, complaints, payment timeliness, product usage, and feedback after key processes.
Example: a customer has high value potential but reports repeated problems with the mobile app and stops using some products. CHS can help identify a customer who requires quick intervention.
In insurance, moments of truth are especially important: claim submission, contact with the claims handler, compensation decision, and policy renewal.
Example: a customer renews a policy for years, but after a poorly handled claim, their sentiment drops sharply. Customer Health Score should consider not only renewal history, but also the quality of the latest critical experience.
In retail, CHS can combine purchase data, loyalty program participation, visit frequency, returns, complaints, store visit ratings, app activity, and responses to promotions.
Example: a customer still buys, but returns products more often, rates store visits lower, and stops using the app. Purchase history alone may not reveal the issue, but CHS should capture the decline in relationship health.
Before calculating Customer Health Score, the company needs to define what a healthy relationship means. In SaaS, it may mean regular product usage and feature adoption. In B2B, it may mean active contact with the account owner, renewal, and positive feedback. In e-commerce, it may mean regular purchases, low complaint volume, and positive engagement with communication.
Do not start with too many components. It is better to choose a few signals that have real business relevance and are available in good quality.
Not every signal has the same weight. Missing payments, declining activity, or negative feedback after a complaint may be more important than a single unopened newsletter.
A good model should be tested. Check whether customers with low CHS were actually more likely to churn, reduce purchases, submit complaints, or fail to renew.
Customer Health Score should trigger specific actions. A low score may generate an alert for the CSM. Declining activity may trigger an educational campaign. A high score may be a signal for sales to discuss relationship expansion.
A CHS model should not be built once and left unchanged. Customer behavior, products, communication channels, and business goals evolve. The model should be reviewed and calibrated regularly.
Start simple. The first Customer Health Score model does not need to be perfect or fully automated. It should be understandable, useful, and connected to action.
At the beginning, choose 4–6 signals that best describe customer relationship health. These may include:
Then define thresholds: when is the customer healthy, when do they require attention, and when are they at risk? Only later should the company expand the model with more data, automation, weighted scoring, and dashboards.
The most important question for the first model is: what will we do when a customer’s score drops?
What works in SaaS may not work in retail. What works in enterprise B2B may not work in e-commerce. Customer Health Score should be tailored to the specific business.
NPS can be an important component, but it is not enough. Customer Health Score should also include behavior, activity, operational data, contact history, and qualitative feedback.
More data does not always mean a better model. If the components are not connected to business decisions, the score becomes complex but not very useful.
The same CHS threshold may mean something different for an enterprise customer, an SMB customer, a new user, and a long-term customer. Segmentation is essential for proper interpretation.
If no one is responsible for acting when the score drops, Customer Health Score becomes just another dashboard metric.
The current score alone is not enough. A decline from 90 to 70 may be more important than a stable score of 60. The trend often says more than a single value.
A model that is not reviewed quickly loses value. Products, processes, channels, and customer behavior change over time.
If teams can see only the score but do not know what caused it to increase or decrease, it is difficult to translate CHS into action. A good model should show the main drivers behind the score.
Eventually, yes — but not every model needs to be fully automated from the start. Many companies can begin with a semi-automated CHS model that combines data from CRM, CX research, customer service tools, and analytical spreadsheets.
The model should be simple enough for teams to understand and precise enough to support decisions. A score that is too complex and difficult to explain may reduce trust. A score that is too simple may miss important signals.
The best approach is iterative: start with a few components, test their usefulness, and then gradually develop the model.
Customer Health Score helps assess whether a customer relationship is healthy, at risk, or ready for growth. It is not a single satisfaction metric, but a composite model that combines many signals: NPS, CSAT, CES, customer activity, product usage, service interactions, complaints, payments, qualitative feedback, sentiment, and relationship data.
The most important principle is this: there is no universal Customer Health Score formula. A good model should reflect what a healthy customer relationship truly means in a specific business.
The value of CHS appears only when the score leads to action. A low score should trigger a response. A medium score should lead to monitoring and activation. A high score may indicate customers ready for expansion, references, or deeper cooperation.
The best CX and Customer Success programs treat Customer Health Score as a relationship management tool, not just a report. This allows the company to detect risks earlier, make better use of growth opportunities, and build more predictable customer relationships.
Customer Health Score is a composite metric that evaluates the health of a customer relationship based on multiple data points, such as satisfaction, activity, product usage, customer service interactions, complaints, payments, qualitative feedback, and churn risk.
Customer Health Score is calculated by combining selected components into one scoring model. A company can assign weights to categories such as NPS, CSAT, customer activity, product adoption, support tickets, financial data, and comment sentiment.
No. Customer Health Score should be adapted to the industry, business model, customer segment, relationship stage, and available data. A model that works in SaaS may not work in e-commerce or B2B services.
Customer Health Score can include declarative, behavioral, operational, financial, and qualitative data. Examples include NPS, CSAT, CES, customer activity, product usage, support tickets, complaints, payments, purchase history, customer comments, and account owner interactions.
NPS measures the customer’s likelihood to recommend, while Customer Health Score evaluates the overall health of the customer relationship based on multiple signals. NPS can be one component of CHS, but it does not replace the full model.
No. A customer may rate the brand highly while using the product less often, having overdue payments, or not responding to account outreach. That is why NPS should be analyzed together with behavioral, operational, and financial data.
Customer Health Score can help predict churn if it includes signals related to churn risk, such as declining activity, negative feedback, increasing number of issues, lack of contact, payment delays, or low product adoption.
The update frequency depends on the business model. In SaaS, CHS may be updated daily or weekly. In B2B services, monthly updates or updates after key events, such as a meeting, complaint, renewal, or project completion, may be sufficient.
A low Customer Health Score should trigger root cause analysis and a specific action. This may include customer outreach, a conversation with the account owner, a recovery plan, priority handling of support tickets, additional onboarding, or a closed-loop feedback process.
No. Customer Health Score is especially popular in SaaS, but it can also be used in B2B, e-commerce, financial services, insurance, retail, and customer service. The key is to adapt the model components to the specifics of the industry.
Customer Health Score is most often owned by Customer Success, CX, analytics, or account management teams. However, action ownership should also involve leaders from customer service, sales, product, marketing, finance, and operations.
Yes, especially at the beginning. A company can start with a simple model in a spreadsheet or CRM and automate it later. What matters most is that the model is understandable, useful, and connected to specific actions.
The most important warning signals include declining activity, lower product usage, increasing support tickets, recurring complaints, negative feedback, lack of contact with the account owner, payment delays, and lower decision-maker engagement.
No. Customer Health Score should be adapted to customer segments because different signals may matter for enterprise customers, SMB customers, new customers, long-term customers, or high-value accounts.
A decline in Customer Health Score should trigger root cause analysis and a specific action, such as customer outreach, ticket analysis, additional onboarding, a recovery plan, or closed-loop feedback.
Yes. A high Customer Health Score may indicate customers who are ready for upsell, cross-sell, renewal, references, or expansion of the relationship.
Start with a simple model based on a few key data points, such as NPS, customer activity, product usage, support tickets, payments, and comments. The model can later be developed and automated.
Copyright © 2023. YourCX. All rights reserved — Design by Proformat