Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
178 reviews
from
External reviews are not included in the AWS star rating for the product.
Great Chatops incident response tool
What do you like best about the product?
incident.io is a game-changer for incident response. Its seamless ChatOps integration makes managing incidents fast, collaborative, and intuitive—right from Slack. The platform is packed with powerful features like automated timelines, role assignments, and customizable workflows, giving teams the flexibility to handle any kind of issue efficiently. It’s clear that incident.io was built with real-world operations in mind. Highly recommend it for any team serious about improving their incident management.
What do you dislike about the product?
With so many features available, it can sometimes be a bit tricky to find the exact option you’re looking for in the interface.
What problems is the product solving and how is that benefiting you?
incident.io streamlines the entire incident response process, making it smooth, consistent, and easy to manage—especially during high-pressure situations. It eliminates the chaos of coordinating across tools by centralizing everything in Slack, from declaring incidents to assigning roles and tracking actions. The automated reporting and timelines save tons of time and ensure post-incident reviews are thorough and accurate. Overall, it helps our team stay focused, aligned, and faster in resolving issues.
Suitable for small and large engineering teams
What do you like best about the product?
The onboarding experience was outstanding — we have a small engineering team (~15 people) and the integration with our existing tools (Linear, Google, New Relic, Notion) was seamless and fast less than 20 days to rollout. The user experience is polished and intuitive, which made internal adoption frictionless.
I also led the rollout for a larger organization (200+ people), and we were able to fully implement incident.io across multiple teams in just 45 days. The structured workflows and Slack-native approach made it easy to scale incident response without overwhelming the teams.
I also led the rollout for a larger organization (200+ people), and we were able to fully implement incident.io across multiple teams in just 45 days. The structured workflows and Slack-native approach made it easy to scale incident response without overwhelming the teams.
What do you dislike about the product?
The Scribe feature doesn't support languages other than English yet — this is something I was really looking forward to using, and it's currently a blocker for broader adoption in non-English-speaking teams.
Additionally, the volume of messages posted by the Slack app can sometimes clutter the channel, making it harder for observers to follow the core of the incident. It would also be helpful if threads created by workflows could be automatically pinned — this feels like a small UX improvement that could have a big impact on visibility.
Additionally, the volume of messages posted by the Slack app can sometimes clutter the channel, making it harder for observers to follow the core of the incident. It would also be helpful if threads created by workflows could be automatically pinned — this feels like a small UX improvement that could have a big impact on visibility.
What problems is the product solving and how is that benefiting you?
incident.io helped us scale our incident response process with minimal overhead. Before adopting it, incident coordination was inconsistent, manual, and hard to follow — especially for stakeholders outside engineering.
Now, incidents are handled in a structured, predictable way. Roles and responsibilities are clear, follow-ups are easier to track, and communication is significantly improved. Teams like Product, CX, and Finance can now easily understand what’s happening during an incident without needing to ask around or dig through Slack.
The biggest benefits have been faster response, better collaboration across functions, and more confidence in our ability to manage critical situations as we scale.
Now, incidents are handled in a structured, predictable way. Roles and responsibilities are clear, follow-ups are easier to track, and communication is significantly improved. Teams like Product, CX, and Finance can now easily understand what’s happening during an incident without needing to ask around or dig through Slack.
The biggest benefits have been faster response, better collaboration across functions, and more confidence in our ability to manage critical situations as we scale.
Fantastic incident management tool
What do you like best about the product?
Customization, integration with Teams, ease-of-use
What do you dislike about the product?
Teams integration has less features than Slack one.
What problems is the product solving and how is that benefiting you?
Having a structured and scalable incident response process.
I have been using incident.io for a couples of weeks now and it is easy and powerful
What do you like best about the product?
Incident.io is easy to use and very intuitive. The command tool to handle incidents through Slack is great. Also, having alerts such as phone calls, SMS, and emails, along with a management tool for incidents and post-incident reports in a single app, is extremely useful.
What do you dislike about the product?
Assigning an incident leader requires extensive configuration; it should be simpler to assign the on-call person.
What problems is the product solving and how is that benefiting you?
We had separate tools for receiving alerts and manage incidents, that's the problem incident.io is solving primarily for us, now by using it, we can have all in a single app.
Simple, fast, customizable
What do you like best about the product?
Slack integration and guided process is so great and customizable, so easy to onborad new responders.
What do you dislike about the product?
Some good features requireement the top tier plan
What problems is the product solving and how is that benefiting you?
Guided workflow during incident management and post-incident really helps onbording anyone in this really rapidly, very customizable. Helps focus on solving incidents without forgeting/missing important side-tasks or information gathering.
Fantastic Product
What do you like best about the product?
Too many to list - it's a one stop shop for incident management (not just on call rotations like many competitors. Built in and custom automations, great slack integration, automated post mortem generation, jira ticket creation, followup and actions creation, post incident workflows. It takes all the pain out of incident management and lets you focus on working the incident itself.
What do you dislike about the product?
I can't think of anything that's worth mentioning.
What problems is the product solving and how is that benefiting you?
incident management and on call
Flexible solution for handling incidents across teams
What do you like best about the product?
Incident.io is incredibly flexible and integrates smoothly with the tools we rely on. It makes it easy to collaborate at key moments, which helps us maintain SLAs and fix things quickly. Workflows, notifications, and forms are highly customizable, making incident.io a key tool across different areas of our business.
What do you dislike about the product?
I don't dislike anything, Incident.io covers the bases I need and is easy to set up and work with.
What problems is the product solving and how is that benefiting you?
Alerting on call teams of an incident, facillitating cross functional communcation, and tracking progress through resolution.
Makes Incident Management a breeze
What do you like best about the product?
Huge fan of the usability of the Slack commands and how it's helped us improve our incident management workflows. The AI features really reduce the friction of incident management. Also the Customer support has been fantastic. It's easy to set up, and easy to integrate with our existing tooling/platform. Wish my company had more incidents so I could play with the features more. Also love the built-in Statuspages
What do you dislike about the product?
There have been a few UI bugs, but the support team has been prompt to respond to feedback and help us resolve or work around them.
What problems is the product solving and how is that benefiting you?
Solves the problem of how to make incidents easy to report, how to coordinate the resolution of incidents, and how to handle communication of the incident with internal and external stakeholders
Intuitive, fast and embedded where people are anyway (Slack)
What do you like best about the product?
To me incident.io strikes just the right balance between not getting in the way while still providing structure, process and data gathering to incident management.
I deal with incidents both as lead, supporter or just observer multiple times a week and during incidents things need to go fast and I like that I can launch and manage incidents right from Slack via shortcuts without having to keep some other tab open and switching back and forth.
It's great that numbers like the frequency of incidents and MTTX metrics are available out of the both and visualised in nice-looking dashboards.
I deal with incidents both as lead, supporter or just observer multiple times a week and during incidents things need to go fast and I like that I can launch and manage incidents right from Slack via shortcuts without having to keep some other tab open and switching back and forth.
It's great that numbers like the frequency of incidents and MTTX metrics are available out of the both and visualised in nice-looking dashboards.
What do you dislike about the product?
No complaints about the core use-case. Creating overrides for escalation scheuldes could be easier (just by drag and drop on the timeline or by making the text input a little smarter - it doesn't seem to be able to identify people just by their first name.)
What problems is the product solving and how is that benefiting you?
Providing structure while not getting in the way during time-sensitive incidents.
Elegant, innovative and adaptive - what a gem of a product (and company)
What do you like best about the product?
The intuitive design, overall ease of use and stellar customer relationship experience has made me an avid fan of this product (and company)
While most companies these days are boasting about their use of AI, incident.io to me stands out about how deliberately they use AI. The suggested follow up actions and suggested incident summaries based on the context gathered in the incident channel are spot on most of the times and the way these are surfaced to the user to either accept, modify or decline is absolutely seamless.
As mentioned by many others, the customer experience has been beyond anything I've seen in enterprise software. Issues are incredibly easy to raise and are responded to and sometimes even fixed within hours. Even feedback on existing features or suggestions for new ones are acknowledged, discussed, catalogued and also diligently followed up on once a suggestion has been released.
While most companies these days are boasting about their use of AI, incident.io to me stands out about how deliberately they use AI. The suggested follow up actions and suggested incident summaries based on the context gathered in the incident channel are spot on most of the times and the way these are surfaced to the user to either accept, modify or decline is absolutely seamless.
As mentioned by many others, the customer experience has been beyond anything I've seen in enterprise software. Issues are incredibly easy to raise and are responded to and sometimes even fixed within hours. Even feedback on existing features or suggestions for new ones are acknowledged, discussed, catalogued and also diligently followed up on once a suggestion has been released.
What do you dislike about the product?
As much as the team is very open and responsive to questions or ideas about the product roadmap, a more structured overview on what features to expect when would be nice (bonus points if customers would even get a chance to vote on roadmap priorities)
The setup/configuration of escalation paths can be a bit confusing (e.g. the differences between working hours of a paths vs. notification urgency vs. schedule)
The UI of the web dashboard changes quite frequently - some (more) tool tips on first visit would be nice to explain what has changed
I'd like some more configuration options for some features - e.g. I'd love to opt out of using the "Pause an incident" feature and would like to choose to only post a final call summary but not continously post call updates
Maintentance announcements on internal status pages - pretty please?
The setup/configuration of escalation paths can be a bit confusing (e.g. the differences between working hours of a paths vs. notification urgency vs. schedule)
The UI of the web dashboard changes quite frequently - some (more) tool tips on first visit would be nice to explain what has changed
I'd like some more configuration options for some features - e.g. I'd love to opt out of using the "Pause an incident" feature and would like to choose to only post a final call summary but not continously post call updates
Maintentance announcements on internal status pages - pretty please?
What problems is the product solving and how is that benefiting you?
It removes most of the overhead that is holding people back to create "proper" incidents, which lowers the barrier and in turn increases visibility on the true amount and types of incidents that do occur but were previously not captured anywhere.
showing 1 - 10