Pull API error rates, feature activation, and integration health into your customer health score, with a plain language explanation of what changed.
Your customer success platform's health score is built almost entirely from CRM activity and survey data, because nobody has the bandwidth to wire in the product telemetry that actually predicts technical churn.
A quiet account can look healthy on paper while its API error rate climbs or an integration silently breaks, and nobody notices until the renewal conversation goes badly.
API error rates, feature activation, integration health from your product analytics
Interpret and act
Northwind Logistics' API error rate climbed 6x above its 90-day baseline this week while CRM activity stayed flat, pulling its technical adoption score down even though the CRM-based health score still reads green. Your team needs to decide what the drop actually means for this account.
Try it — same review surface your operators use, with a representative decision. Nothing here is saved or sent anywhere.
Deciding what a signal really means for a specific account, a drop in API calls could be churn risk or could just mean the customer moved to a leaner integration, and deciding what to do about it, stays with your team.
See this workflow against your own queue.
.png)