Rootly integrates seamlessly with many commonly used monitoring tools. We are currently having most of our alerts coming from Prometheus. Rootly helps us manage all those in quick and easy way, integrates seamlessly with Slack and enriches the alert with helpful info like Runbook links etc. for on call folks to triage quickly. The UI is feature rich yet easy to navigate. I, myself have exported over 10K alerts over last month for analytical purpose and the performance is on par. The AI features are cherry on top but we are yet to fully utilize those. Review collected by and hosted on G2.com.

Not an issue as such but I feel routing alerts to different Slack channels. services and escalation policies have steep learning curve of their own. There are multiple ways to route the same alert and it sometimes confuses me whether to use a routing rule using Prometheus labels, or to use service with default Slack channel set to route the alerts. Review collected by and hosted on G2.com.

Rootly Oncall escalation methods has changed the game of prioritizing the incidents in the right way. Also the alerts are being used by respective teams in self serve way. Review collected by and hosted on G2.com.

Analytics page and Reporting can be better Review collected by and hosted on G2.com.

Rootly’s On-call and Incident Response platform helped us consolidate several disparate platforms into one unified solution. Previously, we had to stitch an incident’s lifecycle across separate tools—one for alerting and paging, another for coordinating the response, and others for status updates and retrospectives. Now we can run that entire path end to end in a single, modern system.

Beyond the product itself, Rootly’s support has been exceptionally responsive. When we need help, we get quick, knowledgeable answers, which made rolling out features like Advanced Alert Routing feel much lower-risk. Review collected by and hosted on G2.com.

The main area with room to grow is the documentation. At times it has lagged behind the product, and I’ve had to confirm a detail directly in the API instead of finding it clearly written down. That said, it’s improving every day and the gaps are closing quickly, so it feels more like a fast-moving product than a genuine pain point. Review collected by and hosted on G2.com.

Rootly stands out compared to other incident management vendors we evaluated thanks to how complete and polished the feature set is out of the box incident workflows, status pages, postmortems, and Slack-native incident channels all feel like they were designed together rather than bolted on. The UI is intuitive enough that engineers adopt it without much training, which isn't always true of similar tools.

Support has also been a highlight responsive, knowledgeable, and quick to help troubleshoot configuration issues or answer questions about best practices, rather than just pointing us to documentation.

Finally, the official Terraform provider makes it easy to manage our incident workflows, services, and configurations as code, which fits naturally into our existing infrastructure-as-code practices and makes changes auditable and repeatable across environments. Review collected by and hosted on G2.com.

Nothing in particular comes to mind, it's been a solid experience overall. Review collected by and hosted on G2.com.

The Slack-native workflow is the standout feature. Declaring an incident, paging the right people, and tracking the timeline all happen inside the channel we’re already working in, so there’s no context switching during a live incident. Before Rootly, our incident response was scattered across ad-hoc Slack threads, manual paging, and someone frantically trying to reconstruct a timeline after the fact for the postmortem. That led to lost context, slower coordination, and inconsistent follow-through on action items. Rootly addresses this by giving us a single, structured workflow for the entire incident lifecycle: it reduces the time it takes to get the right people engaged, maintains a reliable running record of what happened as it happens, and removes much of the manual burden of writing postmortems from scratch. Review collected by and hosted on G2.com.

The initial setup of workflows and integrations (on-call tooling, alerting, status pages) takes some upfront investment to get configured exactly the way our team wanted to Infrastructure as Code, and the sheer number of customization options can be a bit overwhelming at first. Review collected by and hosted on G2.com.

The best thing about Rootly is that it gives teams one place to manage the full incident lifecycle — on-call, incident response, retrospectives, and status pages — instead of juggling separate tools.

Why that’s valuable:

- It reduces context switching for responders.

- It creates a single source of truth for incident data.

- It uses automation and AI for things like investigations, summaries, timelines, and surfacing relevant docs.

- It integrates with tools teams already use, like Slack, Jira, Datadog, Microsoft Teams, and Zoom.

So, in short: Rootly’s biggest strength is making incident response faster, more coordinated, and less manual. Review collected by and hosted on G2.com.

Rootly is useful overall, but some workflows still feel transitional — for example, COE/postmortem work may still need to continue through Jira until the fuller Rootly process is rolled out. Review collected by and hosted on G2.com.

Rootly stays as my favourite Slack integration. It's easy to navigate and customization is limitless. I really like how easy it is to setup Rootly integration since a lot of settings have been moved behind feature flags (on/off toggles).

We are actively using Rootly On Call features and it's been integrated across our entire organization as the primary on-call system without any issues. Along with that is a very modern looking mobile app, which is very easy to use for Engineers as well as Incident Management Teams.

Rootly Support system has remained as something I'd like to highlight. Their response times are fast and customer satisfaction is a priority. I've only had pleasant experience with Rootly. Review collected by and hosted on G2.com.

Since my last review Rootly has gone through major improvements. I'm very pleased with how easy it is to navigate the workflow and various settings/automations etc. The big challenge for all Incident Management products and Rootly is to integrate more AI features and functionalities into their product. We've already seen multiple of these features come out and are eagerly waiting to try out more! 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.