Rootly Reviews & Product Details

The slackbot is slick, gives a simple overview to anyone joining and means most users never need to head into the WebUI. This means that users can focus on one communication stream to manage the event, and that stream works for all users (remote and office-based) equally. Review collected by and hosted on G2.com.

Not so much a downside, but there are features we don't use (yet) - we have so much alert noise, that we haven't dared to turn on "automatic incident creation". I'd also love to see a management summary that gets sent only to nominated users for the past month. Review collected by and hosted on G2.com.

What I like best about Rootly is that it has become the central platform for our entire incident management process. We rely on it for incident ticketing, on-call management, and incident coordination, making it our single source of truth during critical events. The platform is intuitive, highly reliable, and has consistently delivered excellent uptime, which is essential for a business-critical application.

Another standout feature is its reporting capabilities. I use Rootly's reports every month to provide incident metrics and insights to management, helping us track operational performance and identify trends.

The Rootly support team has also been exceptional. On the rare occasions we've encountered issues, they've been highly responsive, proactive, and collaborative in resolving them quickly. Their commitment to customer success gives us confidence that we're well supported.

Overall, Rootly has become an indispensable part of our operations, and I would highly recommend it to any organization looking for a reliable, full-featured incident management platform. Review collected by and hosted on G2.com.

At this point, I don't have any significant dislikes about Rootly. It has been a reliable platform that consistently meets our incident management needs. If I had to suggest an area for improvement, it would be continuing to enhance reporting and dashboard customization to provide even greater flexibility for different teams and management audiences. However, this is more of a nice-to-have than a limitation, and it has not impacted our overall experience with the platform. Review collected by and hosted on G2.com.

Rootly is a powerful incident management tool with excellent AI integration. It gives us the flexibility to build custom workflows, forms, and fields, while still providing a well-curated set of out-of-the-box features that are easy to get started with. On the AI side, Rootly’s AI stands out as one of the best incident management options currently available on the market.

The UI/UX is clean, simple, and easy to adapt to. Rootly is also a reliable platform, and we haven’t experienced any performance issues. I’d also like to highlight that the support and onboarding have been smooth and prompt. Overall, we’ve achieved better ROI compared to other tools in the market. Review collected by and hosted on G2.com.

Overall, I have no complaints about Rootly as a product. Review collected by and hosted on G2.com.

I've been using Rootly for the full 2 years and 2 months I've been at this company, and the company itself has had it in place for over 2 years- it's deeply embedded in how we run incident management. Slack-first triage and declaration, severity- and type-driven workflow automation, and stakeholder notifications that fire automatically instead of relying on someone remembering to loop people in. Once you've built out your workflows and native fields correctly, incidents route themselves.

About six months ago we migrated our on-call/paging module from Opsgenie to Rootly, and it's been a great consolidation, having incident management and on-call scheduling/paging in the same platform removes a whole category of "which tool do I check" friction that existed when the two were split across vendors. Escalations tie directly into the incidents we're already tracking, without stitching together two separate systems.

Support has consistently been fast and genuinely helpful, both throughout our regular usage and again during the on-call migration. What really stands out, though, is how open the Rootly team is to design change requests when we've flagged something that made sense for our workflow, they've actually acted on it, and quickly. That responsiveness makes the whole experience feel seamless rather than like we're stuck waiting on a roadmap. Review collected by and hosted on G2.com.

Honestly, there's not much to complain about — most of what we've run into has been more of a ramp-up curve than an actual downside. The workflow engine (Liquid templating, condition logic) takes some time to fully get comfortable with, and it's worth understanding the "any of" vs "all of" condition logic well before scaling up automation, since getting it backwards can cause workflows to fire more than intended. Review collected by and hosted on G2.com.

I really like the way Rootly has implemented AI into the workflow because it's very intuitive. Rootly is super easy to use, and even before the new AI implementations, which are awesome, it was easy to jump in. The whole UX/UI experience is very easy to follow, and you intuitively know what to do and how to do it. It’s also very easy to find answers on your own through a few clicks. The way they built it is very elegant and smart, which makes it friendly. Rootly makes it extremely simple to configure, adapt, test, run, and continue without hassle. Integration with Slack makes the whole incident lifecycle streamlined, reducing cognitive overload from not needing to switch contexts. The support we've had since day one is great, with a solutions engineer and customer success managers guiding us and even their CEO hoping on and being involved, making the initial setup a breeze [special shout out to Alexa, Amy, Purvai and JJ here]. It's very easy to integrate Rootly with our existing ecosystem and tools like Slack, Jira, Coda[ Super Docs]. The ability to make it fit into our ecosystem effortlessly is really cool. Overall, it's just an awesome product to have. Review collected by and hosted on G2.com.

Nothing in particular, everything has just being great Review collected by and hosted on G2.com.

Running our entire incident workflow inside Slack has been a game-changer. The UI is clean, and performance stays rock-solid even during high-severity outages. Onboarding was extremely smooth, and the support team helped us get everything configured quickly. It also integrates seamlessly with our stack and the AI-generated timelines make writing post-mortems feel almost effortless. The ROI was obvious right away, since it saves our engineers hours of manual toil on every incident. Review collected by and hosted on G2.com.

Setting up on-call schedules and shift overrides felt a little unintuitive at first. During onboarding, the rotation UI took some trial and error to understand and configure correctly. Once we had it set up properly, though, everything ran smoothly and was easy to manage. Review collected by and hosted on G2.com.

The overall process is solid, and the incident management capabilities are really good. Integrations and APIs work well for us, and the on-call schedules, alerting, and workflows are all strong. The Rootly MCP and the AI capabilities have also been really helpful for our team. Review collected by and hosted on G2.com.

Postmortems and documentation are areas that really need a lot of improvement. Also, the AI accuracy could be better. Review collected by and hosted on G2.com.

Functionality; it runs very smoothly and integrates well in our day to day WoW. Being Slack native offers easy interaction. Additionally the customer support we receive is really great! Compared to other solutions it requires little configuration. The AI driven RCA reduces a significant amount of the "not so nice" documentation admin work. Review collected by and hosted on G2.com.

Sometimes we run into some minor functional requests we need for our organization, though those are always quickly followed up on with either a workaround or a functional change implementation. Review collected by and hosted on G2.com.

The retro/postmortem doc auto-generation is what I lean on the most, it pulls the incident timeline and key Slack context automatically, so nobody's stuck reconstructing what happened from memory the next day. On-call rotations and paging are simple to set up and. handoffs actually stick, we stopped dropping shifts the way we did with our old spreadsheet schedule Review collected by and hosted on G2.com.

Having to manually add and remove people from schedule rotations is a pain. I’ve also had issues with some Slack/Rootly commands before, but the team addressed them quickly. Review collected by and hosted on G2.com.

Rootly is extremely flexible when it comes to designing incident response workflows. For a startup like ours, it’s critical to have a single tool that can grow with us and adapt as our operations scale, instead of forcing us to rethink our process or switch systems as our needs evolve. The user interface is clean, modern, and easy to use, and the support experience has been phenomenal from the very beginning. Most importantly, Rootly treats me the same way they would a Fortune 500. As a startup, we often struggle when purchasing software because customer success and support can feel tied to how much money you spend. That hasn’t been the case with Rootly, and it’s been clear since Day 1. Review collected by and hosted on G2.com.

The workflows feature, while very powerful, is a little confusing to set up at first with different folders. I encountered some challenges the first time I set up workflows where duplicate folders would be created and it wasn't clear why. Once configured, however, the workflows and integrations were extremely powerful. Review collected by and hosted on G2.com.