Incident Analysis

Phoebe generates structured post-mortems from your incident Slack channels. It identifies contributing factors, suggests remediations, and builds an incident knowledge base to help prevent and debug future issues.

​

Overview

Incident analyses are structured around the key questions after an incident:

• What happened - summary and timeline
• What contributed - evidence-backed causes and impact
• How it was resolved - actions taken to fix the issue

In the UI, you’ll also see:

• Attribute cards - key metadata like severity, time to detect, time to resolve, user impact
  
• Cause graph - how contributing factors connect to symptoms
  
• Remediations - user-mentioned or Phoebe-suggested actions to prevent recurrence
  

​

Prerequisites

• @Phoebe Slack app installed (setup guide)
• Phoebe added to the incident channel or thread

​

Generate your first analysis

Add @Phoebe to an incident channel. When prompted, classify the channel type:

• Dedicated incident - one incident per channel. Run @Phoebe analyse. Phoebe will use the entire channel as the incident record.
• Multi-incident - multiple incidents in separate threads. Run @Phoebe analyse inside the relevant thread so data from different incidents isn’t combined.

Phoebe ingests discussion, images, and attachments to produce the analysis. If no analysis is requested, Phoebe auto-generates one after 12 hours of inactivity.

​

Chat

Ask follow-up questions to explore findings, clarify details, or extract information not shown in the report. Common questions:

• “Write a summary for the client in less than 50 words”
• “Give me exact start and end times of the outage”
• “What was the impact on customers?”
• “Give me more lessons learnt”
• “What are alternative titles for this incident?”

​

Additional options

​

Organisation-specific settings

Phoebe can be customised to match your team’s conventions:

• Channel naming patterns for Phoebe to auto-join (#inc-, #issue-,#bug-)
• Severity scale (SEV-1 vs P1 vs High)
• Custom classification attributes
• Incident report templates

​

Quiet notifications

Route analyses update posts to a dedicated Slack channel instead of posting in incident channels:

1. Create a channel (e.g. #phoebe-analysis)
2. Add @Phoebe and classify as Other
3. Run /phoebe notify analysis_update

​

Meeting transcripts

Attach call transcripts to give Phoebe more context.
When a meeting link is shared in the incident channel, Phoebe will prompt you to record a transcript.

​

Backfilling historic incidents

Ingest your past year of incident data to improve analysis quality and enable aggregate insights. Share historic post-mortems or RCA documents (Notion, Confluence, Google Docs, etc.) and we’ll create incident records in Phoebe.