An incident is the unit of response: it groups the alerts, the people, the war room, the timeline, and the updates for one problem. Vibe OnCall can detect incidents from Slack or Teams conversations, from email, or from alerts, and runs the incident inside the channel your team already uses.
Where to find it: the Incidents dashboard in the web app, and the Vibe OnCall bot in Slack or Microsoft Teams.
- Incident Detection & Creation — how incidents get created: detected in chat, declared from an alert, or declared by a person.
- Incident Detection from Email — turn an inbound email thread into an incident.
- Incident Lifecycle — the states (Open → Acked → Blocked → Observation → Resolved → Archived) and how to change them.
- Incident Resolution — closing an incident out.
- The Incidents Dashboard — list, board, filters, and the date-range filter that hides older incidents by default.
- Incident Detail View — everything on one incident: summary, timeline, responders, linked alerts.
- Incident Templates and Incident Email Templates — reusable structure for incidents and status emails.
- Incident Meeting Links — attach a standing bridge (Zoom, Meet, Teams) to incidents.
- Sending Incident Updates by Email — keep stakeholders informed without adding them to the war room.
- Service Responders and Stakeholders — who is pulled in automatically when a service is affected.
- Custom Incident Statuses — add your own statuses (early access).
- Tabletop exercises — rehearse an incident with Vibe OnCall driving the scenario.
After it is over: After the incident covers postmortems.
Last reviewed: 2026-08-27 · Still stuck? Email [email protected]
Incident Detection & Creation
Incident Detection from Email
Incident Lifecycle
Incident Resolution