incident.io
incident.ioExternal reviews
179 reviews
from
External reviews are not included in the AWS star rating for the product.
Simplifying the life of incident responders
What do you like best about the product?
The separation of functionality between Slack and the website is extremely powerful. This gives us the ability to have rich reporting and compliance controls in place without cluttering the experience and the workflow for the incident responders working to solve the incident during the live phase. All essential tasks during the incident live phase can be handled or initiated inside Slack. When we move to the post-incident analysis and learning phase, there is a mix of web and slack interfaces.
The idea of having actions during the incidents as a concept that is different from the follow-up actions to consider after the incident.
Status pages (internal and external) are integrated and make it a lot easier to keep the various stakeholders (including customers) informed.
The idea of having actions during the incidents as a concept that is different from the follow-up actions to consider after the incident.
Status pages (internal and external) are integrated and make it a lot easier to keep the various stakeholders (including customers) informed.
What do you dislike about the product?
There is not much to dislike. It is not a static experience. If you are unhappy, let Incident.io support staff know. Most of our comments on features have been responded to by changes to the product, config changes, or different ways of doing it.
What problems is the product solving and how is that benefiting you?
Incident.io has helped us focus more on how we want to conduct the incident response and follow-up and spend less time on implementing homegrown tools in an ad-hoc fashion.
Bringing a complete tool to our incident process allows us to clarify roles, and processes and put the effort into the things that improve the experience for both incident responders and customers.
We have become more professional in the way we handle and communicate during incidents without having to invest a lot of man-hours to make it happen.
The collaboration with our account manager from incident.io and their support team has also helped us democratize the contribution to and improvement of the incident process. Improving the incident process is no longer limited to only the Java programmers who can tweak our homegrown tool. Now, everybody that can state their case in meetings or Slack conversation with support can describe the improvements they would like to see, and have feedback and possibly a fix. We see a lot more engagement and ideas now than compared to when we were building a tool ourselves.
Bringing a complete tool to our incident process allows us to clarify roles, and processes and put the effort into the things that improve the experience for both incident responders and customers.
We have become more professional in the way we handle and communicate during incidents without having to invest a lot of man-hours to make it happen.
The collaboration with our account manager from incident.io and their support team has also helped us democratize the contribution to and improvement of the incident process. Improving the incident process is no longer limited to only the Java programmers who can tweak our homegrown tool. Now, everybody that can state their case in meetings or Slack conversation with support can describe the improvements they would like to see, and have feedback and possibly a fix. We see a lot more engagement and ideas now than compared to when we were building a tool ourselves.
Review of Incident.io
What do you like best about the product?
Very helpful with tracking incidents and keeping incidents up to date, as well as good place to communicate with team members.
What do you dislike about the product?
Very low integration limit when starting with smaller plan.
What problems is the product solving and how is that benefiting you?
Incident.io helps solve communication problems, when there are incidents that come up, we can resolve them together as a team and assist others when brought into the incidents.
Putting Structure around Incident Management
What do you like best about the product?
Incident.io stands out to us as a tool which seamless integrates into our internal communication tool of choice - Slack. This means there is no steep learning curve or change of process required for us to adopt Incident.io. In a matter of days, we were familiar with how to raise incidents through the tool.
The customer success and product teams are extremely responsive and receptive to feedback.
The customer success and product teams are extremely responsive and receptive to feedback.
What do you dislike about the product?
There's not much I dislike really. The metrics through the status page could be a little more flexible to avoid the need to manually export the incidents and manipulate the data.
What problems is the product solving and how is that benefiting you?
Incident.io has allowed us to provide a framework for incident management which is easy for anyone to pick up and follow. It allows us to efficiently get incidents raised automatically and resolved quickly, reducing customer impact.
Flexible status page for support teams
What do you like best about the product?
- Great how you can set up multiple status pages - Tessian have one per region (something others don’t allow and make it much more relevant for your customers)
- You can break it down by components and customise to make it reflect the different products / modules, again so it makes the most sense to your customers
- The ability to subscribe to updates via channel of customers choice
- Love the UI
- How quick and easy it was to set up
- You can break it down by components and customise to make it reflect the different products / modules, again so it makes the most sense to your customers
- The ability to subscribe to updates via channel of customers choice
- Love the UI
- How quick and easy it was to set up
What do you dislike about the product?
- No slack update option for subscriptions
What problems is the product solving and how is that benefiting you?
I run a global support team so the ability to let our customers know the status of our product at any time is critical. Incident.io's status page provides me a quick interface to inform many customers in real time.
Great tooling for tracking incidents!
What do you like best about the product?
It quickly logs everything you do, in chronilogical order and makes the post-incident activies clear and easy to go about!
What do you dislike about the product?
it can alert you quite often! but its a good thing, make sure you give updates regularly
What problems is the product solving and how is that benefiting you?
getting the right people into the call, and adverttising to the rest of the company what is happening
Developer-friendly incident management, fully integrated into slack
What do you like best about the product?
I would really highlight the customer-centricity of the team working in incident.io. Feedback is always heard and has lead to product improvements - with a very short delivery cycle.
The quality on the execution on the idea is usually quite polished and has a developer-friendly orientation.
In general the feature it has fit 1:1 with the needs that an engineering org migh have:
- automation on incidents - making the incident management programmatic
- communication across channels - either SMS, mail and primarily slack
- flexibility on rules and categories, as well as internal fields
- 1-click post-mortem reports - this is a killer feature, time saving, that helps a lot to have relevant conversations around incidents (instead of spending time curating a timeline)
the way that the slack application is setup saves time during an incident and guides quite well on its handling.
The quality on the execution on the idea is usually quite polished and has a developer-friendly orientation.
In general the feature it has fit 1:1 with the needs that an engineering org migh have:
- automation on incidents - making the incident management programmatic
- communication across channels - either SMS, mail and primarily slack
- flexibility on rules and categories, as well as internal fields
- 1-click post-mortem reports - this is a killer feature, time saving, that helps a lot to have relevant conversations around incidents (instead of spending time curating a timeline)
the way that the slack application is setup saves time during an incident and guides quite well on its handling.
What do you dislike about the product?
As suited as it's for developers - it can lack sometimes API's to integrate across systems.
The developer-first mindset might make it also a bit less intuitive to adopt for non-engineering teams - but practicing helps a lot on visualizing how it's used.
The developer-first mindset might make it also a bit less intuitive to adopt for non-engineering teams - but practicing helps a lot on visualizing how it's used.
What problems is the product solving and how is that benefiting you?
- communication across departments
- transparency on systems status - both internally and externally
- standardization of incident management with a programmatic tool
- transparency on systems status - both internally and externally
- standardization of incident management with a programmatic tool
A joy to use
What do you like best about the product?
I'm constantly presently surprised by its behaviors, its integrations just work, and the process makes a lot of sense. On top of that, it's fast and makes the administrative side of incidents a breeze.
What do you dislike about the product?
I'd love to see them get into alerting and escalations. I'm not sure they need to be the complete solution to everything, but their finesse to integrations could only improve the market.
What problems is the product solving and how is that benefiting you?
We use Incident.io to drive our incident response process, handle follow up items and communicate with other teams and the company.
Simplifying Incident Management and Communication
What do you like best about the product?
Incident.io stands out as a valuable tool for automating incident management and communication, with its effective Slack bot integration leading the way. The platform's compatibility with multiple external tools, such as Ops Genie, makes it an excellent central hub for managing incidents.
Another handy feature is its ability to automate routine actions, such as postmortem reports generation. This automation can significantly reduce the time spent on manual, repetitive tasks, reusing the incident communication channel on Slack as a basis for the postmortems summary.
Another handy feature is its ability to automate routine actions, such as postmortem reports generation. This automation can significantly reduce the time spent on manual, repetitive tasks, reusing the incident communication channel on Slack as a basis for the postmortems summary.
What do you dislike about the product?
To get the most out of Incident.io, teams might have to rethink their usual processes and be open to changing how they handle things.
What problems is the product solving and how is that benefiting you?
Streamlining the incident management process allows team members to focus on more important tasks, rather than spending time managing the process itself.
Wonderful UX and Potential for the Future
What do you like best about the product?
Incident.io has a seamless UX. The styles on the site all look polished. Their responsiveness to adding features and fixing bugs when onboarding was wonderful to have. The patterns they've laid out are heading in a great direction and will allow them for future successes.
What do you dislike about the product?
Administration needs a bit of improvement. Terraform support is still new, but lacking in a few regards. The difference in data between what is exposed in the UI and what is available in the API makes customizing and measuring different aspects of the IM lifecycle quite tedious.
What problems is the product solving and how is that benefiting you?
The Incident Management UX was a large challenge for us. Incident.io has improved that by allowing the right amount of customizability and sane defaults that encourage users to use the product properly.
Clean and intuitive UX, great integrations, outstanding customer support
What do you like best about the product?
Clean user experience. Focus on integrations (slack, notion, pagerduty, datadog is coming soon). A great product team that listens to customers and adjusts their roadmap to meet customers where they're at. Finally, the customer success team has been very responsive and helpful.
What do you dislike about the product?
More customizable insights around incident management and an ability to drill down for incidents would be helpful.
What problems is the product solving and how is that benefiting you?
- Incident Management workflow automation
- Incident insights & trends
- Incident insights & trends
showing 21 - 30