Incident Channels

resolve for incident channels captures context directly from your incident 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 (slack only) recognizes incident channels by naming convention admins define one or more channel name patterns (e g incident , sev? , inc sev ) any channel resolve is invited to whose name matches a pattern 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 as the investigation progresses, resolve can also proactively share evidence backed findings directly in the channel to help responders get to the root cause faster (slack only, beta) 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 (slack only) 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 app for slack 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 set up how resolve recognizes incident channels in the left panel, go to admin > incident channels under set up , you'll configure two independent recognition paths use either or both auto join webhook (recommended) for public incident channels your paging tool opens when your tool posts a webhook to resolve, resolve joins the channel and treats it as an incident automatically (no name pattern required) 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 (e g {"channelid" "\<channelid>"} ) this automation adds resolve to public channels only, because slack doesn't allow apps to add themselves to private channels for a private channel, use the pattern path below and invite resolve manually channel name pattern for channels a human adds resolve to ( /add the resolve app, or @resolve in the channel), public or private any channel whose name matches a pattern is treated as an incident in the channel name pattern card, add one or more patterns use to match any run of characters and ? to match a single character examples incident , sev? , inc sev 2 decide how resolve acts in the decide how resolve acts section, choose how resolve behaves settings apply org wide to every incident channel resolve joins respond when mentioned resolve responds when explicitly @mentioned in the channel this is always on, ensuring resolve is available in the channel catch up new participants (slack only) toggle this on so new joiners get a private summary of the incident so far recommended for busy incident channels with many stakeholders proactively share insights (beta, slack only) toggle this on to let resolve participate proactively in the channel in two ways thread follow ups in a thread resolve is already participating in, it understands follow ups without a new @mention (e g "can you elaborate on that?") and responds it won't chime in on threads it isn't already part of incident insights when resolve's investigation finds something worth flagging, it shares a concise summary in the channel these are evidence backed, specific, and haven't already been discussed the goal is to surface new, concrete signals that help responders get to the root cause faster, not repeat what's already known posting mode for incident insights controls how resolve posts resolve decides (recommended) resolve posts new messages for new working theories and root cause shifts, and replies in thread for supporting details and follow ups single thread resolve posts all updates only within the thread it creates at the start of the investigation anyone following that thread will receive notifications as new updates are added note proactive messages include a mute button if someone mutes it, resolve will stop posting proactively in that incident channel 3 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 a name matching one of your incident channel patterns, and resolve is invited using a webhook resolve captures incident context, starts an investigation, and posts an "investigation in progress — i'm here to assist " 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 prerequisites resolve's app for ms teams (beta) https //docs resolve ai/app for ms teams beta is installed in your organization you have admin access to resolve ai 1 add resolve to your incident channel or group chat add @resolveai to the teams channel or group chat you want to use for the incident resolve will post a configuration card welcoming you and prompting you to configure the channel 2 configure the channel as an incident channel in the configuration card, click configure channel when prompted to choose a channel type, select incident resolve will configure the channel and begin capturing incident context 3 use resolve in your incident once configured resolve captures incident context, starts an investigation, and posts an "investigation in progress — i'm here to assist " message responders can @resolveai at any point to ask questions, check logs, deployments, or request a postmortem draft