G2

Luca G.

Director of Engineering

Mid-Market (51-1000 emp.)

7/27/2026

"Native Slack Incident Management That Automates Follow-Ups and Post-Mortems"

4.5/5

What do you like best about incident.io?

The automated incident lifecycle is the standout. The moment an alert fires, a dedicated Slack channel spins up with severity, incident manager, and reporter already assigned, and the status timeline (Investigating → Fixing → Documenting → Closed) updates itself as the team works the problem. Post-mortems and follow-up tracking are built into the same flow, and the automated nudges for overdue follow-ups have noticeably cut down on action items that used to quietly disappear after an incident closed. On-call scheduling and escalation paths are flexible enough to model our actual team structure, and moving a team over from our old alerting setup took minutes rather than a project.

The Slack integration in particular feels native rather than bolted on — incidents, alerts, escalations, and even AI-driven investigation summaries all show up directly in-channel, so nobody has to context-switch to a separate app mid-incident. We've also wired it into our observability stack, and it correlates incidents against historical data and recent code changes with very little manual setup. It's held up reliably even under long, multi-hour, customer-impacting incidents, and it's never been the thing that broke or slowed us down while we were already firefighting.

We haven't run a formal ROI study, but the value shows up clearly in what stopped happening: fewer forgotten follow-ups, less time spent reconstructing "what happened and when" during a post-mortem, and far less manual bookkeeping overall. For a team our size, that time saved has made it an easy tool to justify keeping. Review collected by and hosted on G2.com.

What do you dislike about incident.io?

Rollout of newer capabilities (we're piloting the AI investigation features) has been env-by-env rather than everything at once, so early trials were scoped to a single production environment before expanding further. We also hit a real constraint connecting only one Grafana instance at a time, which meant some environments had metrics available but not full dashboard context. None of this touches the core incident workflow, but it's worth planning around if you're rolling out across a multi-environment setup like ours. Review collected by and hosted on G2.com.

What problems is incident.io solving and how is that benefiting you?

Before this, incident response lived across a mix of manual Slack channel creation, Opsgenie for alerting, and a lot of tribal knowledge about who to page and how to write up what happened afterward. That meant real toil during incidents (someone had to remember to create the channel, tag the right people, track status) and even more toil after (post-mortems and follow-ups that depended on someone's memory and discipline to actually get written and closed out).

incident.io took that manual overhead off our plate. Alerts now route straight into a structured incident with a channel, severity, and incident manager assigned automatically, so responders can focus on the actual problem instead of the process around it. The follow-up nudges have been the quieter but bigger win: action items that used to fall through the cracks after an incident closed now get chased automatically, which has genuinely improved our follow-through on fixing root causes rather than just resolving symptoms. And because the whole timeline is captured as it happens, writing post-mortems is mostly assembly rather than reconstruction from memory.

Net effect: less time spent on incident bookkeeping, better on-call coverage across teams, and a much more reliable trail from "something broke" to "here's what we changed so it doesn't happen again." Review collected by and hosted on G2.com.

Response from Cristina Carnazzo of incident.io

edit

Hi Luca,

Thanks for taking the time to leave such a thorough review! Great to hear the automated incident lifecycle, native Slack experience, and follow-up nudges are taking the toil out of both the response and the write-up. Also glad to hear you're piloting the AI investigation features too. Thanks for flagging the env-by-env rollout and the single-Grafana-instance constraint, that's useful, and I'll pass it along to our team. Thanks for being a customer!

Cheers,

Cristina