Catch accounts sliding into churn risk immediately
Every few minutes, WebRun checks ChurnZero for accounts whose health score has newly dropped into the at-risk range, posts the account name and score change to the customer-success Slack channel, and pings the assigned CSM directly on Telegram so they can step in.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch ChurnZero accounts sliding into churn risk immediately?
WebRun checks ChurnZero every 30 minutes for accounts whose health score has newly dropped into the at-risk range, posts the account to Slack, and pings the assigned CSM directly on Telegram. This gets a human looking at a slipping account within the same day it drops, instead of at the next scheduled account review.
- At-risk accounts get a human looking at them the same day the score drops
- CSMs get pinged directly instead of checking a dashboard for changes
- Score drops are caught within 30 minutes instead of at the next review
Built for customer success teams · SaaS account management · customer success managers · retention teams
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.churnzero.netin a real browser with your saved login - no setup, no API keys. -
1
ChurnZero - find accounts newly at risk
churnzero.net
WebRun opens ChurnZero to find accounts newly at risk. - Open ChurnZero and check health scores against the last recorded run
- Capture every account that newly dropped into the at-risk range
- Note the score change and the assigned CSM for each
Done when Every account newly at risk is listed with its score change and CSM.
-
2
Slack - post the at-risk account
slack.com How to Automate Slack
WebRun opens Slack to post the at-risk account. - Post each newly at-risk account to the customer-success Slack channel
- Include the score change and what drove it if available
- Tag the assigned CSM in the post
Done when The customer-success channel has an alert for every newly at-risk account.
-
3
Telegram - ping the assigned CSM
telegram.org How to Automate Telegram
WebRun opens Telegram to ping the assigned CSM. - Message the assigned CSM directly for each newly at-risk account
- Include the account name and score change
- WebRun never contacts the customer, only the CSM
Done when The assigned CSM has been pinged for every newly at-risk account.
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
Does WebRun reach out to the account directly?
No. WebRun never contacts a customer. It only alerts your Slack channel and the assigned CSM so a person decides how to respond.
How is an account marked at risk?
WebRun reads each account's health score directly from ChurnZero and flags anything that newly crossed into the at-risk range since the last check.
Will the same account trigger repeated alerts?
No. It only alerts on accounts newly entering the at-risk range, so an account that's been at risk for days won't re-alert every run.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.