Automated ChartMogul Churn Spike Alerts
Every morning, WebRun opens ChartMogul, checks yesterday's churned MRR and failed payments against your trailing 30-day average, posts a Telegram digest naming the largest accounts lost, and texts you through Twilio when churn spikes significantly.
How do I get alerted when my churned MRR spikes in ChartMogul?
WebRun checks ChartMogul every morning for yesterday's churned MRR and failed payments, comparing the total against your trailing 30-day average. It posts a Telegram digest naming the largest accounts lost, and texts you through Twilio when churned MRR is more than double normal, so a real spike gets your attention fast.
- Real churn spikes trigger a same-morning text, not a monthly surprise
- The largest accounts lost are named automatically
- Ordinary day-to-day churn stays quiet, so texts stay meaningful
Built for SaaS founders · finance teams · revenue operations · customer success leaders
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.chartmogul.comin a real browser with your saved login - no setup, no API keys. -
1
ChartMogul - check churn and failed-payment metrics
- Open ChartMogul and pull yesterday's churned MRR and failed-payment count
- Compare it against your trailing 30-day average
- Note the customers behind the largest churned amounts
Done when Yesterday's churn and failed-payment metrics have been checked against baseline.
-
2
Telegram - post the digest
telegram.org
WebRun posts to Telegram to share the digest. - Post a digest of churned MRR and failed payments to the founders group
- List the largest churned accounts by name
Done when The team has this morning's churn digest in Telegram.
-
3
Twilio - text on a big spike
twilio.com
WebRun uses Twilio to text on a big spike. - Send a text if churned MRR is more than double the trailing average
- Name the total churned and the biggest account lost
Done when A text has gone out for every day churn spikes significantly.
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 try to win back a churned customer on its own?
No. WebRun only reports the churn and the accounts behind it. Reaching out to win a customer back is left to your team.
How big does a spike have to be for a text?
Churned MRR has to be more than double your trailing 30-day average before it triggers a Twilio text, so ordinary day-to-day churn stays in the regular digest.
Does it include failed payments or just cancellations?
Both. It reads churned MRR from cancellations alongside failed-payment counts, since a failed charge often becomes involuntary churn if it isn't recovered.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.