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.
Streamlined Incident Response
What do you like best about the product?
We've been working with the Incident.io tooling for several months now and it has allowed us to steamline our incident response, freeing up time to dedicate to incident resolution. We've also been able to automate a lot of the manual work we used to have to undertake. The tool is simple to setup, use and has been an easy sell with our business.
The team at Incident.io have been brilliant throughout our onboarding, helping us with all manner of questions around the tooling and best practices.
The team at Incident.io have been brilliant throughout our onboarding, helping us with all manner of questions around the tooling and best practices.
What do you dislike about the product?
There were a few required features missing when we implemented the incident.io tooling (incident types for example), but these have all now been rectified by the team, who were quick to act on requests.
What problems is the product solving and how is that benefiting you?
Sped up and simplified incident response, allowing us to effectively communicate incidents to respective stakeholders.
- Leave a Comment |
- Mark review as helpful
Codifies the manual processes, thus minimising the pain of incident management
What do you like best about the product?
I like how simple it to use the tool is and how it slotted perfectly into our setup.
What do you dislike about the product?
I really can't think of anything that I dislike, their team is proactive in communicating about new features and bug-fixes. It really feels like a tool that is part of the "accepted tooling" for a tech company, alongside Slack, PagerDuty, Sentry, Dead Man's Snitch and others.
What problems is the product solving and how is that benefiting you?
Incident.io takes care of codifying the incident handling process so that the responders can achieve the standards expected by our teams. The tool handholds you just enough to ensure that the mechanical part of the response is covered. Every time.
Elegance under fire
What do you like best about the product?
Managing incidents in the same space our team collaborates provides an elegant mechanism to support comms and alignment. We're reducing recovery times by sharing context in an incident channel, while providing clear and controlled comms to our organisation through the incident.io status pages and integrations. We've worked with incident.io to bring new features and support some of our integrations into our own backend systems to improve our service even further.
What do you dislike about the product?
Incident.io is intrinsically tied into Slack, while this works well for our use case, may be challenging for some organsisations.
The incident.io status pages are only visible to slack account holders (again; good for us to control access), but they've solved this with direct integration to StatusPage and providing API access we've integrated into our other tooling.
The incident.io status pages are only visible to slack account holders (again; good for us to control access), but they've solved this with direct integration to StatusPage and providing API access we've integrated into our other tooling.
What problems is the product solving and how is that benefiting you?
Incident.IO has solved our incident comms and alignment processes by providing unique, easily recognisable places for that conversation to happen and providing just the right level of support to collate the chatter into actionable reporting and feedback. This allows incidents to be recognised, supported, resolved and prevented through the same interfaces we're using for our routine works and empowering our wider team to engage with incident procedures.
Good relationship w/ customer
What do you like best about the product?
I've been working w/ Incident.io in the past 6 months and it could'nt been more grateful w/ their help.
There's no question that they don't take it seriously enough.
There's no question that they don't take it seriously enough.
What do you dislike about the product?
We have past a dificult to renew our plan. It might be the way that incident.io have been seen their international expansion, but the possibilities offered in the medium/long term, seemed to indicate that the type of expansion they are aiming at may not suit the needs that our company will have in the same period.
What problems is the product solving and how is that benefiting you?
Any possibility of customization and automation allows our team to focus on problem-solving and less on the operational activities of the incident process. There is not a month that the product does not offer at least one new solution. It's amazing!
Standardised our incident response and generally a lovely company to work with
What do you like best about the product?
We started using incident.io after deciding we wanted to improve the way we handle incidents and on-call. Up until then, we'd been using flow charts and manual processes for handling that. Turns out there's a better way: incident.io.
Incident has helped us standardise our response for incidents, hooks into all of our important tools such as slack and pagerduty and we know there are more integrations which we've yet to use.
By offloading all the logistics of running an incident.io, our incident managers and the people responding to incidents can do so more effectively and can focus on what they're doing instead of how they need to do it (because incident.io takes care of it).
Lastly, interacting with the team at incident.io is a joy - they're quick to reply to feature requests, how-to requests or general chat. Quite often we've suggested features, for them to be implemented by the end of the day!
Keep up the good work!
Incident has helped us standardise our response for incidents, hooks into all of our important tools such as slack and pagerduty and we know there are more integrations which we've yet to use.
By offloading all the logistics of running an incident.io, our incident managers and the people responding to incidents can do so more effectively and can focus on what they're doing instead of how they need to do it (because incident.io takes care of it).
Lastly, interacting with the team at incident.io is a joy - they're quick to reply to feature requests, how-to requests or general chat. Quite often we've suggested features, for them to be implemented by the end of the day!
Keep up the good work!
What do you dislike about the product?
Honestly can't think of anything. When we started using incident.io the first few messages in the slack channel were quite noisy, but this has been refined a lot.
What problems is the product solving and how is that benefiting you?
- Standardising the response to incidents
- Keeping track of things which need to be done before/during/after incidents
- Simplifying the calculation of on-call pay
- Providing tips and guidance for how to run incidents
- Keeping track of things which need to be done before/during/after incidents
- Simplifying the calculation of on-call pay
- Providing tips and guidance for how to run incidents
Great tool for orchestration of incident management
What do you like best about the product?
We've been using incident.io for nearly a year now and have found it hugely useful for our incident management processes. I would recommend it for any technical organisation using Slack to oversee their incident handling.
What do you dislike about the product?
While I understand that incident.io are focusing on their Slack offering for now, it seems a lot of their offering could be made to be agnostic to the communication tool.
What problems is the product solving and how is that benefiting you?
incident management
Streamlined incident management with incident.io
What do you like best about the product?
Driving the whole incident management from slack
What do you dislike about the product?
A public facing status/incident page will be nice to have. Other than that so far no complaints.
What problems is the product solving and how is that benefiting you?
We are driving our prod incident management via i.io,
Benefits:
1). Tracking follow up tasks.
2). A central place with info/actions taken during an incident.
3). Brought in a structure with few roles on handling incidents.
4). Drive the whole process via slack.
Benefits:
1). Tracking follow up tasks.
2). A central place with info/actions taken during an incident.
3). Brought in a structure with few roles on handling incidents.
4). Drive the whole process via slack.
Best tool for managing incidents through Slack
What do you like best about the product?
We improved our incidents processes a lot as we can do all important actions directly within slack without the need to involve more tools or applications. It helps us to standardize and automate incident processes.
What do you dislike about the product?
With their per-responder licensing model, it is difficult to accurately forecast costs over time. Additional costs may occur while using.
Some features are missing, like posting to private channels or connections to more OnCall Services (Splunk in our case) but these might come over time
Some features are missing, like posting to private channels or connections to more OnCall Services (Splunk in our case) but these might come over time
What problems is the product solving and how is that benefiting you?
We're improving transparency for all stakeholders and employees within the organization while on the same time streamlining incident processes and follow up in a nice and smart way
incident.io has helped us improve and formalise our operational processes
What do you like best about the product?
It's super easy to launch new incidents, and a lot of the incident infrastructure is then taken care of automatically. We've also been impressed with the possibilities of the workflow features. The team is super receptive to feature requests and bug reports. Overall, we've liked how it's helped us start driving a formalisation and overall improvement of our incident management.
What do you dislike about the product?
Some engineers consider the Slack bot noisy, and workflows are not as flexible as we'd like currently.
What problems is the product solving and how is that benefiting you?
We're improving the overall functioning of our operational processes, particularly regarding incident management. We've noticed improvements in the overall quality of incident management, and reduced stress from people in incidents themselves.
Recommendations to others considering the product:
It's a useful tool if you're currently using Slack, and need to improve your overall management of incidents.
Really innovative and responsive company and product! Makes incident work super slick.
What do you like best about the product?
It really helps provide you with a structure to your incidents such that it's easier to coordinate and harder to miss things. The slack channels are a good way to communicate quickly - I like that it's not overcomplicated and not trying to make you communicate in another platform or style, just like a super-charged slack workspace for incidents.
What do you dislike about the product?
Nothing to report that we dislike - you mostly just have to decide for yourselves how you want to use it and customise appropriately, which needs love and attention to get the best out of all the features!
What problems is the product solving and how is that benefiting you?
In particular for us as a business, we're regulated by a central organisation and so incident.io is helping us really formalise and prove that our processes are strong and reliable, as well as modern and slick.
showing 131 - 140