UI, new features. On-call shifts planning. Review collected by and hosted on G2.com.

Alerts vs Incidents. Closing incident does not close alert. Review collected by and hosted on G2.com.

Rootly has been a simple on-call alerting platform that meets many of our needs, all at a very competitive price compared to competitors. What I like best is how easy it is to use and get going out of the box - the platform is intuitive and does exactly what we need. Customer support / relations has been fairly engaged and happy to work with us on feature requests - even with being a relatively small team and small customer. It was quick and seamless to get up and running, especially with popular integrations that are supported and well documented. Review collected by and hosted on G2.com.

Being a simple platform, some features and complex use cases (such as automatic scheduling) is where Rootly falls behind the competitors . Although, this has not been a dealbreaker for us as the platform is quite simple, easy to use and sits at a very competitive price. Review collected by and hosted on G2.com.

Rootly is a fantastic tool for both incident management and on-call handling. It has opinionated defaults that are often great on their own, but are also configurable.

It integrated easily with our alerting systems, and provided both an easy initial setup but also the promise of more power and flexibility in routing alerts into pages if we needed it in the future. The on-call tool has much better ergonomics than our previous solution, for a fraction of the price of other pager solutions.

Why have separate tools for incident management, on-call/paging, statuspages, and incident workflows when you could have one well-considered one that just works without jumping through hoops?

Perhaps the biggest secret though is the customer support which is fantastic, even for a smaller team like ours. They've been responsive to both feature requests and bug reports, and clearly care about their product and their customers.

I can recommend Rootly without hesitation if you're looking to level-up your incident management and paging systems. Review collected by and hosted on G2.com.

As a relatively newer product (compared to its competitors at least), there are some rough edges especially around the terraform provider. Additionally there are some events you'd expect to be able to trigger workflow that don't exist. But given the already high quality of the rest of the product and the rate at which it's improving, working around these things is a tradeoff I'm more than happy to make. Review collected by and hosted on G2.com.

Ease of use and reliability. It was very easy to set up, and the support has been good. Review collected by and hosted on G2.com.

Alerts tend to be noisy and disruptive. Marking them as noise doesn't seem to work as well. Review collected by and hosted on G2.com.

Rootly helped me reduce my cognitive load while on-call recently. Declaring an incident and getting the basics clearly defined upfront (severity, owner, roles, conference bridge) is quick, and the prompts are actually helpful without being really annoying. Review collected by and hosted on G2.com.

Some workflows took a couple iterations to match how we actually operate (not a dealbreaker). Review collected by and hosted on G2.com.

What I like best about Root.ly is how seamless it makes the incident management process. It brings structure and automation to what can otherwise be a chaotic and stressful situation, and the intuitive workflows help keep everyone aligned. I also really appreciate how well it integrates with the tools we already use, which makes adoption painless and ensures it fits naturally into our existing processes. Overall, it creates a sense of confidence that incidents will be handled consistently and efficiently, without adding unnecessary overhead. Review collected by and hosted on G2.com.

There are so many options that it can feel overwhelming at first, but the flexibility is worth it. Review collected by and hosted on G2.com.

Slack-native incident management: Instead of forcing teams into a separate tool, Rootly operates inside Slack—where incidents actually unfold. That reduces context switching and speeds up coordination. Review collected by and hosted on G2.com.

Slack fatigue. Some teams prefer separating incident response from normal chat. Running everything in Slack can create notification overload during major incidents. Review collected by and hosted on G2.com.

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.