---
title: incident.io Reviews
meta_title: 'incident.io Reviews 2026: Details, Pricing, & Features | G2'
meta_description: Filter 228 reviews by the users' company size, role or industry
  to find out how incident.io works for a business like yours.
aggregate_rating:
  rating_value: 4.8
  review_count: 228
  scale: '5'
date_modified: '2026-07-31'
parent_category:
  name: IT Management
  url: https://www.g2.com/categories/it-management
---

# incident.io Reviews
**Vendor:** incident.io  
**Category:** [Incident Management Software](https://www.g2.com/categories/incident-management)  
**Average Rating:** 4.8/5.0  
**Total Reviews:** 228
## About incident.io
Incidents can be stressful, but they don’t have to be. incident.io helps tech-led businesses navigate incidents from declaration to post-mortem and well beyond. Built on the experience from thousands of incidents, from small bugs to SEV-1’s, incident.io eliminates anxiety, uncertainty, and chaos experienced by responders during an incident. With an elegantly-designed interface, streamlined and transparent communication channels via Slack, and powerful workflows that bring automation and flexibility to your response process, incident.io minimizes communication silos and helps eliminate manual processes. With incident.io, you can focus on improving your product’s reliability and reducing downtime. With over a dozen integrations with popular tools like PagerDuty, Jira, and Backstage, incident.io ensures seamless connectivity throughout the incident response process. Trusted by industry-leading companies, including Etsy, monday.com, and Skyscanner, incident.io empowers faster incident resolution and cultivates shared understanding of roles and responsibilities among your team members. End-to-end incident management from the first alert to the final follow-up, with On-call, incident response, and status pages in one powerful incident management platform. Leveraging powerful dashboards that provide deep insights, engineering teams can learn from past incidents and apply cumulative knowledge to build more resilient products. With an intuitive interface that can be used by everyone — from the SRE, to the CS rep, to the CEO — and a seamless user experience, incident.io meaningfully improves your incident management process so that you can spend less time responding to incidents and more time fostering customer trust.



## incident.io Pros & Cons
**What users like:**

- Users appreciate the **ease of use** of incident.io, which streamlines incident management and enhances overall workflow efficiency. (55 reviews)
- Users value the **powerful Slack integration** for its efficiency in managing real-time incident responses and communication. (45 reviews)
- Users praise the **helpful and responsive customer support** of incident.io, making their onboarding seamless and enjoyable. (41 reviews)
- Users love the **seamless integrations** of incident.io, enhancing incident management and collaboration through various platforms. (29 reviews)
- Users appreciate the **excellent customer satisfaction** with incident.io's seamless UX and responsive support throughout the process. (25 reviews)
- Intuitive (24 reviews)
- Features (20 reviews)
- Easy Setup (19 reviews)
- Automation (16 reviews)
- Customizability (13 reviews)

**What users dislike:**

- Users note the **lack of robust reporting features** for enterprise needs, limiting effective analytics and customizations. (11 reviews)
- Users note **integration issues** with incident.io, finding it lacks depth and requires manual steps for effectiveness. (9 reviews)
- Users express frustration over **limited customization** options, particularly for notifications and reporting features in incident.io. (8 reviews)
- Users express frustration over **limited features** , wishing for enhanced customization and more robust functionality in incident.io. (8 reviews)
- Users note several **feature issues** with the public API and catalog creation, impacting integration and usability. (7 reviews)
- Learning Curve (4 reviews)
- Users find the **setup and configuration confusing** , especially regarding escalation paths and the UI's frequent changes. (3 reviews)
- Template Issues (3 reviews)
- Overwhelming (2 reviews)
- Search Difficulty (2 reviews)

## incident.io Reviews
  ### 1. Phenomenal Support, Powerful AI Features, and Tons of Integrations

**Rating:** 5.0/5.0 stars

**Reviewed by:** Guilherme R. | Incident Manager, Enterprise (> 1000 emp.)

**Reviewed Date:** July 29, 2026

**What do you like best about incident.io?**

We really value the number of available integrations (e.g., Calendar Feeds, Confluence, Jira, Emails, Incoming Calls, Prometheus, Cronitor, Vanta, and Zendesk). Our team also appreciated the AI features, such as postmortem generation, incident interactions that help manage the full lifecycle, and the integration with the Scribe agent. Lastly, the support we received throughout pre-sales, onboarding, and post-go-live has been phenomenal.

**What do you dislike about incident.io?**

The Insights dashboard still feels pretty limited, with only a handful of options for building a custom dashboard. License management also isn’t very straightforward, since there’s no way to get notified when a new Response seat is assigned or when someone is offboarded from Okta and loses their on-call seat.

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

We now have a single, unified platform to manage our incidents end-to-end. Incident.io is fully integrated with Slack, allowing our teams to handle the entire incident lifecycle directly in Slack. Previously, we had to juggle three different applications to do the same work.

  ### 2. Native Slack Incident Management That Automates Follow-Ups and Post-Mortems

**Rating:** 4.5/5.0 stars

**Reviewed by:** Luca G. | Director of Engineering, Mid-Market (51-1000 emp.)

**Reviewed Date:** July 27, 2026

**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.

**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.

**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."

**Official Response from Cristina Carnazzo:**

> 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

  ### 3. Boosted Incident Response with Better Slack Swarming and Clearer Bridge Comms

**Rating:** 4.0/5.0 stars

**Reviewed by:** Jason F. | Telemarketing Executive, Mid-Market (51-1000 emp.)

**Reviewed Date:** July 20, 2026

**What do you like best about incident.io?**

Obviously using Slack and it's integrations with that has meant we are able to swarm incidents much more effectively. We have made a conscious choice to not use the responder element of INC IO, but I do think in the sales process if that functionality was expanded on then the ROI on INC IO would have not just been focused on effectiveness of INC MGMT (MTTR) but also on tool consolidation. 

The use of scribe in our bridges has materially increased stakeholders understanding of how incs are progressing, and has also allowed the INC commander to be able to generate comms from the bridge, with only needing to skim read before publication.  I like using the browser version and ask the AI tool for a summarization/questions that I used to direct to the INC commandaer role, freeing them up to be more effective.

I am excited for the SRE function to be launched.

**What do you dislike about incident.io?**

It feels like you started with INC and then bolted on other elements afterward (retro, status page, responder, SRE). A clearer articulation of your roadmap would give customers a better lens into where you’re headed, and how that direction could align with simplifying things internally.

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

The INC process was poor and ineffective. Even though the tool is only one part of our overall maturity, it has still enabled us to drive meaningful, material improvements.

  ### 4. Massive Time Savings with AI Scribe and Deep Slack Integration

**Rating:** 5.0/5.0 stars

**Reviewed by:** Gavin W. | Site Reliability Engineer, Small-Business (50 or fewer emp.)

**Reviewed Date:** July 16, 2026

**What do you like best about incident.io?**

The configurability and AI "Scribe" bot that helps document an incident as its happening have been massive time savers for our team, especially in stressful time-sensitive situations. The deep integration with Slack is also useful for our organization as its fast to alert engineers, as well as the wider business to any incident, and its current status. 

There have been no performance issues, and the UI is easy to use and understand.

We received a very hands-on onboarding experience, with our representative from incident running multiple simulations for us and tailoring our demos to our specific use case. We found a pricing tier that worked for us, and may consider expanding it wider in our organization in the future.

**What do you dislike about incident.io?**

The range of options for configuring the account and setting up routing rules can feel overwhelming at first. A few settings are also difficult to fine-tune for our use case until we’ve worked through a couple of real incidents and seen how everything behaves in practice.

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

Replacing multiple tools (PagerDuty/Datadog Incident management) with one tool for both on-call, incident response, status pages, and post-mortems.

Having the single place to go has been great at improving our incident response time, and keeping good records so we continue improving our processes.

  ### 5. incident.io Streamlines Incident Management with Helpful Automations and Integrations

**Rating:** 4.5/5.0 stars

**Reviewed by:** Mark G. | Technical Program Manager, Enterprise (> 1000 emp.)

**Reviewed Date:** July 13, 2026

**What do you like best about incident.io?**

Having a single platform to manage our full set of Incident Management processes makes it easy to get everything working together. As a result, responders don’t have to worry as much about the tools and can focus on resolving incidents.

The incident.io team has also improved their incident-time automations a lot. The suggestions and summaries they provide during incidents are usually very helpful for responders. On top of that, the incident.io team is incredible to work with: they’re very responsive when we need support, and since day 1 they’ve been happy to take on feedback to improve the product. They also ship incredibly quickly, which continually increases the value of the product. I feel like there’s always a new tool or feature to try.

**What do you dislike about incident.io?**

Their reporting tools could generally do with a bit more love, although I get the sense the team is already working on it.

I also feel that feature discovery within the product could be stronger. I’d like to see something like a checklist or smart suggestions for people who manage incident.io instances, so it’s easier to make sure they’re using the full toolkit. That said, it might just be a me problem!

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

Having a central platform for everything incident-related makes it much easier to ensure our process actually works, compared with relying on multiple disparate tools that can distract or confuse responders. The strong integration with Slack also means responders can spend more time communicating with each other, rather than having to jump into yet another platform.

It also feels like the incident.io team is heading in the right direction with AI tools like MCP and things like their desktop app, helping responders do the work where they need to do from the places they're already working.

**Official Response from Cristina Carnazzo:**

> Hey Mark, thanks so much for taking the time to leave such a thoughtful review. You're correct that we're always looking to improve reporting, but if there's something specific please call it out! Good to hear you're finding the AI tools and MCP useful, lots more to come there!

Cheers,
Cristina

  ### 6. Seamless Integrations, Top-Notch Support, and Powerful AI Flows

**Rating:** 5.0/5.0 stars

**Reviewed by:** Vaggelis K. | Incident Manager, Enterprise (> 1000 emp.)

**Reviewed Date:** July 13, 2026

**What do you like best about incident.io?**

The product is continuously updated with new features. It’s easy to use, and it’s straightforward to set up workflows, on call schedules, and status pages. Everything connects seamlessly with our ways of working, and there are multiple integrations available. The support team is top-notch and responds quickly. The app’s performance is great; we rarely experience any lag. AI flows have started helping us from the initial handling, especially with follow-ups and post-mortems.

**What do you dislike about incident.io?**

The only thing I can think of is that we’d like to have a feature projection map or a feature roadmap that’s available in near real time for enterprise users. The team is shipping updates and new features all the time, but it would be even better to have clearer visibility into what’s coming in the next quarter’s features.

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

There are too many to simple state them here. 

problems that require cross department handling - its a piece of cake. we invite all the relevant stakeholders with 3-4 clicks. 

on incidents - handling its 900% better than before. 
we had issues with status pages via atlassian, now everything is connected with the incident.io ecosystem and works flawlessly. 
the api is also quite useful!

  ### 7. Intuitive and customer-centric product

**Rating:** 5.0/5.0 stars

**Reviewed by:** Jade L. | Incident Response Manager, Mid-Market (51-1000 emp.)

**Reviewed Date:** July 28, 2026

**What do you like best about incident.io?**

The product is very intuitive and easy to use. Their support team is always helpful and when we need some new feature they are eager to understand our needs and at some point we know it'll be delivered. 

The AI is very helpful for handling incidents on a daily basis and the performance is usually great. Something that never tires to amaze me is how their engineering team is aware of when we have problems before we even contact them (we receive notifications from them saying they have noticed we have had problems and they're on the fix beforehand).

The pricing is fair although the new AI features will probably be more pricy than we'd want. 

For integrations I think the team has a lot of improvements to make, specially with SalesForce where the integration is right now basic and doesn't allow us to bring that many customizations.

**What do you dislike about incident.io?**

The product wasn't created thinking in organizations that require regional customizations. Also, the dependency on some external services (for Insights and escalation voice calls for example) are a downside. I trust IncidentIO, and not their partners.

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

IncidentIO helps us provide a clear incident response process in our company.

  ### 8. The Ultimate Incident Management Solution

**Rating:** 5.0/5.0 stars

**Reviewed by:** Andrew K. | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 24, 2026

**What do you like best about incident.io?**

I think incident.io is the best product in the incident management space, which is a big deal for us. It makes on call easy(that's the commodity piece), but truly great incident management is an unlock, creating leverage and accountability within our teams.   It effectively helps with speedy mitigation or remediation of incidents and ensures adherence to our postmortem process for continuous improvement. The platform also provides helpful statistics and insights into our analytics around incidents. I find the AI that joins incident calls extremely beneficial for keeping updates current. Additionally, it simplifies mentioning incidents through its state machine and normal workflow, and the integration into tools like Slack, Linear, and Notion is something we utilize heavily.

**What do you dislike about incident.io?**

The analytics features are new. I wish they were more mature, and there are more ways to slice and dice our data. I've given some of this feedback and have seen quick action when I've given feedback. So just looking for more product development in that area.

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

I use incident.io for on-call scheduling management, alert routing, and incident management. It enhances accountability, speeds up incident remediation, and ensures our postmortem process for continuous learning. The AI improves call updates, and we gain insights from analytics, though I wish they were more mature.

  ### 9. Fantastic fantastic product- and we've tried many prior to being very happy with IIO

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.)

**Reviewed Date:** June 25, 2024

**What do you like best about incident.io?**

Our experience with the IIO platform, PMs, and customer service has been outstanding. Slack communication when we would like suggestions/advice or have feature requests is answered promptly and thoroughly. The employees watching our messages range in specialty and are always available to assist
UI and feature improvement delivery is constant and so impressive
The ease of implementation for us was fantastic, but what I've enjoyed is their suggestions of how to evolve our incident process. We've improved our incident process tailored to our company an incredible amount since adopting IIO. We 100% rely on and use it everyday. 

Huge shout out to Eryn and Jonathan who have been there every step of the way.

**What do you dislike about incident.io?**

There hasn't been anything to dislike about our experience with this company.

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

Incident.io addresses several critical challenges for us, including immediate incident creation for fast turn around, consolidated conversations, AAR automations.
We've started to focus on metrics and followups (Linear/gitlab integration ftw), something that was missing from our org.

**Official Response from Cristina Carnazzo:**

> Thanks so much for taking the time to leave such a thoughtful review! Great to hear incident.io has become part of your everyday, and that the process suggestions have helped you tailor your incident response. Being responsive in Slack and shipping constant improvements is exactly what we aim for. I'll pass the shout-out along to Eryn and Jonathan too. Thanks for being a customer!
  


  ### 10. Slack-Native Incident Management with Powerful APIs and a Responsive Team

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.)

**Reviewed Date:** July 23, 2026

**What do you like best about incident.io?**

The Slack-native workflow is what stands out the most: private channels, timelines, and participant tracking are all created automatically, which cuts down on manual setup during a live incident when every minute matters. On top of that, the API and webhook support have made it easy to build our own automation on top of incident.io without disrupting it as the source of truth for incident state. It's also amazing to have a responsive vendor team that's willing to partner on new features and quick fixes.

**What do you dislike about incident.io?**

The main gap is around workflow automation for our company-specific tasks that surround an incident rather than the incident record itself. Things like provisioning collaboration resources, keeping responder group membership in sync as people join or leave, and calculating incident cost, so we ended up building our own middleware to cover that ground. It works well now that it's built, but it would be nice if there were more automation features out of the box. Nothing that's stopped us from relying on it as our platform of choice, just areas where we've had to build around it rather than use it as-is.

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

Before incident.io, our security team ran on a separate internal tool while the rest of the company had already standardized elsewhere, which meant duplicate tooling, inconsistent reporting, and extra overhead any time a security incident intersected with an engineering one. Moving onto the same platform as the rest of the enterprise solved that fragmentation: everyone works from a single source of truth for incident state, with a consistent timeline, severity/status model, and reporting structure across teams. Moreover, there are benefits in less manual overhead during an actual incident. The Net effect is that we have faster time-to-organized-response, better cross-team visibility into incident trends, and one less system for security engineers to context-switch into during a high-pressure moment.

  ### 11. Intuitive and Engaging Incident Management Tool with Stellar Support

**Rating:** 5.0/5.0 stars

**Reviewed by:** Pedro Ivo M. | Enterprise (> 1000 emp.)

**Reviewed Date:** July 20, 2026

**What do you like best about incident.io?**

For me, the best part of using incident.io is how they engage with us and listen to our feedback. They are always trying to improve the product based on our ideas and proposals, which makes me feel heard and valued. It's also super easy to use, allowing anyone to jump in without needing much instruction. Additionally, I think it's the best data management tool I've used in a while, and I can't even compare it to other products like PagerDuty or Opsgenie. The setup process was quite easy, taking less than a week to set up new integrations and migrate escalations and alerting routes.

**What do you dislike about incident.io?**

The biggest problem people point out in the company is that incident.io doesn't give the flexibility to edit the format of the Slack messages. They would like to be able to customize the messages in the way they want. I understand that standardization simplifies things for them, but this is the only area that could be improved.

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

Before incident.io, our incident management was fragmented. We had alerts coming from multiple sources; Alertmanager, CloudWatch, and Zendesk, but no unified way to manage them. When an incident hit, we'd be jumping between tools to declare it, manage the response, and piece together post-incident reviews. The result was inconsistent, low-quality postmortems and lost context. Incident.io solved that by centralising the entire incident lifecycle in one place. We ingest alerts from all our sources, configure complex routing, and manage on-call schedules and escalations without leaving the system. When an incident fires, we declare it from the alert and drive the whole response directly from Slack; no context loss, no tool-switching. The meeting gets auto-transcribed, and their AI agent helps us keep communication clean and structured, even in the chaos of an active incident. What really sets them apart is the post-incident side. We stay in incident.io to create the report, map follow-ups, and tag all the metadata we need for later analysis—all in one workflow. Late last year, they shipped a feature that used call transcripts and Slack messages to help us review and improve our reports. Then in mid-2026, they automated the initial report draft entirely. That's not just a tool; that's a partner that keeps improving based on how teams like ours actually work.

**Official Response from Cristina Carnazzo:**

> Thanks for taking the time to leave such a detailed review! It means a lot that the engagement and listening come through, being a partner that keeps improving based on how teams actually work is exactly what we're going for. Great to hear that centralizing the whole incident lifecycle, especially the post-incident side, has made such a difference. Thanks for flagging the Slack message formatting, I'll pass that feedback along to our team. 

We appreciate you being a customer. 

  ### 12. Fun, Easy-to-Use Tool with a Streamlined Slack Workflow and Helpful AI Agent

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 27, 2026

**What do you like best about incident.io?**

Easy to use, with a strong post-incident process and sensible defaults. The Slack integration provides a streamlined, intuitive workflow. The catalog also makes it easy to automate flows, and the AI agent helps me get what I need done without having to hunt for the right command.

It’s genuinely fun to use.

**What do you dislike about incident.io?**

Nothing major comes to mind. The pricing was a bit high, but it was worth every penny. Our sales rep was very flexible and worked with us to reach the price point we were targeting.

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

Our incident management process used to be a mess, with a mix of ticket automations, a sub-par on-call solution, and far too many manual steps. incident.io is helping us move toward a more efficient, streamlined, and automated incident response.

On top of that, the clear post-incident process helps us learn from what happened and be more reliable going forward.

  ### 13. Streamlined Incident Management with Robust Automation

**Rating:** 4.5/5.0 stars

**Reviewed by:** Kegan M. | Vice President of analysis, Mid-Market (51-1000 emp.)

**Reviewed Date:** July 16, 2026

**What do you like best about incident.io?**

We like the user interface. The options for customizing different things can be quite detailed, which is really nice. I appreciate the amount of time it saves for old manual processes and the integrations into a lot of our tools. The automations make it really easy for the team to get through incidents, automatically assigning them to the correct teams, nudging people, and using different flows. It's all in one channel, making it very clear who is in charge of what. The summary features help us a lot by automating the process at the end, which used to take a long time manually. It's very straightforward and easy to set up.

**What do you dislike about incident.io?**

We've had slight issues with the out of office hours scheduling and swapping of shifts. Nothing major, but I did see that there was some new information about that released, so maybe they've updated that already.

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

We use incident.io automations to make incident management easy, assigning tasks clearly without confusion. The summary feature saves time by automating the process we used to do manually, all in one place, integrating with Slack and other tools.

**Official Response from Cristina Carnazzo:**

> Thanks for taking the time to leave such a thoughtful review! Great to hear the integrations and summary features are saving your team time, and that assigning and coordinating in one channel is keeping things clear. Thanks for flagging the out-of-hours scheduling and shift swapping, I'll pass that feedback along to our team. Thanks for being a customer!


  ### 14. Effortless Incident Management with Stellar Slack Integration

**Rating:** 5.0/5.0 stars

**Reviewed by:** Marvin H. | CTO, Enterprise (> 1000 emp.)

**Reviewed Date:** July 16, 2026

**What do you like best about incident.io?**

I find incident.io much easier to manage incidents compared to our previous provider, PagerDuty. It's all organized in one Slack channel, the paging settings are smart, and it significantly reduces overhead, allowing me to focus on the incident while keeping stakeholders informed. I really appreciate their attention to detail, with little things like notifications to auto-merge alerts during busy incidents or prompts for cover after tough nights. The Slack-based incident management and the investigation bot are very cool, and it's incredibly easy to set up. I also love that whenever we talk to the incident.io team about smaller features, they quickly implement them.

**What do you dislike about incident.io?**

I sometimes wish there was even more oncall schedule management. What they have is already expansive, there's just little things I'd like to see, but every time we talk to the incident.io team about smaller features they quickly implement them, so I'm sure this answer will be out of date very shortly.

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

I find incident.io makes incident management easier, with smart paging and efficient Slack channels. It reduces overhead, keeps stakeholders informed, and lets me focus on incidents. Their attention to design and user needs is impressive, with features like auto-merging alerts and scheduling help.

  ### 15. Stellar Support and a Feature-Rich, Usable On-Call Platform

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 14, 2026

**What do you like best about incident.io?**

I've PMed the move from Opsgenie to incident.io On-call for our company, and the support we have received from the incident.io team has been nothing less than stellar. They have gone above and beyond to address all of our questions and concerns, and been extremely responsive throughout the process. Their expertise has helped us feel comfortable that incident.io is the right tool for us with it's broad feature set and integrations with our other tools. It is the clear leader in the space from both a functionality standpoint as well as usability and embracing new functionality with AI.

**What do you dislike about incident.io?**

There are some features that could be more fully built out, but whenever we have provided feedback it has been addressed and/or responded to quickly.

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

Moving from Opsgenie to incident.io On-call will allow us to streamline our on-call paging and incident handling workflows into one tool. Having the ability to combine those services together will not only benefit us from a pricing standpoint but further allow us to build automations to reduce user interaction wherever possible.

  ### 16. Centralized Incident Management with Stellar Collaboration

**Rating:** 5.0/5.0 stars

**Reviewed by:** Marinos G. | Enterprise (> 1000 emp.)

**Reviewed Date:** July 13, 2026

**What do you like best about incident.io?**

I love how incident.io organizes post-incident actions and follow-ups. We can create follow-up actions for every incident and link them with Jira tickets, assigning them to teams while tracking progress without manually contacting owners. Integrating Slack for alerting channels, Grafana for metrics, and GitLab for tracking code changes has been great. The collaboration with the incident.io team is helpful, as we can reach out with any questions or requests. Personally, I am very satisfied with how it helped us make huge progress in managing incidents and their follow-ups.

**What do you dislike about incident.io?**

The AI-SRE or investigations feature, as it's called now, doesn't work properly for us. We tested it in both abstract incidents and specific incidents where we knew the root cause. Even when we guided it towards specific changes that we knew caused the incident, it couldn't pinpoint them.

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

I use incident.io for centralized incident management, fast escalations, easy incident tracking and follow-ups, and gaining insights on past incidents. It helps us create follow-up actions linked to Jira, track progress without manual follow-ups, and note significant improvement in incident handling.

  ### 17. incident.io: Flexible Catalog, AI Investigations, and an Intuitive Slack-First Experience

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 10, 2026

**What do you like best about incident.io?**

There are a lot of things I like about incident.io.

The Catalog is one of the standout features. It's incredibly flexible and makes it easy to connect incidents to the people, services, teams, and other metadata that matter to your organisation. Once it's configured, it becomes a really powerful source of context during incidents and post incident reviews.

Their AI-powered investigations feature is also a game changer. It helps surface relevant information quickly, reduces the manual effort involved in triaging incidents, and supports faster, more informed decision-making during high-pressure situations.

The user experience is also excellent. The interface is intuitive, the workflows feel cohesive, and everything fits together naturally. The Slack integration is especially well done. People can start running incidents with very little training, which has made adoption across engineering straightforward.

Finally, the support team has been exceptional. They're responsive, knowledgeable, and genuinely care about helping their customers succeed. Every interaction has felt collaborative rather than transactional, which is something I really value.

**What do you dislike about incident.io?**

There isn't much I dislike about the product. If I had to pick something, it would be that some of the more advanced configuration and workflow features can take a bit of time to fully understand. That's partly because the platform is quite powerful, but it does mean there's a learning curve for administrators.

I'd also love to see continued investment in reporting and analytics. The current capabilities are good, but there is room for deeper insights into incident trends and operational health.

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

incident.io gives us a consistent, low friction way to manage incidents from start to finish. It standardises how incidents are declared, coordinated, communicated, and reviewed, while integrating with the tools our engineers already use.

The Slack integration makes adoption easy, and the Catalog provides valuable context by linking incidents to the right services, teams, and ownership information. As a result, we spend less time managing the incident process and more time resolving customer issues.

  ### 18. Intuitive UI and Native Integrations Make Onboarding a Breeze

**Rating:** 5.0/5.0 stars

**Reviewed by:** Hei Jing T. | Principal SRE, Enterprise (> 1000 emp.)

**Reviewed Date:** July 29, 2026

**What do you like best about incident.io?**

The UI is easy to use and very intuitive, which makes the onboarding process simple. There are also lots of native integrations available right out of the box.

**What do you dislike about incident.io?**

Workflow configuration feels quite limited right now. I’d like to see more customizable features added, such as the ability to build a string using variables.

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

It’s much easier to know who to reach out to and who to escalate to when there’s an issue, so I no longer have to maintain a huge spreadsheet of contacts. The AI features used in meetings also help speed up the documentation process, both during the incident and afterward.

  ### 19. Seamless Incident Management with Robust Slack Integration

**Rating:** 4.0/5.0 stars

**Reviewed by:** Wael N. | Enterprise (> 1000 emp.)

**Reviewed Date:** July 09, 2026

**What do you like best about incident.io?**

I really like incident.io for oncall and incident management. The catalog allows very rich connections between resources and helps us decide what's important. Our oncall teams can manage their own escalation policies and schedules. Incident.io's incident management is flexible, allowing us to add custom fields to better track and handle incidents. The Slack integration is excellent because it allows teams to stay on Slack during an incident without having to jump between tools. Additionally, it was easier to set up than equivalent products, and the support team, especially Sunita, made our migration smoother by driving the process.

**What do you dislike about incident.io?**

The escalation path could use some improvements, such as being able to link one node to another for custom tree shapes and performing if/else over any field, not just the priority. Additionally, the UX around custom fields in incidents could be better thought through; they are both underwhelming and hidden enough to confuse people.

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

I use incident.io for oncall and incident management. It lets us manage escalation policies, track incidents flexibly, and seamlessly integrate with Slack, so we don’t jump between tools. It replaced our custom OpsGenie tools with a tailored solution.

**Official Response from Cristina Carnazzo:**

> Hi Wael, thank you for taking the time to leave a review and also for your thoughtful feedback on the escalation path and custom fields. I've passed it along to the team! Cheers, Cristina

  ### 20. Intuitive, Time-Saving Incident Management with Powerful Integrations

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 09, 2026

**What do you like best about incident.io?**

Key things that we appreciate are the integrations with our alerting stack, the AI / SRE, and integration with our tools such as slack makes incident management intelligent and saves time. The UI is also intuitive and easy to use, at this point we don;t feel there is a better solution.

**What do you dislike about incident.io?**

Nothing major, it might be useful to have some decision type logic in the information fields (if this, then that), so for example, if you have nested sets of values. So, in our case, if you chose a particular root cause or risk type, you could select level one, which would then open up a second set of level 2 values that are only applicable to the level one value.

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

It allows us to distil a complex tech stack with complex issues and alerts, into clear sets of impacts and actions and simplifies our responses.

  ### 21. Fast, Intuitive Incident Management with Excellent Onboarding and Solid ROI

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 24, 2026

**What do you like best about incident.io?**

Very clean and intuitive interface.  Easy to develop on call schedules.  Conversion from on call incident into post mortem is very clean.  Chat logs in the incident response page from the call in real time is super helpful.  Similarly slack management helps a lot.  The application is fast and no real issues.  Pricing is solid in comparison to pagerduty, good ROI.   Onboarding support was very high, they helped us convert everything over and even created additional materials to help onboard folks.  The AI/intelligence features for the post mortem are very useful, haven't really used the AI SRE side as much.  Integration with our observability stack and ticketing was very clean.

**What do you dislike about incident.io?**

No complaints.  Generally everything works well.

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

On call, incident management, and post mortems.  The post mortem tool was way more helpful than I originally anticipated.

**Official Response from Cristina Carnazzo:**

> Thanks for taking the time to leave such a detailed review! Love that the post-mortem tool turned out more useful than you expected. Whenever you're ready to dig into the AI SRE side (Investigations) please reach out, big things about to hit! Thanks for being a customer!

  ### 22. Quickly Resolves Issues with Excellent Support

**Rating:** 4.5/5.0 stars

**Reviewed by:** Laura M. | Scrum Master

**Reviewed Date:** July 13, 2026

**What do you like best about incident.io?**

I love incident.io and its ability to get incidents to the right people really quickly. The support from the team is also really great. When we find a bug or an issue, they are always really quick and responsive to get back to us.

**What do you dislike about incident.io?**

We use incident.io in quite a specific way, which is not entirely aligned with how other customers use the tool. So we have some specific niche requirements in some areas, and it's not always possible to get the system to do what we need.

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

I use incident.io for our call handlers to report issues in our tools reported by customers, which are then quickly routed to the right teams for resolution. We can easily create bug tickets in Jira where further work is needed and update stakeholders throughout.

**Official Response from Cristina Carnazzo:**

> Hi Laura,
Thank you for the kind words about our team, point of pride for us, I'll pas along the compliment!

Cheers,
Cristina

  ### 23. Seamless Incident Management with Stellar Integrations

**Rating:** 5.0/5.0 stars

**Reviewed by:** Alex B. | DevOps Lead, Enterprise (> 1000 emp.)

**Reviewed Date:** July 10, 2026

**What do you like best about incident.io?**

I find incident.io really valuable for streamlining our processes using a single tool. I like that it has app functionality for easier viewing and portability. The awesome integrations with Microsoft Teams and other tools like Jira and Confluence help streamline our operations. What I like most is their UX, which makes the app easy to view and simplifies processes. The initial setup experience was seamless, and the team was super helpful with our tight timelines.

**What do you dislike about incident.io?**

There are some key integrations with Microsoft Teams to make it on par with Slack; however, the team is actively progressing through this and always provides timely updates.

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

I use incident.io for incident management and alerting. It streamlines our processes using a single tool, offers app functionality for easier viewing and portability, and integrates well with Microsoft Teams.

**Official Response from Cristina Carnazzo:**

> Hey Alex,
Thanks for taking the time to leave a review and for your callout around Teams, you're right there are some improvements to be made and it's a big priority for us I can assure you! If there's anything specific you'd like to see we're all ears!

Cheers,
Cristina

  ### 24. Easy Integration, Smooth Daily Use, and Great Support

**Rating:** 5.0/5.0 stars

**Reviewed by:** Henrique P. | Associate DevOps Manager, Mid-Market (51-1000 emp.)

**Reviewed Date:** July 28, 2026

**What do you like best about incident.io?**

Easy integration with current tools, good support during the project phase and after, easy daily operation on the UI and with slack integration.

**What do you dislike about incident.io?**

The reporting tool (Insights) that is provided doesn't offer much customization.

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

A centralized way to handle with incidents and tracking the post-incident actions. The capacity to keep anyone informed about what is happening related to incidents across the company. Just few months after the implementation of the tool we saw a huge improvement of our Incident Management process.

  ### 25. Seamless Incident Management with Responsive Support

**Rating:** 4.5/5.0 stars

**Reviewed by:** David H. | Mid-Market (51-1000 emp.)

**Reviewed Date:** May 19, 2026

**What do you like best about incident.io?**

I really appreciate the support from incident.io staff. Whether it's on the technical side, or related to licensing and billing, they've been incredibly responsive. Even when I've asked about features I'd like to see added to the roadmap, they've responded quickly. Not everything is handled instantly, but there's often a quick turnaround, which I find really impressive. It's been a joy to work with them.

**What do you dislike about incident.io?**

There are some really minor little bits of friction. Sometimes a particular feature hasn't been there or it doesn't have feature parity with a previous solution. The parity level is like 99%, but not quite a hundred. There are slightly irritating UI issues, like cosmetic bugs. For example, in the routing and alerting config, if we could drag to reorder the routes so we didn't have all the lines flowing over each other, that would improve the user experience. But on the whole, these are incredibly minor little things that we can perfectly happily live with.

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

I use incident.io as a one-stop shop for incident management, solving confusion around steps in the process. It guides us consistently through incidents with prompts and nudges.

  ### 26. Effortlessly Manages Incidents, Highly Configurable

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 26, 2026

**What do you like best about incident.io?**

I find incident.io to be very reliable and highly configurable. The team is responsive, and it's just a well-designed product. I really like that we can use Slack channels to triage incidents since we're pretty Slack-centric as a company. The scribe feature is amazing because for each incident channel, we can start a call in which the scribe automatically joins and transcribes the call, creating a really useful record.

**What do you dislike about incident.io?**

I guess we're working with them on improving the routing so that we can simplify it across the organization. We need fewer escalation pads. Also, the setup could have been maybe more straightforward. I think we should have worked with their solutions architect team to help us set things up.

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

I use incident.io to effectively manage incident response and escalations. It's reliable, highly configurable, and integrates well with Slack for triaging incidents. The scribe feature is amazing for creating useful records of calls.

  ### 27. incident.io: Our right hand for incident management

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Banking | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 20, 2026

**What do you like best about incident.io?**

What I like most about incident.io is how much easier it makes handling incidents, especially when things are already stressful. Having updates, actions, and communication organized in one place saves a lot of back-and-forth and helps everyone stay on the same page. The Slack integration also makes it feel like part of our normal workflow rather than another tool we have to manage.

**What do you dislike about incident.io?**

The main downside is that some of the setup and customization can feel a bit overwhelming at first. There are a lot of options, which is useful, but it can take time to configure everything properly and learn where certain features are. Some notifications can also feel a little noisy until you fine-tune them.

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

incident.io helps us manage incidents in a much more structured way. Instead of updates being scattered across Slack messages, documents, and different tools, everything is kept in one place. This makes it easier to assign actions, keep stakeholders informed, and track what happened afterward. The main benefit is that we respond faster, spend less time coordinating, and have a clearer process for learning from each incident.

  ### 28. Defacto Incident Platform for Small-Medium Teams

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User | Small-Business (50 or fewer emp.)

**Reviewed Date:** July 16, 2026

**What do you like best about incident.io?**

I find that incident.io is incredibly helpful for organizing our incident management and review processes. The Slack integration is the best feature, allowing us to keep discussions centralized, which is essential for effective incident response. The incident review dashboard helps us easily review historical incidents, enhancing our knowledge organization. Additionally, the IIO AI SRE tool is very useful as it integrates well with our knowledge base. Setting up incident.io was very easy, making it straightforward for our team to adopt. Overall, it's our defacto incident platform for small-medium teams.

**What do you dislike about incident.io?**

We find it problematic to manage communication with vendors or Slack channels that aren't default managed by Incident.io. Our platform is built on many cloud vendors, and we have individual Slack channels with each for incident communication. We would benefit if Incident.io could integrate these channels for better incident management with vendors.

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

I use incident.io for incident management, tracking, and collaboration. It organizes our process with a channel per incident, maintains discussions in one place, integrates well with Slack, and makes reviewing historical incidents easy.

  ### 29. Seamless Slack Integration and AI-Powered Incident Management

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User | Enterprise (> 1000 emp.)

**Reviewed Date:** July 10, 2026

**What do you like best about incident.io?**

I like the simplicity of incident.io as it makes the platform easy to understand and use, which helps with adoption across teams. I appreciate how it is powered by Slack because we are primarily a Slack workspace, making it easy to declare incidents, coordinate responders, and communicate updates. The AI capabilities, particularly with the feature Scribe, are also a standout for me. These features are especially helpful in reducing the manual effort involved in documenting and summarizing incidents, saving time and ensuring we don't miss any details. I also find the post-incident flow very effective for debriefs and post-mortems.

**What do you dislike about incident.io?**

During the Debrief, Scribe joining the channel manually instead of automatically could be improved. We want the same experience as when an incident is declared and Scribe automatically joins. It takes extra steps to get Scribe in the debrief calls, and we would like the same seamless experience if possible.

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

Incident.io solves our on-call gap coverages and centralizes incident management. It simplifies team adoption, integrates with Slack for easy incident coordination, and AI reduces documentation efforts, ensuring nothing is missed.

**Official Response from Cristina Carnazzo:**

> Hi there, 
Thank you for taking the time to leave a review, we're so glad to know incident.io is helping you reduce manual effort. Regarding Scribe joining automatically, do you happen to use MS Teams? If so we just shipped this feature last week! It should already be enabled for Slack users and is a setting to toggle on or off. Please reach out to me at cristina.carnazzo@incident.io  or your dedicated team if you need any assistance in setting this up!

  ### 30. Simple, effective incident management that engineers actually like

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 09, 2026

**What do you like best about incident.io?**

I really like how incident.io gives us a real operating model for incident management, not just a coordination layer. The Catalog is especially strong because it creates a clear source of truth for services, teams, and ownership, which makes it much easier to route incidents correctly and keep the response structured. I also like how much of the workflow can live in Slack, so responders stay in the same context and we avoid the usual fragmentation across chat, docs, and tickets. The workflows and nudges help enforce discipline around declaration, roles, updates, and follow-ups, which is exactly what you want when you’re trying to run incidents consistently at scale. Overall, it feels like a product that pushes teams toward better incident hygiene rather than just helping them react faster.

**What do you dislike about incident.io?**

My only small gripe is that it can take a bit of time for new users to get comfortable with all the capability, but that’s also a sign of how much the product can do. Overall, it feels like a very thoughtful platform for teams that take incident management seriously.

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

incident.io solves the operational chaos around incident response by giving teams one consistent system for declaration, coordination, communication, and follow-up. What I get out of it is less time spent improvising and more confidence that the right people are paged, the right context is captured, and the process actually stays disciplined under pressure. The Catalog is especially valuable because it links services, teams, and ownership, so even manual incidents can be routed intelligently instead of depending on tribal knowledge. It also keeps the response close to Slack, which matters because that’s where incident coordination really happens in practice. In short, it helps me run incidents as a repeatable process rather than a series of ad hoc reactions.

**Official Response from Cristina Carnazzo:**

> Catalog is the sleeper best feature, thanks for calling that out! Thanks for taking the time to leave a review, it's so helpful for other teams looking to bring incident.io into their workflow.

  ### 31. incident.io’s Deep Customization Lets Us Tailor Workflows to Our Needs

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Sports | Enterprise (> 1000 emp.)

**Reviewed Date:** July 10, 2026

**What do you like best about incident.io?**

We really like the ability to customize our catalog, settings and workflows to completely meet our organization's needs. While other similar products tend to focus on simple, out of the box solutions, incident.io really allows users more control to curate the set-up to meet their needs

**What do you dislike about incident.io?**

The customer support is great, but feature requests—especially for things we already had with our previous provider (OpsGenie)—move quite slowly, since they seem more focused on ramping up their AI features

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

incident.io is very focused on how to make incidents more meaningful to the business through visibility and insights. This has been really impactful for both technical and non-technical users to consolidate onto one platform

**Official Response from Cristina Carnazzo:**

> Thanks for taking the time to leave a review, and for the feedback on the feature requests, I'll make sure that gets to the right team and if there is anything specific please call it out. Great to hear about visibility and insights from the tool being useful and actionable to the broader business.

Cheers,
Cristina

  ### 32. Powerful Catalog, Smooth UX, and Fantastic Support

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Banking | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 26, 2026

**What do you like best about incident.io?**

The UX of the desktop app and Slack integration makes it easy for new or less experienced users to get up to speed quickly. The Catalog is, by far, the most powerful feature for an Incident Manager and the external integrations are a big help.

Customer support has been fantastic.

Often, when we’re looking to improve our processes or workflows, we find that a solution already exists within the platform. They’re also very receptive to customer feedback when planning feature updates and releases.

**What do you dislike about incident.io?**

The platform’s limitations can be frustrating, especially as it works to catch up in functionality. Some integrations are also limited, although they do seem to be improving gradually over time.

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

Having incident management, on-call schedules, catalog management, and other related tools all in one platform reduces complexity and creates a more well-rounded experience for users.

  ### 33. Super Customizable Incident Management With Great Support

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 24, 2026

**What do you like best about incident.io?**

Super customizable, including automations. The team is constantly innovating and shipping useful new features. Great customer support. It's just a great platform for dealing with incidents - organization, record-keeping, policy enforcement, etc.

**What do you dislike about incident.io?**

There's certainly a learning curve, given how configurable it is. And it's easy to go overboard on the automations and things, making incident channels feel a bit chaotic. But those are both tame-able with some learning.

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

Keeping incident response organized, keeping postmortems organized and easily tied to the incidents that they're for. Super configurable on-call rotation options that let's us create "training" schedules for new joiners.

  ### 34. Streamlined Incident Management with Stellar Support

**Rating:** 5.0/5.0 stars

**Reviewed by:** Gualter A. | Head of Support Engineering, Information Technology and Services, Mid-Market (51-1000 emp.)

**Reviewed Date:** July 30, 2026

**What do you like best about incident.io?**

I use incident.io to manage our incidents at n8n, including customer-facing events, cloud infrastructure, or general Sev 1 tickets. I really like that it makes all teams work under the same structured process with a clear intake incident process. The support is great, very responsive through Slack. The UI and web app are well polished, and their AI features show promising returns.

**What do you dislike about incident.io?**

Nothing to highlight here to be honest

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

I use incident.io to have all teams follow a structured process for managing incidents, ensuring a clear intake process with AI assisted handling and post-mortem generation.

  ### 35. All-in-One Incident Management with Seamless Slack Integration and Top-Notch Support

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Food & Beverages | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 24, 2026

**What do you like best about incident.io?**

As an SRE, incident.io has all they key features needed to manage an incident (tooling, collaboration, post-mortems, followups etc). The UI is rich and the integration across their web-slack-app product set is seamless.
The support they provide is top-notch.

**What do you dislike about incident.io?**

Nothing really. We've had nothing but an amazing experience with them ever since we started using them

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

When we have an incident we need a quick way to declare it, get the right people involved and resolve it ASAP. We struggled with all these in random strange ways, until incident.io came along

  ### 36. Highly Flexible Incident Management with Smart Defaults

**Rating:** 4.5/5.0 stars

**Reviewed by:** Octavio D. | Senior Technical Support Engineer, Enterprise (> 1000 emp.)

**Reviewed Date:** July 09, 2026

**What do you like best about incident.io?**

incident.io is a highly flexible incident management platform, with strong out-of-the-box functionality and lots of sensible default behaviors.

**What do you dislike about incident.io?**

The incident.io Terraform provider needs broader coverage of what can be configured, so we don’t have to rely as much on manual setup and configuration.

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

incident.io has tremendously helped us streamline our incident management process by automating many operations that used to be manual and that previously depended on the operator’s knowledge of SOPs. It has also made it easier for engineering teams to take ownership of the post-incident retrospective exercise, and it helps us generate standard incident metrics.

  ### 37. Deep Customization Made Easy to Navigate

**Rating:** 4.0/5.0 stars

**Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 17, 2026

**What do you like best about incident.io?**

I really appreciate the depth of customization available, and the fact that most of it can be managed through Infrastructure as Code.

The incident experience on Slack is also top-tier.

**What do you dislike about incident.io?**

Setup can feel overwhelming at first, mainly because there are so many settings and customization options available.

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

incident.io automates a fair chunk of our incident response workflow. It takes care of some of the usually tedious parts, like managing rotas, merging multiple alerts into a single incident, and generating reports so we can track our incident rate and how effective our responses are.

**Official Response from Cristina Carnazzo:**

> Thanks so much for taking the time to review us! Great to hear the customization and Infrastructure-as-Code approach are working well, and that the Slack experience is top-tier. I hear you on setup feeling overwhelming with so many options, I'll share that with the team, and let me know if we can help you fine-tune anything. Thanks again for being a customer!

  ### 38. AI-First Incident Management with AI that Actually Saves Time

**Rating:** 5.0/5.0 stars

**Reviewed by:** Alex N. | Member

**Reviewed Date:** December 23, 2025

**What do you like best about incident.io?**

I like that with incident.io, issues are right there in Slack, giving really good visibility into what sort of issues are being submitted and ensuring that people are responding. It structures the response, making sure there's a clear process, ownership, and coordination going into resolving issues. It's super easy and useful to look and see where things are, especially since Slack is where most people spend their workday. Having it all centered there is awesome, and the initial setup was very easy.

**What do you dislike about incident.io?**

I think they should roll out the AI SRE to all customers. Right now, it's just for some of their design partners like Airbnb and Etsy and Zendesk. I would love to see an AGI general intelligence agent that can end-to-end solve incidences and respond, open, and close tickets for everyone. It would probably be light years ahead of the other companies on the market. AI is such a hot topic that it would be great if that was more widely available.

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

I use incident.io for better visibility into customer issues, tracking tickets, and ensuring clear response processes. Integrated into Slack, it enhances coordination and ownership among teams, structuring responses clearly and effectively.

  ### 39. Polished UI and AI-Powered Incident Response That Saves Time

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Internet | Enterprise (> 1000 emp.)

**Reviewed Date:** July 16, 2026

**What do you like best about incident.io?**

The UI is polished and is clear. The @incident Slack bot helps a lot in incidents by taking vague direction and understanding what I need. Scribe for incident calls helps keep teams in sync. The AI generated incident summaries and updates saves a lot of time. Yes, it is the best in the industry.

**What do you dislike about incident.io?**

Sometimes the Scribe misunderstands things, AI written incident summaries occasionally gets things wrong. The Insights functionality is very limited, you have to use their prebuilt modules, there is no way to build custom queries or graphs.

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

The primary problem it solves is tracking and managing incidents in a seamless and easy way. It also aids in incident summary generation, transcribing calls and providing reporting.

  ### 40. Revolutionized Our Incident Management with Ease

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.)

**Reviewed Date:** May 24, 2026

**What do you like best about incident.io?**

I like incident.io for its Catalog, which acts as the source of truth by providing a centralized table for everything in R&D. This dynamic single source of truth is appreciated by various sources. I also appreciate the automated workflows as they allow us to automate tasks like assigning an Escalation Engineer to impactful incidents, enabling better coordination and communication with customers. Additionally, the initial setup was super easy, even easier than expected, which was a pleasant surprise.

**What do you dislike about incident.io?**

Manual statuspage updates, as we didn't migrate our StatusPage to incident.io (we need to gate historical uptime behind login only to customers of ours).

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

I replaced PagerDuty with incident.io to manage scale and complexity, providing a single source of truth and automating incident handling. The Catalog centralizes our R&D info, and workflows automate tasks like assigning an Escalation Engineer to impactful incidents, improving coordination and customer communication.

  ### 41. Solid Incident Management, Great Team Support

**Rating:** 5.0/5.0 stars

**Reviewed by:** Guilherme D. | Co-founder & CTO, Small-Business (50 or fewer emp.)

**Reviewed Date:** July 16, 2026

**What do you like best about incident.io?**

I like incident.io for solving our incident management flows effectively. The team is amazing and easy to deal with. I appreciate the good pricing and how the product solves our issues while evolving with the world. The solution is pretty solid, and the initial setup was super easy and self-serviced.

**What do you dislike about incident.io?**

It's being working well so far, I have no concerns

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

I use incident.io for managing incidents, monitoring, postmortem, and escalation for teams. It solves our incident management flows.

**Official Response from Cristina Carnazzo:**

> Thanks so much for leaving a review! Great to hear incident.io is solving your incident management  and that the team's been great to work with, point of pride for us! Thanks for being a customer

  ### 42. Intuitive Incident Management with Stellar Support

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User | Small-Business (50 or fewer emp.)

**Reviewed Date:** July 06, 2026

**What do you like best about incident.io?**

I find incident.io incredibly intuitive to work with and set up, making the entire process much more straightforward. The sales team is super helpful, which contributes to the intuitive handling of our incidents. The integration with our monitoring stack, tracing platform, and the use of service uptime pages effectively supports our customer needs. The initial setup was extremely easy, and I loved the onboarding checklist.

**What do you dislike about incident.io?**

nothing that I can think of

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

I use incident.io to connect and escalate incidents efficiently, communicate with our customers, and integrate with our monitoring stack. It's incredibly intuitive, making incident management straightforward, and the sales team is very helpful.

  ### 43. Incident Management Tool that just works

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Insurance | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 22, 2026

**What do you like best about incident.io?**

It works so wonderfully well. It's intuitive, and powerful, which really helps incident response and post incident actions flow well.

**What do you dislike about incident.io?**

The reporting is terrible. Most of the time we either ingest the data and do analysis through a 3rd party tool or utilize the MCP to create our own dashboards.

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

Making incident response and post incident actions seamless.

  ### 44. Flexible, Slack-Centric Platform for Modern Workflows

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Computer & Network Security | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 19, 2026

**What do you like best about incident.io?**

I like that it's built around slack and very flexible for modern workflows and processes.

**What do you dislike about incident.io?**

The platform can be a little complex in the beginning and there is a learning curve, but it's more of a testament to how many feature sets there are available so it's a positive thing imo!

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

On call rotations and escalations in our company

  ### 45. Modern, configurable, Ai-Native Incident Management tool

**Rating:** 4.0/5.0 stars

**Reviewed by:** Mihai R. | Engineering Area Lead, Small-Business (50 or fewer emp.)

**Reviewed Date:** July 16, 2026

**What do you like best about incident.io?**

Modern tool that’s highly automated and AI-enabled. It handles incident work well, and there are plenty of configuration options to tailor it to what you need.

**What do you dislike about incident.io?**

It can become too noisy, and it can also end up being misconfigured.

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

Company level incidents, and remediation of problems via post mortems

  ### 46. incident.io: High-Quality Features Backed by a Consistently Supportive Team

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Automotive | Enterprise (> 1000 emp.)

**Reviewed Date:** July 07, 2026

**What do you like best about incident.io?**

We really enjoy working with incident.io, both for the product’s features and overall quality, and for the strong team behind it, who are consistently supportive.

**What do you dislike about incident.io?**

Really minor UX improvements can help to get to a truly excellent product

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

Helping resolve incidents faster. Allowing integrations with multiple products. Improving efficiency with AI summaries

**Official Response from Cristina Carnazzo:**

> Thank you for the review and for the kind words about our team! If you have suggestions for UX improvements we always want to hear them! Cheers, Cristina

  ### 47. Modern Incident Management with Strong Integration, Needs Faster Updates

**Rating:** 3.5/5.0 stars

**Reviewed by:** Verified User | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 09, 2026

**What do you like best about incident.io?**

I appreciate incident.io because it modernizes our incident management tooling and integrates well with third-party tools. I particularly like its customizability with integration on the catalog, which makes it possible to do lookups using the catalog. The initial setup was also pretty easy, which was a plus.

**What do you dislike about incident.io?**

Prioritization of new features and bugfixes is a problem. Depending on your size, customers don't get their feature requests prioritized and bugfixes are slow.

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

Incident.io modernizes incident management, integrates with third-party tools, and offers a customizable catalog integration.

  ### 48. Ease of Use with Great Slack Integration and Embedded Incident Call Links

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 16, 2026

**What do you like best about incident.io?**

Ease of use, the Slack integration and the embedded incident call link

**What do you dislike about incident.io?**

I do not like how seats are assigned to be honest

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

We appreciate the fact that we can create reports about incidents across the business

  ### 49. Easy to Use, Feature-Packed, and Backed by Great Support

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Oil & Energy | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 13, 2026

**What do you like best about incident.io?**

Easy to use, packed with features, great support

**What do you dislike about incident.io?**

Nothing, it does exactly what I want it to

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

It allows me to manage incidents defined by category

  ### 50. AI-Powered Features That Make Work Easier

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.)

**Reviewed Date:** July 20, 2026

**What do you like best about incident.io?**

I like AI-enabled features and a lot of small well-thought things that makes life much easier.

**What do you dislike about incident.io?**

I left feedback on things that could've been more customizable, like custom insights, payroll.

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

it enables us with more automation we previously had starting from Scribe and timeline reconstruction to chatting with @incident to get interesting insights or help to troubleshoot issues


## incident.io Discussions
  - [What do you like most about incident.io for incident management, and what could be improved?](https://www.g2.com/discussions/what-do-you-like-most-about-incident-io-for-incident-management-and-what-could-be-improved) - 1 comment
  - [What is incident.io used for?](https://www.g2.com/discussions/what-is-incident-io-used-for) - 1 comment

- [View incident.io pricing details and edition comparison](https://www.g2.com/products/incident-io/reviews?section=pricing&secure%5Bexpires_at%5D=2026-08-01+10%3A39%3A30+-0500&secure%5Bsession_id%5D=fe9b6347-7efa-4fa9-9217-de84ee059a90&secure%5Btoken%5D=20d75e6d24b338d7d1c82d3f5057fe8ccfc862294c29cd78e1a2d4f700195ae1&format=llm_user)
## incident.io Integrations
  - [Amazon CloudWatch](https://www.g2.com/products/amazon-cloudwatch/reviews)
  - [Backstage](https://www.g2.com/products/backstage/reviews)
  - [Confluence](https://www.g2.com/products/confluence/reviews)
  - [Datadog](https://www.g2.com/products/datadog/reviews)
  - [GitHub](https://www.g2.com/products/github/reviews)
  - [GitLab](https://www.g2.com/products/gitlab/reviews)
  - [Google Workspace](https://www.g2.com/products/google-workspace/reviews)
  - [Grafana Labs](https://www.g2.com/products/grafana-labs/reviews)
  - [IBM Terraform (formerly HashiCorp Terraform)](https://www.g2.com/products/ibm-terraform-formerly-hashicorp-terraform/reviews)
  - [Jira](https://www.g2.com/products/jira/reviews)
  - [Jira Service Management](https://www.g2.com/products/jira-service-management/reviews)
  - [Linear](https://www.g2.com/products/linear/reviews)
  - [Notion](https://www.g2.com/products/notion/reviews)
  - [Personio](https://www.g2.com/products/personio/reviews)
  - [Prometheus](https://www.g2.com/products/prometheus/reviews)
  - [Sentry](https://www.g2.com/products/sentry/reviews)
  - [SE Ranking](https://www.g2.com/products/se-ranking/reviews)
  - [Slack](https://www.g2.com/products/slack/reviews)
  - [Splunk On-Call](https://www.g2.com/products/splunk-on-call/reviews)
  - [VictoriaMetrics](https://www.g2.com/products/victoriametrics/reviews)
  - [Zendesk for Customer Service](https://www.g2.com/products/zendesk-for-customer-service/reviews)
  - [Zoom Workplace](https://www.g2.com/products/zoom-workplace/reviews)

## incident.io Features
**Monitoring**
- Constant Monitoring
- Timely Alerts
- TIcket Accuracy
- AI Monitoring

**Generative AI**
- AI Text Generation

**Reliability Objectives & Service Operations - AI SRE Tools**
- Intelligent On-Call Workflows
- Error Budget Tracking
- SLI & SLO Management
- Service Health Modeling & Reporting

**Management Tools**
- Ticket Assignment
- Standardization
- Lifecycle Visualization

**Agentic AI - IT Alerting**
- Autonomous Task Execution
- Multi-step Planning
- Cross-system Integration
- Adaptive Learning
- Natural Language Interaction
- Proactive Assistance
- Decision Making

**AI Detection & Signal Quality - AI SRE Tools**
- Cross-Telemetry Correlation
- Change-Aware Detection
- Adaptive Anomaly Detection
- Alert Correlation & Noise Reduction

**Generative AI**
- AI Text Generation
- AI Text Summarization

**Investigation & Root Cause Analysis - AI SRE Tools**
- Guided Incident Investigation
- Live Debugging in Production
- AI Root Cause Analysis
- Runtime-Verified Root Cause Analysis

**Agentic AI - Incident Management**
- Autonomous Task Execution
- Multi-step Planning
- Cross-system Integration
- Adaptive Learning
- Natural Language Interaction
- Proactive Assistance
- Decision Making

**Automation & Platform Controls - AI SRE Tools**
- Automated Runbook & Workflow Execution
- Human-in-the-Loop Remediation
- Integration, APIs & Secure Access Controls
- AI-Assisted Code Fix Generation

## Top incident.io Alternatives
  - [PagerDuty](https://www.g2.com/products/pagerduty/reviews) - 4.5/5.0 (948 reviews)
  - [FireHydrant](https://www.g2.com/products/firehydrant-firehydrant/reviews) - 4.5/5.0 (142 reviews)
  - [Rootly](https://www.g2.com/products/rootly/reviews) - 4.8/5.0 (92 reviews)