Hand off the Mattermost on-call channel
At every shift change, WebRun opens the Mattermost on-call channel, summarizes open incidents and unresolved threads from the outgoing shift, posts that summary to Slack as the permanent record, and sends the incoming on-call person a direct Telegram alert so nothing gets lost between shifts.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I hand off an on-call Mattermost channel cleanly?
At every shift change, WebRun summarizes open incidents and unresolved threads from the outgoing Mattermost on-call channel, posts that summary to Slack as a searchable record, and sends the incoming on-call person a direct Telegram alert. Resolving the actual incidents stays with the engineers, shift to shift.
- Every shift starts with a clear, written handoff
- Nothing open gets lost between outgoing and incoming on-call
- Handoffs build a searchable history in Slack over time
Built for DevOps and SRE teams · IT support · on-call engineers · incident response 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
mattermost.comin a real browser with your saved login - no setup, no API keys. -
1
Mattermost - summarize open items
mattermost.com
WebRun opens Mattermost to summarize open items. - Open the on-call channel in Mattermost
- Collect threads and incidents still open at shift end
- Note who was handling each one
Done when Every open item from the outgoing shift is summarized.
-
2
Slack - post the handoff record
slack.com How to Automate Slack
WebRun opens Slack to post the handoff record. - Post the handoff summary to the on-call record channel
- List each open item with its current status
- Keep this as the searchable shift history
Done when The handoff summary is posted to Slack.
-
3
Telegram - alert the incoming on-call
telegram.org How to Automate Telegram
WebRun opens Telegram to alert the incoming on-call. - Send the incoming on-call person a direct Telegram message
- Highlight anything that needs immediate attention first
- Leave the response and next steps to them
Done when The incoming on-call person has the handoff on Telegram.
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 WebRun resolve open incidents itself?
No. It only summarizes what's still open and hands it off. Resolving an incident stays the job of the on-call engineer.
Why post to Slack as well as Telegram?
The Telegram message gets the incoming on-call person moving fast. The Slack post keeps a searchable record of every handoff over time.
What if the outgoing shift had nothing open?
The handoff still posts and simply confirms there's nothing outstanding, so the incoming on-call person starts with a clean record either way.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.