Detect At-Risk Accounts Before Churn
Every morning, WebRun cross-references HubSpot account health scores with recent Zendesk ticket data to find accounts with declining engagement, rising complaint volume, or near-expiry contracts, then posts a ranked at-risk list to your #customer-success Slack channel for your CSM team to act on.
How can I automatically detect customer accounts at risk of churning?
Every morning, WebRun cross-references HubSpot account health scores with recent Zendesk ticket data to find accounts with declining engagement, rising complaint volume, or near-expiry contracts, and posts a ranked at-risk list to your Slack #customer-success channel - so your CSM team can step in before a customer leaves.
- At-risk accounts surfaced daily before churn signals become cancellations
- CSMs get a ranked list - highest-risk accounts first
- Declining engagement and rising complaint trends caught early
Built for customer success managers · SaaS companies · account managers · subscription businesses
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.hubspot.comin a real browser with your saved login - no setup, no API keys. -
1
HubSpot - read account health and contract data
hubspot.com
WebRun opens HubSpot to read account health and contract data. - Open the Companies view and filter for accounts with a Health Score below your churn-risk threshold
- Note accounts whose contract renewal is within 90 days
- Flag accounts with no CSM touchpoint logged in the past 30 days
Done when All at-risk accounts are identified by health score, renewal proximity, and CSM inactivity.
-
2
Zendesk - check recent ticket volume and sentiment
zendesk.com
WebRun opens Zendesk to check recent ticket volume and sentiment. - Search for tickets from at-risk accounts in the last 30 days
- Count open unresolved tickets and note any with Urgent priority or escalation tags
- Flag accounts with more than 3 open tickets as 'High support load'
Done when Each at-risk account has a support-load score added to its risk profile.
-
3
Slack - post the ranked at-risk list
slack.com
WebRun opens Slack to post the ranked at-risk list. - Post the at-risk list to #customer-success ranked by combined risk score (health + support load + renewal proximity)
- Include: account name, ARR, key risk factor, assigned CSM, and renewal date
- Mention the assigned CSM for accounts with the highest risk scores
Done when The CSM team has a ranked, actionable at-risk account list in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it contact at-risk customers automatically?
No - it only surfaces the risk list. All outreach is initiated by the CSM based on the alert.
How do I set my churn-risk threshold?
Tell WebRun the Health Score cutoff (e.g. below 40) and the renewal window (e.g. 90 days) in the plan - it will apply those numbers on every run.
What if a healthy account suddenly sends a lot of angry tickets?
The Zendesk support-load check catches exactly that scenario - high ticket volume or escalated tickets add to the risk score even if the HubSpot health score is still green.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.