> For the complete documentation index, see [llms.txt](https://docs.pagerly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pagerly.io/incident-response/incident-roles-and-updates.md).

# Incident Roles & 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](/incident-response/postmortems.md)).

## 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.