Feature: Slack Integration

Workflow integration.

Overview

The Nova Slack integration meets incident response where teams already work. Most engineers run incidents in Slack; the integration provides ack, escalate, and summary actions without forcing a context switch to a separate UI.

• Auto-created incident channels. Each incident spawns its own channel with relevant team members invited. Investigation lives in one place.
• Slash commands. /nova ack, /nova escalate, /nova summary drive the response without leaving the keyboard.
• Auto-summary for postmortems. Channel transcript becomes the postmortem timeline draft. Less manual reconstruction afterwards.
• Bidirectional context plus per-team routing. Slack comments flow into Nova; Nova insights post into Slack; alerts route to the owning team’s channel.

The approach

Three habits make the Slack integration earn its keep: auto-create the incident channel, expose action verbs as slash commands, and capture the channel for the postmortem.

• Incident channel auto-created. Per-incident dedicated space. The investigation history is one searchable artefact.
• Slash commands for action. Ack, escalate, and summary. The most-used verbs are one keystroke away.
• Auto-summary for postmortem. Channel transcript becomes the timeline draft; the postmortem starts from real data, not blank.
• Per-team routing. Alerts route to the owning team’s channel. Cross-team coordination is in one Slack workspace, not seven.

Why this compounds

Each incident handled in Slack reduces context-switching cost. Compounded across the year, the savings show up as faster MTTA and cleaner postmortems.

• Faster incident response. Slack reduces context switches. MTTR drops measurably on the first quarter of use.
• Better postmortems. Auto-summary provides the timeline; the human spends time on analysis, not on reconstructing what happened.
• Better adoption. Slack-first matches actual team workflow. Engineers reach for the tool reflexively.
• Year-one investment, year-two habit. The first integration takes a sprint to wire. By year two, every incident runs through the same pattern.