Most incidents your team declares share the same shape — the same responders, severity, war room, and bridge link. An incident template captures that shape once, so declaring becomes picking a template and adjusting rather than rebuilding under pressure.
What a Template Captures
A template holds the fields you'd otherwise fill in by hand each time:
- Title and description — a starting point for the incident summary. Teams often use these to encode a naming convention (for example, service · region · symptom) that responders complete when they declare.
- Severity — the default severity level (e.g. SEV1, SEV2).
- Responders — users and teams that are automatically added to the incident.
- Labels — incident labels applied on creation.
- Meeting link — a preset bridge (Google Meet, Zoom, or Microsoft Teams) that's attached to the incident automatically when the template is applied.
- War room — when enabled, a war room is created automatically as the incident is declared. Its name follows your organization's war room channel naming setting.
- Custom fields — any custom field values your organization tracks.
Note: Meeting links are managed once at the organization level, so a template points at a preset link rather than a raw URL — when the bridge changes, you update it in one place.
Managing Templates
Templates are created and maintained from the Vibe AI dashboard. From the templates settings page you can:
- Create a new template — give it a name, then set any of the fields above. Only the name is required; leave everything else empty and fill it in at declaration time.
- Edit an existing template — update any field at any time. Changes apply to future incidents only; incidents already declared from the template are not affected.
- Delete a template you no longer need.
Note: Referenced responders, teams, labels, and meeting links are validated against your organization. If one is later removed, it's simply dropped from the template the next time it's used — the rest of the template keeps working.
