Hand off SendGrid bounce spikes to the right person
Every hour, WebRun checks SendGrid's bounce and spam-complaint rate for recent sends, and when a send crosses your set threshold, it packages the affected recipient count and details, posts them to Telegram, and sends a Twilio SMS page to the on-call deliverability engineer so the investigation starts immediately.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get alerted when SendGrid bounce rates spike?
WebRun checks SendGrid's bounce and spam-complaint rates every hour, and when a send crosses the threshold you set, it posts the incident details to Telegram and sends a Twilio SMS page to your on-call deliverability engineer, so a sending problem gets a named owner and starts getting fixed within the hour it happens.
- Bounce spikes get an owner within the hour instead of at the next report
- No deliverability incident sits unnoticed overnight
- The on-call engineer gets the exact numbers needed to start investigating
Built for engineering teams · deliverability specialists · email infrastructure 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.sendgrid.comin a real browser with your saved login - no setup, no API keys. -
1
SendGrid - check bounce and complaint rates
WebRun opens SendGrid to check bounce and complaint rates. - Open SendGrid and review bounce and spam-complaint rates for the last hour's sends
- Compare each send's rate against your set threshold
- Capture the affected recipient count for anything over threshold
Done when Every send over threshold this hour has been identified.
-
2
Telegram - post the incident details
WebRun opens Telegram to post the incident details. - Post the incident to the deliverability channel in Telegram
- Include the send name, rate, and affected recipient count
- Link back to the SendGrid activity feed for detail
Done when The incident details are posted to Telegram.
-
3
Twilio - page the on-call engineer
WebRun opens Twilio to page the on-call engineer. - Send an SMS page to the on-call deliverability engineer
- Include the send name and the rate that triggered the page
- Leave the fix, whether pausing IPs or reviewing content, to the engineer
Done when The on-call engineer has been paged for every incident this hour.
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 pause my SendGrid sending automatically?
No. WebRun only detects and pages the incident. Pausing IPs, pools, or campaigns is a decision the on-call engineer makes.
Who gets paged?
Whichever internal on-call deliverability engineer you configure. It's an internal SMS page, never a message to an actual recipient.
What threshold triggers a page?
Whatever bounce or spam-complaint rate you set. WebRun checks every hour and only pages when a send crosses it.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.