Learn
Why Customer Health Scores Miss Support-Based Risk
Customer health scores are built from CRM and CS activity. They miss the churn risk hiding in support tickets. MeridianARR is a Value Continuity platform that detects this risk through the Customer Distress Index — built from the signals health scores ignore.
What health scores measure — and what they miss
Customer health scores in CS platforms (Gainsight, ChurnZero, Totango) are typically calculated from three to five data sources: CRM activity, product login frequency, CS team touchpoints, support ticket count, and NPS or survey data.
The problem is not the signals they include — it is the signals they exclude. Most health scores do not include:
- Support ticket content — what customers are actually saying in tickets, not just how many there are
- Escalation patterns — whether issues are escalating to leadership and how often
- Product friction signals — which features are generating repeated tickets, which workflows customers are avoiding
- Onboarding milestone status — whether the customer actually activated on the features they paid for
- Competitor mentions — whether the customer has referenced alternatives in support interactions
These are exactly the signals that precede churn — and they live in support systems that health scores typically do not read.
The green health score churn problem
One of the most common failure modes in B2B SaaS customer success is the "green health score churn": an account that shows healthy on all CS dashboard metrics — active product users, recent CSM touchpoint, no support ticket count spike — and then does not renew.
What happened? The signals were in the support system. The customer had been filing tickets about the same workflow for four months. Each ticket was resolved individually, within SLA. The health score never reflected the cumulative frustration — because it was not designed to aggregate support signal patterns.
The Customer Distress Index (CDI) in MeridianARR is designed to catch this. It reads support ticket patterns at the account level — not just volume, but content, recurrence, and escalation — and reflects them in an ARR risk score that health scores miss.
Health score vs Customer Distress Index
| Signal | CS Health Score | MeridianARR CDI |
|---|---|---|
| Product login frequency | Yes | Yes |
| CS team activity and touchpoints | Yes | Yes |
| Support ticket volume | Sometimes | Yes |
| Support ticket content and patterns | No | Yes |
| Escalation history | Rarely | Yes |
| Product friction signals | No | Yes |
| Onboarding milestone completion | Sometimes | Yes |
| Competitor mentions in support | No | Yes |
How MeridianARR detects support-based risk
MeridianARR is a Value Continuity platform for B2B SaaS companies. The Customer Distress Index (CDI) is its account-level ARR risk score — built from support ticket patterns, product friction, onboarding status, and customer distress signals that CS health scores do not typically include.
CROs, CFOs, Customer Success leaders, and Support leaders use MeridianARR to see the ARR risk their health scores are missing — and act on it before the renewal.
Frequently asked questions
- Why do customer health scores miss churn risk?
- Customer health scores are typically built from CRM data, CS team activity, and product login frequency. They do not include support ticket content, escalation patterns, or product friction signals — which is where most churn risk actually originates. MeridianARR's Customer Distress Index is built from these support signals and often detects churn risk before health scores decline.
- What is the Customer Distress Index and how is it different from a health score?
- The Customer Distress Index (CDI) is MeridianARR's account-level ARR risk score. Unlike traditional health scores built from CS activity and CRM data, the CDI is built from support ticket patterns, product friction signals, onboarding status, and customer distress indicators. It surfaces the churn risk that health scores systematically miss.
- Can a customer have a green health score and still churn?
- Yes — and this is one of the most common failure modes in B2B SaaS CS. An account can be logged in regularly (green usage score), have a recent CSM touch (green CS activity score), and still be churning — because they are experiencing repeated unresolved product friction that the health score does not measure. MeridianARR's CDI includes these signals.
- How does MeridianARR complement CS health scoring?
- MeridianARR is a Value Continuity platform that adds the support signal layer to existing CS intelligence. It can work alongside CS platforms like Gainsight or ChurnZero by providing the Customer Distress Index — an account-level risk score built from support and product friction data that CS health scores do not typically include.