Incident Channels

resolve for incident channels captures context directly from your incident slack channels, and brings autonomous investigations into your incident workflows it builds an evolving picture of the incident, and helps responders move faster at every stage from first detection to postmortem feature overview incident channels let resolve ai treat specific chat channels as live incident investigations recognizes incident channels by naming convention admins set a naming prefix (e g incident , inc , sev1 ) any matching channel resolve is invited to is treated as an incident channel captures and understands incident context resolve understands channel messages, links, logs, and other artifacts it classifies them into symptoms, human findings, impact updates, and evidence so it can reason about the incident as it unfolds runs an autonomous investigation in the background once it has enough context to understand the problem, resolve starts an incident investigation and continuously updates it as new information appears in the channel answers questions with full incident context any @ mention in the incident channel sees the current investigation state, including prior messages, links, and evidence responders can ask resolve to check logs, dashboards, inspect deployments or prs/mrs provides instant “catch up” summaries for new joiners when a new person joins the channel, resolve can send them a private, concise summary of what’s happened so far—only visible to them generates postmortems resolve can create a postmortem draft from the incident channel’s activity and the investigation timeline, findings, impact, and supporting links, ready to paste into google docs, notion, jira, linear, and more getting started prerequisites resolve's https //docs resolve ai/app for slack is installed in your workspace you have administrative permissions to workflows in your incident automation tool you have admin access to resolve ai 1\ add your incident channel prefix in the left panel, go to admin > incident channels set one or more channel name prefixes that your org uses for incident channels, for example incident sev1 , sev2 inc save the configuration what this enables any time resolve is invited into a channel whose name starts with this prefix, it treats that channel as an incident channel and begins ingesting context for investigations 2\ configure channel behavior in the same incident channels settings page, choose how resolve behaves mention triggered responses resolve responds when explicitly @mentioned in the channel this is always on, ensuring resolve is available in the channel catch up new participants (optional) toggle this on so new joiners get a private summary of the incident so far recommended for busy incident channels with many stakeholders 3\ automate resolve's invitation to your incident channels (optional, but recommended) to avoid manually inviting resolve to each of your incident channels, connect your paging or incident workflow tools so they automatically create channels and invite resolve using a webhook select the collaboration tool integration instance (e g myslack) create a new webhook copy the webhook endpoint url and headers to your incident orchestration tool (e g pagerduty, opsgenie, zapier or a custom incident slackbot) configure the webhook payload as per the instructions ( {"channelid" "\<channelid>"} ) 4\ use resolve in your next incident channel once the above is configured an incident is declared via your chosen workflow (e g pagerduty, slack command, zapier, opsgenie, etc ) a channel is created with your incident prefix and resolve is invited using a webhook resolve captures incident context, starts an investigation, and posts an “investigation started” message responders ask @resolve to check logs, deployments, impact, or status use catch up summaries for new joiners request a customized postmortem draft at the end of the incident by using an inline prompt such as @resolve create a post mortem for me that covers 1 incident title, 2 a summary and narrative of the issue, its impact and the root cause, 3 details of the root cause, 4 detailed timeline of findings and actions, 5 impact analysis, 6 lessons learned and action items