What's New in
Phoenix Incidents

Send a stakeholder update in one click.

There is now a Suggest With AI option in the Send Update modal in Slack. During high-severity incidents, Incident Commanders are entirely consumed by technical troubleshooting. They often forget to update the broader company, or drafting those updates takes vital focus away from fixing the issue.

With Suggest With AI, the Incident Commander can instantly generate a high-quality summary of the engineering chat with one click, keeping stakeholders informed while keeping engineering focused on mitigation.

1. 1

   Open the Send Update modal in your Phoenix incident Slack channel

2. 2

   Click Suggest With AI to generate a summary of the engineering chat

3. 3

   Review, edit if needed, and send to stakeholders

Come late to an incident? Get caught up instantly.

When an incident escalates and a new engineer or subject matter expert is paged in late, they have to scroll through dozens or hundreds of chaotic messages to catch up.

Type /phoenix recap and the Phoenix bot provides a succinct AI-driven summary of what has happened, what has been ruled out, and what the current status is — saving critical minutes of onboarding time during triage.

1. 1

   Type /phoenix recap in any active Phoenix incident Slack channel

2. 2

   Phoenix returns an instant TL;DR of the incident

Tag any Slack message directly into the incident timeline.

Building an accurate post-incident timeline is historically painful because engineers rarely stop to log timestamps mid-crisis.

React to any Slack message in an incident channel with the ⌚ watch emoji and Phoenix automatically bookmarks that moment and logs it into the incident timeline, ensuring zero context is lost for the post-incident review.

1. 1

   See a critical message in your Phoenix incident Slack channel

2. 2

   React with the ⌚ emoji

3. 3

   Phoenix logs it to the incident timeline automatically with its exact timestamp

A safe middle-ground for your RCA approval process.

Often, an engineering team finishes their initial internal Root Cause Analysis, but it still needs to be formally reviewed by security, compliance, or leadership before being published.

The new optional Review status in the RCA workflow creates a safe middle-ground where the technical write-up is complete but remains open for broader feedback without prematurely closing the loop or skewing operational metrics.

1. 1

   Engineering team completes the internal RCA analysis

2. 2

   Move the RCA to Review status — it stays editable

3. 3

   Compliance, security, or leadership adds feedback and signs off

4. 4

   Close the RCA when approved — metrics stay accurate throughout

A formal stage between fixing the problem and calling it resolved.

When a fix is deployed, the incident is not truly Resolved. The team needs to watch the dashboards to make sure the fix holds.

The new Monitoring status creates a formal stage that stops the active resolution clock but alerts the business that the fire is out, giving engineers breathing room to verify stability before completely closing the ticket.

Turn a finished RCA into an executive briefing in one click.

An RCA is deep by design — exactly what engineering needs, and more than leadership has time to read.

The new Executive Summary section writes the briefing for you: Phoenix reads the finished analysis plus incident context and drafts a clear, non-technical summary right inside the RCA in Jira.

1. 1

   Complete the guided RCA in Jira

2. 2

   Click Generate Executive Summary

3. 3

   Review, adjust, and share with leadership