How to Set Up Sub-Account Health Scores
How to design and set up a customer health score for GoHighLevel sub-accounts, from picking signals to acting on the result.
Updated September 14, 2026
A health score is only useful if it’s built from signals that actually predict churn and refreshed automatically — a static score calculated once a quarter from a gut-feel spreadsheet isn’t really a health score, it’s a guess with a number attached. Here’s how to set one up properly for GoHighLevel sub-accounts.
What signals should feed a sub-account health score?
A useful health score for a GHL sub-account combines three behavioral signals: login activity (is anyone showing up), product adoption (are they using workflows and automations), and revenue trend (is usage-based spend growing or shrinking) — each capturing a different angle on engagement that the others miss.
Login activity alone misses the account that logs in but never touches anything of value. Adoption alone misses the account that’s stopped spending on SMS and calls, which is often the earliest sign that leads have dried up. Combining all three catches patterns that any single signal would miss on its own.
How should each signal be weighted?
There’s no universal weighting that fits every agency, but login activity is usually the fastest-moving and earliest signal, adoption is the most precise indicator of actual value delivery, and revenue trend is the most directly tied to renewal risk — a reasonable starting split is roughly even across all three, adjusted once you see which signal most reliably precedes your own cancellations.
Review your last 10-20 cancellations and check which signal moved first in each case. If login inactivity consistently led the pattern, weight it more heavily; if accounts kept logging in but adoption quietly dropped, weight adoption more. Let your own churn history calibrate the model instead of guessing.
What score range and thresholds should I use?
A 0-100 scale is the simplest to communicate internally — anything below roughly 40 is typically “at risk” and deserves outreach, 40-70 is “watch,” and above 70 is “healthy,” though the exact cutoffs should shift based on where your own churned accounts historically scored before they left.
Don’t treat the thresholds as fixed on day one. Pull the scores your churned accounts would have had 60 days before they cancelled, and set your “at risk” threshold near wherever most of them clustered — that calibration is what makes the score predictive rather than arbitrary.
How often should the score update?
The score should update automatically as new activity comes in — daily or near-real-time — rather than being manually recalculated weekly or monthly, since a manually-refreshed score is stale by definition and misses the exact window where early intervention still works.
A health score that’s a week old by the time someone reviews it has already lost most of its lead-time advantage over just waiting for a cancellation email. Automatic, continuous scoring is what makes the difference between reactive and proactive retention.
What should happen when a score drops?
A dropping score should trigger a specific, automatic action, not just a number someone might notice during a manual review — at minimum, an alert to the account manager naming which underlying signal is driving the drop, so outreach can be specific instead of generic.
Tie score bands to defined actions: below the at-risk threshold triggers an alert and a required check-in within a set number of days; entering the watch band triggers a lighter automated touch. Without a defined action attached to each tier, the score becomes something people glance at rather than something the team actually works from.
Building this without a dedicated tool
A spreadsheet-based health score is workable for a handful of sub-accounts but breaks down past 20-30, since login activity, adoption, and revenue trend all live in different places and none of them update themselves. GoCSM’s Health AI scores every sub-account continuously from real behavioral data, available starting on the Basic plan at $197/month.
For the underlying signals in more depth, see GoHighLevel agency churn benchmarks and how to calculate agency MRR churn. Once scoring is running, quarterly business reviews are a natural place to walk clients through their own trend.