Escalate an incident nobody has picked up
Every few minutes, WebRun opens Better Stack, checks the incident list for anything still unacknowledged past the grace period you set, works out who is next on your escalation rota, texts that person through Twilio with the monitor name and how long it has been down, and posts the same escalation to your engineering channel in Telegram.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I escalate an incident nobody has acknowledged?
WebRun escalates stale Better Stack incidents every few minutes. It checks the incident list for anything unacknowledged past your grace period, texts the next person on your on-call rota through Twilio with the monitor name and minutes open, and posts the escalation to your Telegram channel.
- No incident sits unacknowledged past your grace period
- The right on-call gets a text with the monitor name and downtime
- Every escalation is visible in Telegram, so nobody is paged in silence
Built for site reliability engineers · DevOps teams · on-call engineers · engineering 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
betterstack.com/users/sign-inin a real browser with your saved login - no setup, no API keys. -
1
Better Stack - find unacknowledged incidents
betterstack.com
WebRun opens Better Stack to find unacknowledged incidents. - Sign in to Better Stack and open the incidents list
- Capture every incident that is still open and not yet acknowledged
- Record the monitor name, the start time and how many minutes it has been open
- Keep only incidents past the grace period you set for their severity
Done when Every unacknowledged incident past the grace period is listed with its age.
-
2
Twilio - text the next on-call
twilio.com How to Automate Twilio
WebRun opens Twilio to text the next on-call. - Open Twilio and look up the next number on your escalation rota
- Send an SMS naming the monitor, the minutes open and the incident link
- Send only to the on-call numbers saved in your rota. Never text a customer
- Do not re-text the same person about the same incident within the cooldown you set
Done when The next person on the rota has been texted about each stale incident.
-
3
Telegram - post the escalation
telegram.org How to Automate Telegram
WebRun opens Telegram to post the escalation. - Open your engineering channel in Telegram
- Post the escalation with the monitor, the age of the incident and who was paged
- Add a follow-up line when an incident is later acknowledged or resolved
- Stay silent when every open incident already has an owner
Done when The engineering channel shows every escalation raised on this run.
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 text customers or update a status page?
No. The Twilio SMS goes only to the on-call numbers in your rota, and WebRun never posts to a public status page. Any customer-facing update stays a human decision.
Does it acknowledge or resolve incidents itself?
No. WebRun only reads the incident list and escalates. It never acknowledges, never resolves and never silences a monitor, so the record in Better Stack stays honest about who actually responded.
How do I stop it texting the same person repeatedly?
Set a cooldown. WebRun texts a given person about a given incident once per cooldown window, then moves to the next name on the rota rather than repeating.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.