Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Great product, great customer support
What do you like best about the product?
Our team uses incident.io's status page feature for incidents and scheduled maintenance. The product "just works" -- it has pretty much everything we need and nothing we don't. The product team clearly worked with users to identify the key features. I appreciate its simplicity.
The customer support team is hyper responsive and has even shipped some requests that we submitted to improve the product.
The customer support team is hyper responsive and has even shipped some requests that we submitted to improve the product.
What do you dislike about the product?
I don't have anything I dislike about the product.
What problems is the product solving and how is that benefiting you?
- Internal incident management
- Communicating our API health via status page.
- Communicating our API health via status page.
- Leave a Comment |
- Mark review as helpful
Super App: No Stress during an Incident
What do you like best about the product?
Incident.io is a super app that you can easily set up, use and integrate with other 3rd party applications to ensure relevant stakeholders are notified to resolve any unplanned activity.
At no time will you need customer support, but at the same time they are always available to assist. Not to forget the features available i.e. classifying incidents per severity, incident lead, brief description space ensuring efficient incident management and readiness anytime
At no time will you need customer support, but at the same time they are always available to assist. Not to forget the features available i.e. classifying incidents per severity, incident lead, brief description space ensuring efficient incident management and readiness anytime
What do you dislike about the product?
The fact that it has not yet inculcated any AI feature to help in summarizing and preparing the incident, learnings and post-incident activities.
What problems is the product solving and how is that benefiting you?
The incident.io app enabled the organization to stay ready at any time to manage, support and resolve customers whenever an incident occurred.
Further, we were able to perform retrospective reports and tweak rules and incident policy to match business and stakeholder needs.
Further, we were able to perform retrospective reports and tweak rules and incident policy to match business and stakeholder needs.
Easy to use tool that meets your team in Slack instead of adding another tool
What do you like best about the product?
We kept trying to implement Incident Response processes but couldn't get people to leave Slack to use a new tool. Incident.io lets us build a dynamic and powerful IR process in Slack which out team is already familiar with.
What do you dislike about the product?
Their intro plan can be a little limited with only a few integrations and automations available by default.
What problems is the product solving and how is that benefiting you?
Helps everyone in the company including non-techincal folks to report incidents and remain aware of what's going on. In a small startup keeping track of the little fires can be immesely helpful and this helps keep discussions for each incident organized with easy to use postmortem tools.
A great platform that simultaneously empowers and simplifies incident response
What do you like best about the product?
incident.io has drastically reduced the additional cognitive load on stakeholders involved in the Incident Response lifecycle in our company. It has great usability that removes operational tasks of organization, documentation and structuring from the path that make us focus almost 100% of our effort on tasks that will actually contribute to mitigating and, subsequently, resolving that incident.
Another advantage is the tools it provides us with to also improve the pre- and post-incident cycle based on data and enforced routines.
The effort to integrate incident.io with our main tools, in addition to the necessary setups in the tool itself, were practically nil. Really very easy to operate and configure.
Additionally, the customer service team has been incredibly responsive and helpful. The resolution time for the few problems we had was extremely quick, in addition to all the attention they gave to exposing our needs, some of which were incorporated into the platform within a few months/weeks.
In a very short time, incident.io became an essential tool in the day-to-day life of our engineering team, with smooth adoption and without generating much friction or learning overhead.
Another advantage is the tools it provides us with to also improve the pre- and post-incident cycle based on data and enforced routines.
The effort to integrate incident.io with our main tools, in addition to the necessary setups in the tool itself, were practically nil. Really very easy to operate and configure.
Additionally, the customer service team has been incredibly responsive and helpful. The resolution time for the few problems we had was extremely quick, in addition to all the attention they gave to exposing our needs, some of which were incorporated into the platform within a few months/weeks.
In a very short time, incident.io became an essential tool in the day-to-day life of our engineering team, with smooth adoption and without generating much friction or learning overhead.
What do you dislike about the product?
I believe there are some things that could be more configurable, such as the types of events that should become messages in the incident feed on the slack channel. Sometimes the feed becomes excessively polluted. But this is a minor issue, nothing that really interferes with our day-to-day work.
What problems is the product solving and how is that benefiting you?
We are a SaaS and we are focused on reducing Mitigation Time for high/mid severity incidents, in addition to better mapping low severity incidents in order to prevent them from happening recurrently and preventing the expansion of their impacts on our customers and the productivity of our product/engineering team.
The tool helps us focus on what really needs to be done to mitigate and resolve the issues that are happening during the incident. We can, for example, dump information and then reorganize or filter it more carefully. Furthermore, structuring communication allows more people to participate more effectively, without the need to interrupt the response flow at all times to understand what is happening and the current state of response.
For the post-incident flow, all the data analysis tools, in addition to the learning flows themselves that generate greater enrichment of incident data, are things that have helped us a lot to understand where our main problems are and how to attack them. .
The tool helps us focus on what really needs to be done to mitigate and resolve the issues that are happening during the incident. We can, for example, dump information and then reorganize or filter it more carefully. Furthermore, structuring communication allows more people to participate more effectively, without the need to interrupt the response flow at all times to understand what is happening and the current state of response.
For the post-incident flow, all the data analysis tools, in addition to the learning flows themselves that generate greater enrichment of incident data, are things that have helped us a lot to understand where our main problems are and how to attack them. .
Solid experience, easy to set up
What do you like best about the product?
Incident.io was easy to install and configure. It's already helped us do a better job of responding to minor incidents that previously were handled informally and not as well documented.
We've already had some nice interactions with their customer success team and engineers with some minor feature requests that got added quickly.
We've already had some nice interactions with their customer success team and engineers with some minor feature requests that got added quickly.
What do you dislike about the product?
We're not using Incident.io's status pages yet for external reporting because they don't have status page integration with outside services in the same way that statuspage.io does.
What problems is the product solving and how is that benefiting you?
Incident.io helps us ticket incidents, pull discussion into one place, coordinate outside response, and collect evidence for later post-mortems. It does everything we need an incident management tool to do.
Gentle guidance through incident processes
What do you like best about the product?
- Automating actions we were doing manually (creating the slack channel, adding bookmarks and buttons, list of things to do in the learning flow etc.)
- Gentle nudges towards the right path, which can be quite easily customized to fit our needs.
- The way of sharing updates - if you're not part of the incident, you can just check the main announcement and thread with individual updates to know what's going on, no need to read through the whole incident channel.
- You don't have to leave slack to run the incident. The commands are straightforward and quite intuitive, but you can also use buttons to navigate it.
- The AI assistance with updating summary is splendid, I'm looking forward to more customization options there and also when generating postmortems.
- Having a shared slack channel with incident.io where release notes are posted and we where we can raise questions and bug reports. Great customer support!
- Gentle nudges towards the right path, which can be quite easily customized to fit our needs.
- The way of sharing updates - if you're not part of the incident, you can just check the main announcement and thread with individual updates to know what's going on, no need to read through the whole incident channel.
- You don't have to leave slack to run the incident. The commands are straightforward and quite intuitive, but you can also use buttons to navigate it.
- The AI assistance with updating summary is splendid, I'm looking forward to more customization options there and also when generating postmortems.
- Having a shared slack channel with incident.io where release notes are posted and we where we can raise questions and bug reports. Great customer support!
What do you dislike about the product?
- Encountering minor bugs quite frequently. It is expected when moving fast that some things will break and mostly it is just annoying stuff like formatting.
- When followups are exported to jira, they can't have an assignee
-As opposed to having an option to merge incidents, sometimes it could be helpful to split one incident into two (you discover multiple separate issues, but already have information in the channel). Not exactly a dislike of incident.io, but rather wishful thinking to have some way of splitting these complex scenarios into smaller parts that can be addressed separately. Perhaps some kind of grouping functionality for actions and followups?
- I would like more options to nudge the users that they should complete some manual step (mark action as completed, send a notfication when the learning flow is not moving forward for a few days etc.)
- When followups are exported to jira, they can't have an assignee
-As opposed to having an option to merge incidents, sometimes it could be helpful to split one incident into two (you discover multiple separate issues, but already have information in the channel). Not exactly a dislike of incident.io, but rather wishful thinking to have some way of splitting these complex scenarios into smaller parts that can be addressed separately. Perhaps some kind of grouping functionality for actions and followups?
- I would like more options to nudge the users that they should complete some manual step (mark action as completed, send a notfication when the learning flow is not moving forward for a few days etc.)
What problems is the product solving and how is that benefiting you?
Guiding people through the incident lifecycle, making sure that internal and external updates are shared in a timely fashion and we actually identify ways how to learn from the incidents.
Crucial piece of your incident management
What do you like best about the product?
Incident.io is extremely easy to use. The platform is easy to set up and integrates well with several tools. Making it a critical part of our incident handling and communication process. It helps both during an incident and the post-incident/post-mortem process by allowing users with little training to manage incidents like pros.
What do you dislike about the product?
Some of the best features are in the pro plan, and the price discrepancy between the basic and the pro can be daunting. Especially since incident.io doesn't handle alerting, you need to rely on a separate platform to manage alerts.
What problems is the product solving and how is that benefiting you?
It simplifies the collaboration and communication process during an incident. Ensuring all needed parties are well informed about an incident and the necessary follow-up work is handled appropriately.
Invaluable to share information of incidents in the organization
What do you like best about the product?
An easy and well thought out way to handle incidents and share information and status updates with minimal overhead.
We use Slack in the organization as the primary information channel, and the Slack integration performs flawless and makes it possible to interface with incident.io primarly using Slack.
I'm also very fond of the statistics found in incident.io.
I'm expected to be able to document historical incidents, and I can find what I need in the tool.
We use Slack in the organization as the primary information channel, and the Slack integration performs flawless and makes it possible to interface with incident.io primarly using Slack.
I'm also very fond of the statistics found in incident.io.
I'm expected to be able to document historical incidents, and I can find what I need in the tool.
What do you dislike about the product?
There is really nothing to actually dislike about incident.io
What problems is the product solving and how is that benefiting you?
Sharing, documenting and handling incidents in a structured manner
Makes it easy to handle incidents the right way
What do you like best about the product?
The Slack integration is excellent, one of the best integrations I've seen. Out-of-the-box workflows are excellent, and it makes it easy for engineers to onboard into the tool.
What do you dislike about the product?
We have too many tools for managing incidents and system status overall, and we'd prefer much stronger integrations with other tools (like Pagerduty, Datadog, etc) or more functionality in one place.
What problems is the product solving and how is that benefiting you?
Improving our organizational incident response, reducing MTTA and MTTR
Not just for big teams!
What do you like best about the product?
In the past our incident process was very manual and haphazard. Incident.io has automated all the parts like creating a Slack channel, ensuring the right people are there, and nudging responders to provide timely status updates.
It also provides a common interface, available to all, for updating the incident status.
As a small 30-person company, I wasn't sure we needed a tool to manage an occasional process like incidents but it has been helped to make incidents a whole-company activity. For example, our marketing dept would be aware of an ongoing incident and could pause a campaign until it was resolved; and our support team is kept in the loop about resolutions.
It also provides a common interface, available to all, for updating the incident status.
As a small 30-person company, I wasn't sure we needed a tool to manage an occasional process like incidents but it has been helped to make incidents a whole-company activity. For example, our marketing dept would be aware of an ongoing incident and could pause a campaign until it was resolved; and our support team is kept in the loop about resolutions.
What do you dislike about the product?
As, primarily, a Slack app it's somewhat limited by the Slack UI and this can lead to less-than-ideal UX.
The pricing also jumps up tremendously if you need more than 2 integrations or a few workflows. I tend to find we don't use the product as much as we could because of the price jump.
The pricing also jumps up tremendously if you need more than 2 integrations or a few workflows. I tend to find we don't use the product as much as we could because of the price jump.
What problems is the product solving and how is that benefiting you?
Incident.io provides a place for us to gather the right people, communicate the incident status, and reflect afterwards on lessons we can learn
showing 21 - 30