Write Your On-Call Handoff Summary
Every Monday morning, WebRun opens PagerDuty to collect the past week's incidents and alert counts, cross-references Jira for any open follow-up tickets, and posts a structured handoff summary to Slack so the incoming on-call engineer is fully briefed.
How can I automatically write an on-call handoff summary at the end of every shift?
Every Monday morning, WebRun opens PagerDuty to collect the past week's incidents and alert counts, cross-references Jira for any open follow-up tickets, and posts a structured handoff summary to Slack - so the incoming on-call engineer is fully briefed before picking up the pager.
- Incoming on-call engineer briefed before their shift starts
- Incident summary and open follow-ups captured in one place automatically
- Handoff quality consistent every week without manual effort
Built for SRE teams · DevOps engineers · 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
app.pagerduty.comin a real browser with your saved login - no setup, no API keys. -
1
PagerDuty - collect last week's incidents
pagerduty.com
WebRun opens PagerDuty to collect last week's incidents. - Open PagerDuty Analytics and filter incidents to the past 7 days
- For each incident, read the title, severity, duration, and resolution summary
- Note any incidents still open or pending post-mortem
Done when All incidents from the past week are captured with their status and summary.
-
2
Jira - list open follow-up tickets
atlassian.com
WebRun opens Jira to list open follow-up tickets. - Search Jira for open bugs or tasks tagged with your on-call label
- List each ticket's title, priority, and owner
- Flag anything blocking or unassigned
Done when Open follow-up tickets are listed with priority and ownership status.
-
3
Slack - deliver the handoff report
slack.com
WebRun opens Slack to deliver the handoff report. - Post the structured handoff to #on-call: incident summary, open tickets, and any known risks for the coming week
- Tag the outgoing and incoming engineers by name
Done when Both engineers have the handoff report 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
Can it reassign the on-call rotation automatically?
No - changing the PagerDuty schedule is a people-management action. WebRun writes the report; scheduling stays in your hands.
What if there were no incidents last week?
It posts a brief 'All quiet last week' message - silence is worth confirming, not skipping.
Can I add custom sections to the handoff?
Yes. Tell WebRun what else to include - runbook links, upcoming maintenance windows, key metrics - and it weaves them into the report.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.