Compute a Customer Health Score and Alert on Churn Risk
Save accounts before they leave — combine usage, support and billing signals into a health score and alert CSMs when an account turns risky.
- 1
Schedule the Scoring
Add a
Schedule Triggerrunning daily across your active accounts. - 2
Gather Signals
Add
HTTP Requestnodes pulling usage trends, support ticket volume and payment health per account. - 3
Compute the Score
Add a
Codenode combining the signals into a 0-100 health score with weightings you control. - 4
Alert on Decline
Add an
IFnode flagging accounts that dropped below a threshold or fell sharply, then aSlackalert to the CSM. - 5
Activate and Test
Activate the workflow and feed a test account declining signals. Confirm the risk alert fires.
Frequently asked questions
What signals matter most?
Declining core-feature usage and rising support friction are usually the strongest churn predictors — weight them highly.
Can I automate a playbook?
Trigger a save playbook (check-in email, CSM task) automatically when an account crosses into the risk zone.