Understanding Health Scores
Learn how Klyra calculates customer health scores using support signals, engagement data, and AI analysis to help you spot at-risk accounts early.
Overview#
Health scores give you a single number (0-100) that represents how well a customer relationship is going. Instead of guessing which accounts need attention, health scores surface at-risk customers before they churn.
Klyra's health scores combine support signals (ticket volume, sentiment, response times) with engagement data (product usage, login frequency) and AI analysis (pattern detection, trend prediction) into an actionable score.
How scores are calculated#
Each customer account gets a health score based on weighted factors:
Support signals (40% weight)#
| Signal | Healthy | At-risk |
|---|---|---|
| Ticket volume trend | Stable or decreasing | Spike in last 30 days |
| Average sentiment | Positive/neutral | Negative trend |
| Resolution time | Within SLA | Frequently breached |
| Escalation rate | Low | High |
| Repeat issues | Rare | Same problem recurring |
Engagement signals (30% weight)#
| Signal | Healthy | At-risk |
|---|---|---|
| Login frequency | Regular | Declining |
| Feature adoption | Growing | Stagnant |
| Last active | Recent | 14+ days ago |
| Team members active | Multiple | Single/none |
Relationship signals (30% weight)#
| Signal | Healthy | At-risk |
|---|---|---|
| Communication frequency | Regular check-ins | Going silent |
| CSAT scores | Positive | Declining |
| Contract renewal proximity | Distant/renewed | Approaching with issues |
| Executive engagement | Active | Disengaged |
AI adjustment#
After calculating the formula-based score, Klyra's AI reviews the account's recent activity and applies an adjustment of up to +/- 10 points. The AI explains its reasoning — for example:
"Score adjusted -5: Customer opened 3 urgent tickets this week about the same billing issue. Pattern suggests systemic frustration, not isolated incidents."
Score ranges#
| Range | Status | Color | What it means |
|---|---|---|---|
| 80-100 | Healthy | Green | Customer is engaged and satisfied |
| 60-79 | Neutral | Yellow | No immediate risk, but worth monitoring |
| 40-59 | At Risk | Orange | Multiple warning signs — take action |
| 0-39 | Critical | Red | High churn probability — intervene now |
Setting up health scores#
Step 1: Enable health scoring#
- Go to Settings > Customer Intelligence > Health Scores
- Toggle health scoring on
- Klyra begins calculating scores for all accounts with enough data
Step 2: Configure weights (optional)#
The default weights work well for most teams, but you can customize them:
- Go to Settings > Customer Intelligence > Health Score Config
- Adjust the weight percentages for support, engagement, and relationship signals
- Changes take effect on the next score calculation cycle (every 6 hours)
Step 3: Set up alerts#
Get notified when accounts need attention:
- Go to Settings > Notifications
- Enable health score alerts for:
- Score drops below a threshold (e.g., 60)
- Score changes by more than 15 points in a week
- Account moves from "Healthy" to "At Risk" status
Using health scores day-to-day#
Dashboard overview#
The Dashboard shows a health overview card with:
- Distribution of accounts by health status
- Accounts that changed status recently
- Trending scores (improving vs. declining)
Account detail page#
Click on any customer in Customers to see:
- Current health score with trend chart
- Score breakdown by factor
- AI reasoning for the latest calculation
- Health score history over time
- Recommended actions
Anomaly detection#
Klyra automatically detects anomalies — unusual changes in account behavior:
- Sudden spike in ticket volume
- Sharp sentiment drop
- Unusual activity patterns (e.g., a power user goes silent)
Anomalies appear in your Dashboard > Anomaly Alerts card and trigger notifications if configured.
Churn prediction#
Building on health scores, Klyra's churn prediction model analyzes:
- Health score trajectory (direction matters more than absolute value)
- Historical patterns from other accounts that churned
- Contract timeline and renewal history
- Engagement velocity (rate of change in activity)
The result is a churn risk percentage and an actionable save plan — specific steps your team can take to retain the customer.
Best practices#
- Don't just look at the number — read the AI reasoning and factor breakdown to understand why the score is what it is
- Set up weekly health reviews — use the Daily Digest to review accounts that need attention
- Act on "At Risk" early — accounts at 40-59 are easier to save than those below 40
- Track improvement — after taking action, monitor if the health score responds. If not, the intervention didn't address the root cause
- Use it in handoffs — when reassigning an account, the health score gives the new owner instant context
Next steps#
- Configure the AI agent — AI-resolved tickets contribute positively to health scores
- Set up Slack — Slack activity feeds into engagement signals
- Getting started guide — return to the overview if you need to set up other features