It was so easy to set up. We got our entire engineering team onboarded to an on-call schedule in a single day! Review collected by and hosted on G2.com.

I can't say there's anything that jumped out as negative. Review collected by and hosted on G2.com.

Rootly makes incident management simple and efficient. I really like how easy it is to integrate with existing tools like Slack, Jira, and PagerDuty. The automated workflows save a lot of manual overhead and ensure our team follows consistent processes during incidents. The interface is clean, and setup was straightforward, even for a relatively small IT team like ours. Review collected by and hosted on G2.com.

Occasionally, some of the deeper customizations require a bit of trial and error, and documentation can be improved in a few places. It’s not a blocker, but more real-world examples for advanced workflows would help us unlock even more value quickly. Review collected by and hosted on G2.com.

Very easy to use and responsive, connects with Slack Review collected by and hosted on G2.com.

Often nagging behavior and inability to understand certain tasks - templates would make this better Review collected by and hosted on G2.com.

It was a breath of fresh air using Rootly having moved from one of their competitors where we weren't able to get the solution fully working (who also charged us for "premium" support!).

Rootly is easy to set-up with support included in a straightforward no-nonsense affordable subscription plan. Furthermore, feedback/suggestions we had were taken seriously and as a result they've now improved the platform not only for us but all their other customers. Review collected by and hosted on G2.com.

We have no issues so far, Rootly just works with minimal admin. Review collected by and hosted on G2.com.

Rootly is an exceptional incident management platform that helps teams resolve issues faster and more effectively. Its seamless Slack integration and automated workflows make incident response feel effortless and organized. It's clearly been built with performant engineering teams in mind. Review collected by and hosted on G2.com.

The only downside is that Rootly can feel a bit complex to set up initially, especially for smaller teams without dedicated DevOps resources. Review collected by and hosted on G2.com.

Rootly makes incident management much easier by integrating right into Slack and automating a lot of the busy work and enables unique processes for each type of incident. It keeps everything organized, enforces a consistent process, and saves a ton of manual effort. The customizable playbooks and integrations with tools like PagerDuty, Jira, and confluence are super helpful for fitting into different team workflows. AI based incident summarization/RCA drafting in slack is also really neat feature for incident management at scale.

Rootly's customer support as well as initial onboarding experience was very good. Review collected by and hosted on G2.com.

One downside of Rootly is that the UI can feel a bit clunky at times, especially when navigating through incidents or setting up custom workflows. Some workflows take a bit of trial and error to get right, and certain integrations could be smoother. Also, while automation is great, there are times when it feels like there are too many notifications or updates in Slack, but overall the slack nagging gets people to action on things. Review collected by and hosted on G2.com.

We love using Rootly for incident management! The Slack integration makes real-time collaboration effortless, and the automated runbooks, along with Jira and PagerDuty integrations, have streamlined our workflow. Review collected by and hosted on G2.com.

No major downsides—occasional minor UI improvements would be nice, but the team iterates quickly! Review collected by and hosted on G2.com.

Rootly is incredibly easy to use and configure, allowing us to streamline our entire incident management process. One of the standout features is the ability to create automated workflows, which saves a lot of time and ensures that key steps in the incident process are handled efficiently. For example, setting up automated reminders for SLA breaches or post-incident reviews is simple, and it keeps the team on track without manual intervention. The seamless integration with applications like Slack is another major benefit. We can manage almost the entire incident management process directly from Slack, from initiating incidents to updating timelines and coordinating with the team. This integration significantly improves communication and speeds up the resolution process. Review collected by and hosted on G2.com.

The main area for improvement is in the 'metrics' side of the application. Currently, there are some limitations around filters in certain panel options, which makes it harder to return the exact data we need for how we use the application. For example, it would be helpful if the graphs created within the metrics were more interactive. Ideally, users should be able to click on a specific data point, like the number of incidents between certain dates, and be taken directly to the relevant incident results. Improving this functionality would make Rootly even more effective in managing and analysing incident data. Review collected by and hosted on G2.com.

There is a lot of positives to talk about with Rootly, but by far the biggest draw for me was the flexibility of the product.

Many products out there are very opinionated - they expect your Incident Management flow to follow the flow and process that THEY define.

Rootly can give you an out-of-the-box template and opinions, but it also lets you customise almost everything to your organisation. From forms and fields, workflows, integrations, it's all there to be as flexible as possible.

Another huge plus is quite simply the people working on Rootly - not only are they great to work with, but have been extremely receptive to feedback and feature requests, resulting in active development of features that my users care about - rather than only features that someone in the company cares about, which I've encountered with other vendors.

We built Rootly from the perspective of "Anyone should be able to use this, with or without experience, and without needing to reference documentation" and Rootly has 100% enabled this. We have documentation and processes outlined, and they're entirely ignored because Rootly can literally guide you through the process from within Slack and the tooling, which is a huge win for adoption. Review collected by and hosted on G2.com.

My only real problems with Rootly are around certain features being a little weaker than the main Incident Management product, like the metrics dashboards not being as flexible as I would like.

However, not only have I heard Rootly are working on overhauling this, but we also utilise this data externally within our own tooling (as Rootly allows us to export this data) which heavily negates this downside. Review collected by and hosted on G2.com.

A few things I like so far:

- Easy to use with a great slack interface

- Has an API which allows me to use Rootly's data when I eventually want to work with this data programatically

- Although we don't use this feature, there's the ability to incorporate with JIRA which makes issue tracking for action items easier

- Anytime I've found a bug I can work with rootly's support team to get the issue resolved quickly

- Review collected by and hosted on G2.com.

Not too many things to dislike, but things I would love:

- More automation around incident retros - automating creating meetings based on participent's gmail calendar would be sick. Even though we have manditory retros with our workflow, those are often skipped, meaning we lose the valuable lessons learned during an incident.

- This may be a limitation of slack, but a clearer UI demarkation of who is playing which role in an incident would help users' tell who is playing which role in an incident Review collected by and hosted on G2.com.