Automated Customer.io Deliverability Alerts
Every morning, WebRun opens Customer.io, reads yesterday's deliveries, bounces, spam complaints, and unsubscribes for every campaign and broadcast, compares each rate against your normal level, pings Telegram when a message is out of line, and posts the per-message breakdown to Slack.
How do I catch email bounces and spam complaints before deliverability drops?
Every morning, WebRun opens Customer.io, reads yesterday's deliveries, bounces, spam complaints, and unsubscribes for each campaign, and compares every rate against your normal level. It pings Telegram when a message is out of line and posts the per-message breakdown to Slack, so a bad send is caught on day one.
- The message hurting your domain is named on day one
- Alerts fire against each message's own baseline, not a blanket number
- The daily breakdown sits in Slack for the whole team to see
Built for lifecycle marketers · email marketing teams · growth teams · CRM managers
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
fly.customer.ioin a real browser with your saved login - no setup, no API keys. -
1
Customer.io - read yesterday's delivery health
customer.io
WebRun opens Customer.io to read yesterday's delivery health. - Open Customer.io and review yesterday's deliveries across campaigns, broadcasts, and transactional messages
- Capture sends, bounces, spam complaints, and unsubscribes per message
- Note how many addresses were added to the suppression list and by which message
Done when Yesterday's delivery figures are captured for every message that sent.
-
2
Telegram - ping when a rate spikes
telegram.org
WebRun opens Telegram to ping when a rate spikes. - Compare each message's bounce and complaint rate against its own recent average
- Ping the channel only when a message sits above the threshold you set
- Name the message, the rate, and how far it is above normal
Done when Any message with an out-of-line bounce or complaint rate has been flagged in Telegram.
-
3
Slack - post the per-message breakdown
slack.com
WebRun opens Slack to post the per-message breakdown. - Post the full breakdown to your lifecycle channel, worst rate first
- Show sends, bounce rate, complaint rate, and unsubscribes per message
- Leave pausing or editing a campaign to a person. WebRun does not stop a send itself
Done when The per-message deliverability breakdown is 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 pause a campaign on its own?
No. WebRun reads delivery figures and alerts your team. Pausing a campaign, editing a message, and cleaning a segment stay with a person, so a working send is never stopped by an automation.
How does it know a rate is too high?
It compares each message against its own recent average rather than a single blanket number, and only alerts when the gap passes the threshold you set. A message that always runs slightly high does not cry wolf daily.
Does it send anything to subscribers?
No. WebRun only reads reporting data. The output goes to your own Telegram and Slack channels, and no subscriber is ever contacted.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.