Catch Batch opt-out spikes before they spread
Every hour, WebRun opens Batch, checks the opt-out and unsubscribe rate for recent push, in-app, and email sends, posts an alert to Telegram the moment a campaign crosses its normal range, and texts the on-call growth lead through Twilio when the spike is severe enough to need immediate attention.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch a Batch campaign opt-out spike early?
WebRun checks Batch every hour for push, in-app, and email campaigns whose opt-out rate is trending above normal, posts a Telegram alert naming the campaign, and texts the on-call growth lead through Twilio when the spike is severe. This catches a bad send early instead of finding out from a falling subscriber count days later.
- Opt-out spikes get flagged within the hour they start
- Only severe spikes wake the on-call phone
- The team catches a bad send before it drains the subscriber base
Built for mobile app growth teams · lifecycle marketers · product marketing · app engagement 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
batch.comin a real browser with your saved login - no setup, no API keys. -
1
Batch - check opt-out rates
WebRun opens Batch to check opt-out rates. - Open Batch and review recent push, in-app, and email campaigns
- Read the opt-out and unsubscribe rate for each
- Compare each rate against its normal range
Done when Every recent campaign has its opt-out rate checked against its normal range.
-
2
Telegram - post the alert
WebRun opens Telegram to post the alert. - Post an alert to the growth team's Telegram channel for any campaign outside its normal range
- Name the campaign and the opt-out rate
- Post nothing when every campaign is within range
Done when The team has a Telegram alert for any campaign trending high.
-
3
Twilio - text the on-call lead
WebRun opens Twilio to text the on-call lead. - Send a text to the on-call growth lead only when a spike is severe
- Include the campaign name and the opt-out rate in the text
- Never message app users directly, only the internal on-call number
Done when The on-call lead is texted only for a severe spike.
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 it message the app's own users?
No. WebRun only alerts your internal team on Telegram and texts the on-call lead through Twilio. It never contacts your app's end users.
What counts as a severe spike?
A jump well outside the campaign's normal opt-out range. Smaller wobbles only get the Telegram alert, so the on-call phone is not woken for noise.
How quickly would I know about a bad send?
Batch is checked every hour, so a spike is flagged within the same hour it starts trending, not the next morning.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.