For the complete documentation index, see llms.txt. This page is also available as Markdown.

Incident Roles & Update Reminders

Assign named response roles (Incident Commander, Comms Lead, Scribe, Ops Lead) and keep the incident channel updated with status-update reminders.

Beyond the single assignee, Pagerly lets you assign named response roles for a coordinated response, and set status-update reminders so the incident channel never goes quiet.

Incident roles

The assignee stays the primary owner used for paging and escalation. Roles add clear responsibilities on top:

Role
Responsibility

Incident Commander

Owns overall coordination

Comms Lead

Handles stakeholder communication

Scribe

Documents the incident timeline

Ops Lead

Drives the technical response

Assigning a role

  • From Slack β€” incident action menu (β‹―) β†’ πŸ‘€ Assign Role β†’ pick the role and the person. Leaving the person empty unassigns the role.

  • From the dashboard β€” use the Roles & Updates panel on the incident page.

When a role is assigned, Pagerly posts it into the incident thread and records it on the incident timeline (so it flows into the postmortem).

Status-update reminders

Keep stakeholders informed by scheduling a nudge for the next status update.

  • Set a reminder β€” incident action menu β†’ ⏰ Set Update Reminder (or the Update reminder control on the dashboard). Choose 15 / 30 / 60 / 120 / 240 minutes.

  • When it's due β€” Pagerly posts a nudge into the incident thread mentioning the assignee, with Post update and Snooze 15m buttons.

  • Auto-clear β€” posting an update or a comment on the incident clears the pending reminder automatically, so you're only nudged when the channel actually goes quiet.

Last updated