--- title: Rootly Reviews meta_title: 'Rootly Reviews 2026: Details, Pricing, & Features | G2' meta_description: Filter 96 reviews by the users' company size, role or industry to find out how Rootly works for a business like yours. aggregate_rating: rating_value: 4.7 review_count: 96 scale: '5' date_modified: '2026-08-01' parent_category: name: IT Management url: https://www.g2.com/categories/it-management --- # Rootly Reviews **Vendor:** Rootly **Category:** [Incident Management Software](https://www.g2.com/categories/incident-management) **Average Rating:** 4.7/5.0 **Total Reviews:** 96 ## About Rootly Rootly is the AI-native on-call and incident management platform that helps you resolve incidents faster, improve system resilience, and streamline on-call operations. It’s your always-on production AI agent that automates root cause analysis and identifies patterns that drive continuous improvement—trusted by thousands of companies like NVIDIA, Replit, Elastic, Canva, Clay, DoorDash, SoFi, and Superhuman. ## Rootly Pros & Cons **What users like:** - Users appreciate the **ease of use** with Rootly, seamlessly integrating into Slack and enhancing incident management effortlessly. (19 reviews) - Users admire Rootly's **exceptional customer support** , noting the team's proactive assistance and seamless communication throughout the process. (14 reviews) - Users praise the **Slack integration** of Rootly for enhancing real-time collaboration and minimizing context switching. (14 reviews) - Users praise Rootly for its **seamless automation** which simplifies incident management and enhances team collaboration and efficiency. (11 reviews) - Users love Rootly's **seamless integrations** , which simplify workflows and enhance collaboration with existing tools like Slack and Jira. (11 reviews) - Customer Satisfaction (6 reviews) - Users appreciate the **easy setup** of Rootly, enabling quick onboarding and efficient integration with existing tools. (6 reviews) - Flexibility (6 reviews) - Intuitive (6 reviews) - Efficiency (5 reviews) **What users dislike:** - Users identify **feature issues** with Rootly, particularly in analytics, reporting, and custom forms that need improvement. (5 reviews) - Users note **integration issues** with Rootly, as it lacks robust out-of-the-box options compared to competitors. (4 reviews) - Users note the **missing features** in Rootly, particularly lacking out-of-the-box integrations and automation options. (4 reviews) - Users find Rootly's **initial setup complexity** challenging, especially for smaller teams without DevOps expertise. (3 reviews) - Users highlight **limited features** , like needing multiple channels per incident and complex workflows, which can hinder usability. (3 reviews) - Users note a **lack of tutorials** for advanced workflows, leading to trial-and-error in customizations. (2 reviews) - Limited Customization (2 reviews) - Users experience **notification overload** in Slack during incidents, leading to frustration and distraction from critical tasks. (2 reviews) - Users feel that the **overwhelming options** in Rootly can lead to confusion and notification overload during incidents. (2 reviews) - Template Issues (2 reviews) ## Rootly Reviews ### 1. The Best Incident Management tool for everyone! **Rating:** 5.0/5.0 stars **Reviewed by:** Karl K. | Senior Problem Engineer, Gambling & Casinos, Mid-Market (51-1000 emp.) **Reviewed Date:** January 18, 2023 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** 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! **What problems is Rootly solving and how is that benefiting you?** Rootly reduces most of the manual work needed to lay down the foundation for a new incident through automation and workflows. New incident along with a specific slack channel can be created in seconds by anyone. Same goes for tracking and creating action items or managing postmortem timeline if needed. Our way of using Rootly is also promoting transparency within the company, so that anyone and everyone can join the incident channel if they want to contribute or want to be up to date with the latest developments. Rootly sends out notifications in relevant channels and this often reduces the time to gather correct team of specialists and to resolve the incident itself. **Official Response from Adam Frank:** > Karl, thank you for writing this, and for coming back to update it after your first review. We continue to invest in AI so we'll keep you updated with new functionality as we release it. It's always great to hear your feedback. ### 2. Rootly: Reliable, Intuitive Incident Management with Excellent Reporting and Support **Rating:** 5.0/5.0 stars **Reviewed by:** Steven K. | Global Incident Manager, Mid-Market (51-1000 emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** 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. **What problems is Rootly solving and how is that benefiting you?** Rootly has streamlined and standardized our entire incident management process by providing a single platform for incident ticketing, on-call management, and incident coordination. Instead of relying on multiple tools, our teams can manage the complete incident lifecycle in one place via the integration of Slack, which improves collaboration and helps us respond to incidents more efficiently. The platform has also made it easier to track and report on incidents. I regularly use Rootly's reporting features to generate monthly management reports, giving leadership visibility into incident trends and operational performance. Combined with its high reliability and responsive support team, Rootly has become a critical part of our operations, helping us minimize downtime, improve response times, and maintain a consistent incident management process. **Official Response from Adam Frank:** > Steven, thank you for the review, and specifically for framing the reporting side. More flexibility for different audiences is the right ask and it is where the metrics work is headed. ### 3. Powerful Incident Management with Best-in-Class AI and Flexible Workflows **Rating:** 5.0/5.0 stars **Reviewed by:** Tejash C. | Site reliability Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** Overall, I have no complaints about Rootly as a product. **What problems is Rootly solving and how is that benefiting you?** Rootly has been our alerting and incident lifecycle management tool. From alerting through postmortem creation, we rely on Rootly, and it has made incident management much easier and more straightforward for our team. **Official Response from Adam Frank:** > Tejash, thank you for writing this. Calling our AI the best in the category is a high bar and we would rather keep earning it than sit on it. Good to hear the balance landed. ### 4. Our incident management backbone, now with on-call built in **Rating:** 5.0/5.0 stars **Reviewed by:** Teodora B. | Major Incident Manager, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** 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. **What problems is Rootly solving and how is that benefiting you?** Rootly gives us one place for incident lifecycle management — declaration, severity-driven routing, communication, and now on-call/paging — instead of stitching together separate tools. The Opsgenie-to-Rootly on-call migration in particular removed a seam between "who gets paged" and "how the incident gets managed," which used to be two disconnected systems. **Official Response from Adam Frank:** > Teodora, thank you for writing this in such detail. The Opsgenie consolidation account is useful to other teams weighing the same move. Your point on "any of" versus "all of" is the single most common workflow mistake we see, and it is a docs failure on our side rather than a user error. We are adding worked examples for condition logic. Thanks for pointing it out. ### 5. Painless, Streamlined, friendly and Smart. The Rootly experience is awesome **Rating:** 5.0/5.0 stars **Reviewed by:** Guillermo S. | International Project Manager, Enterprise (> 1000 emp.) **Reviewed Date:** May 08, 2026 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** Nothing in particular, everything has just being great **What problems is Rootly solving and how is that benefiting you?** Rootly streamlined our incident management, reducing cognitive overload by integrating into Slack and covering the whole incident lifecycle without context switching. **Official Response from Adam Frank:** > Guillermo, thank you for the review. Passing this to Alex, Amy, and Purvai directly, and JJ will see it too. Knowing what to do without reading documentation is the bar we aim at, so it is good to hear it landed. ### 6. Auto-Generated Postmortems and Smooth On-Call Handoffs **Rating:** 4.0/5.0 stars **Reviewed by:** Johann N. | VP of Engineering, Mid-Market (51-1000 emp.) **Reviewed Date:** July 23, 2026 **What do you like best about Rootly?** 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 **What do you dislike about Rootly?** 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. **What problems is Rootly solving and how is that benefiting you?** Rootly cuts down time to resolution by keeping paging, rotations, and incident response in one place, rather than having to chase people down manually. It also encourages a repeatable process instead of ad hoc firefighting, and the auto-generated retro docs build in accountability—there’s always a clear record of what happened and who owned what. **Official Response from Adam Frank:** > Johann, thank you for writing this. Manual add and remove on rotation membership is fair and should be automated. Glad the retrospective generation is carrying its weight. ### 7. Flexible, Scalable Incident Workflows with Phenomenal Support **Rating:** 5.0/5.0 stars **Reviewed by:** Alex M. | Chief Executive Officer, Small-Business (50 or fewer emp.) **Reviewed Date:** June 19, 2026 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** 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. **What problems is Rootly solving and how is that benefiting you?** Integrations with existing tools and speed to resolution. For a startup company like ours, two main problems are solved by Rootly. 1 - we can more quickly communicate out meaningful status updates to our end consumers. 2- we can resolve incidents much faster with less human intervention needed. **Official Response from Adam Frank:** > Alex, thank you for the review. On the Fortune 500 comparison, that is deliberate. Tiering support by contract size is a practice we decided not to adopt. We appreciate you business and it's a pleasure working with you. ### 8. Effortless Incident Management with Rootly **Rating:** 5.0/5.0 stars **Reviewed by:** Anastasia K. | Mid-Market (51-1000 emp.) **Reviewed Date:** July 30, 2026 **What do you like best about Rootly?** I like Rootly for its organized incident management and internal alerting, making the process simple and smooth. I appreciate having two different status pages for our American and Australian customers. The software feels modern, with a very simple UI and straightforward setup that just works without any issues. I value the ability to add almost any alert source and the use of the generic webhook, which we use a lot. Rootly's MCP feature is great as it helps us analyze the data effectively. Additionally, the initial setup was pretty straightforward; we were live within two weeks. **What do you dislike about Rootly?** There's not much really. Rootly covers everything that we need. So that's why it's hard for me to tell what should be improved. We had some small challenges with the UI, but I know that it's just a matter of time because Rootly is already addressing them. **What problems is Rootly solving and how is that benefiting you?** Rootly is part of Pepper's incident management and on-call process. It makes managing multiple status pages simple and smooth. The alert setup allows adding nearly any alert source, making it valuable for our team. **Official Response from Adam Frank:** > Anastasia, thank you so much for writing this. Two weeks to live is great to hear, and running separate status pages for American and Australian customers is a fantastic idea. Glad to hear it's holding up. We appreciate your feedback so please keep it coming. You're directly helping make the product better. ### 9. All-in-One Incident Response Platform with Powerful Integrations and Automation **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Security and Investigations | Mid-Market (51-1000 emp.) **Reviewed Date:** July 29, 2026 **What do you like best about Rootly?** I like how it encompasses all the parts needed for incident response and the incident management lifecycle in a single system; on-call, tracks timelines, role assignment, houses incident metrics and root cause data, you can visualize data with dashboards, incident reports can be built and stored in Rootly. It has rich integrations that allow us to plug it into our incident response workflow, on-call experience, and the different tools and vendors we use. We use it to integrate with Datadog, Slack, Zendesk, Zoom, and our homegrown tools. It has a workflow engine that allows us to build custom automations and reduce manual work during an incident when time and focus is crucial. It has the APIs, MCP, and UI we need to get our work done effectively. It performs and is reliable to our expectations. It is priced very well when looking at competing vendors. The account team is super helpful and available when we need them. They're very helpful with onboarding new features and functionality when asked and they're always offering to help. They have good AI functionality that allows for things like summarizing an incident to catch someone up that has joined an incident. **What do you dislike about Rootly?** The dashboard building isn't intuitive and requires time investment to understand and build dashboards. I haven't found a way to build in enforcement to make sure incident hygiene meets our needs and requires follow up at times. I'd like to see more automation built there so I don't need to build custom solutions. **What problems is Rootly solving and how is that benefiting you?** We didn't have a formal incident process or toolset prior to Rootly. Rootly gave us the tooling and guidance we needed to mature our incident management and incident response processes. We now have a formal incident response process and the tooling we need to deliver on that process. **Official Response from Adam Frank:** > Thank you for writing this, and for being precise about both gaps rather than leaving them general. We appreciate your thoughtful feedback. Reminders and nudges exist today and can be scoped per workflow, which covers prompting but not enforcement. Good to hear the tooling and the guidance both carried though. ### 10. Effortless Incident Management and Stellar Support **Rating:** 5.0/5.0 stars **Reviewed by:** Alan L. | SRE Lead, Mid-Market (51-1000 emp.) **Reviewed Date:** July 24, 2026 **What do you like best about Rootly?** I find Rootly simple to use and fully featured, which allows us to go from 0 to 1 quickly. It gives us the ability to control workflows, alerts, and alert sources through both the GUI and Infrastructure-as-Code, which fits well with our organization's focus. The customer support is top-notch. The documentation is available and handy, and there are a bunch of tools like the MCP that AI agents can utilize. I also appreciate Rootly's large ecosystem of integrations, which includes Slack, Zoom, Webhooks, and more. The initial setup was very easy, and although there's some learning and evaluation involved, the onboarding process overall was quite simple. Rootly addresses our needs for on-call workflows, incident management tasks, and metrics efficiently. **What do you dislike about Rootly?** I find that sometimes our organization requires custom workflows, and the documentation isn't detailed enough to support creating these. This is only limited to a few outlier cases that the support team was able to remedy/assist with. **What problems is Rootly solving and how is that benefiting you?** I find Rootly handles on-call workflows and routine incident management well. It's simple to use and fully featured, allowing us to quickly manage alerts and workflows. The large ecosystem of integrations is a big plus, along with top-notch customer support. **Official Response from Adam Frank:** > Alan, thank you for writing this. The documentation gap on outlier custom workflows is something I'll look to address personally. We are adding worked examples rather than more reference pages, since reference was never the problem. Good to hear the MCP server is useful. It was built for the agent-driven setup you are describing. ### 11. Comprehensive, Customizable Incident Management with Responsive Support **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Rootly?** Rootly offers comprehensive incident management capabilities across the entire incident lifecycle, along with strong AI-powered features. It provides a wide range of out-of-the-box integrations with status pages, AI platforms such as OpenAI and Claude, and various monitoring tools, making it easy to integrate into an existing ecosystem. One of Rootly's biggest strengths is its highly customizable workflows, which provide the flexibility to automate and tailor processes to meet specific organizational needs. Another aspect I really appreciate is their responsiveness. The team communicates effectively, promptly acknowledges feature requests, and actively works on implementing valuable improvements. That level of customer engagement and commitment to continuous enhancement is something that truly stands out. **What do you dislike about Rootly?** I don't have anything right now that I dislike in rootly. Going really good so far. **What problems is Rootly solving and how is that benefiting you?** Rootly enables us to manage the entire incident management lifecycle end-to-end, with seamless integrations to Slack and Atlassian Statuspage. We rely extensively on Rootly's customizable workflows to streamline and automate our incident management processes. Going forward, we're also looking to leverage its AI capabilities, particularly for postmortem generation and analysis, to further improve our incident response and learning process. **Official Response from Adam Frank:** > Thank you for the review. The retrospective generation you are planning to adopt, it drafts from the incident timeline and context for you rather than asking you to summarize after the fact, which is where most of the time saving shows up. Reach out if you have any questions. We'd be happy to hear your feedback. ### 12. Seamless, Smart, and Stress-Free Incident Response **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Automotive | Mid-Market (51-1000 emp.) **Reviewed Date:** September 12, 2025 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** There are so many options that it can feel overwhelming at first, but the flexibility is worth it. **What problems is Rootly solving and how is that benefiting you?** Root.ly is solving the challenge of coordinating incident response quickly and consistently. Before, incidents could feel scattered across different tools and teams, but Root.ly centralizes everything into one streamlined workflow. It reduces confusion, automates repetitive tasks, and ensures everyone is aligned from start to finish. The benefit is faster resolution times, less stress during high-pressure situations, and clear documentation afterward that helps us learn and improve for the future. **Official Response from Adam Frank:** > Thank you for writing this. "Overwhelming at first, worth it later" is honest. The platform carries a lot of depth but also a lot of simplicity and your feedback helps improve it every day so thank you again. We appreciate working with you. ### 13. Slack-Native incident and oncall management for relaible operations **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Rootly?** We use Rootly for on-call and incident management. What we like most is that it's completely Slack-native, making it easy for teams to declare, coordinate, and resolve incidents without leaving Slack. It provides a clear, structured incident workflow from declaration through resolution, and its on-call scheduling and alerting capabilities have been especially valuable for our operations. **What do you dislike about Rootly?** The workflow customization options feel somewhat limited, particularly for more complex use cases. Third-party integrations could also be broader, more flexible, and easier to adapt to different setups. Although Rootly has introduced AI features, they still seem fairly basic; with more power and maturity, they could do a better job supporting incident management and automation. **What problems is Rootly solving and how is that benefiting you?** Rootly has standardized our incident management process by providing a single, Slack-native workflow for incident declaration, on-call paging, collaboration, stakeholder communication, status page updates, and post-incident follow-up. It has reduced manual coordination, improved response times, and provided a more consistent and transparent incident response process across teams. **Official Response from Adam Frank:** > Thank you for the review, and for being specific about all three. It is worth knowing which cases specifically regarding workflow customization, since "limited" and "limited for what we need" are different problems. On AI, we're continuing to invest every day and pushing the limits. There's a lot more capability and power that's recently come and and will be coming out over the coming weeks. ### 14. Rootly Brings Clear, Structured Incident Management with Reliable On-Call Alerting **Rating:** 5.0/5.0 stars **Reviewed by:** Vaclav H. | Frontend Lead, Small-Business (50 or fewer emp.) **Reviewed Date:** July 16, 2026 **What do you like best about Rootly?** We use Rootly for incident management, and it gives us a clear, structured process for handling incidents from declaration through resolution. What we like most is the on-call and alerting setup: we can define who gets paged when something breaks, with phone and push notifications that wake the right person up at night if needed. The escalation policies also let us control who gets called and in what order, so the on-call person is contacted first instead of alerting everyone at once. **What do you dislike about Rootly?** The workflows feature is powerful, but it takes some time to get comfortable with. Setting up custom workflows comes with several dependencies, and the documentation didn’t always address our specific use case, so we had to iterate a few times before we got everything configured the way we wanted. **What problems is Rootly solving and how is that benefiting you?** Rootly solves the problem of coordinating incident response and on-call alerting. Previously, we didn’t have a consistent way to ensure the right person was notified when something broke, especially outside of working hours. Now alerts go straight to the phone of whoever is on-call, with clear escalation rules that define who gets contacted next if the first person doesn’t respond. As a result, incidents are picked up faster and ownership is clear, rather than relying on someone happening to notice an issue or having to manually call around. **Official Response from Adam Frank:** > Vaclav, thank you for the review. Iterating several times because the documentation did not cover your case is on us, and the fix is worked examples for the dependency chains rather than more reference material. Good to hear the escalation ordering does what it should. Paging the right person first instead of everyone at once is the entire point of it. ### 15. Incredibly Helpful, Receptive Support and Engineering Teams **Rating:** 5.0/5.0 stars **Reviewed by:** Lindsay H. | Operations Associate, Mid-Market (51-1000 emp.) **Reviewed Date:** July 23, 2026 **What do you like best about Rootly?** Their customer support and engineering teams have been incredibly helpful and receptive to any feedback we’ve shared. They’ve made sure we can use the platform to the best of our ability, and they’re always eager to help as we roll out new features. **What do you dislike about Rootly?** The startup was very challenging, and we ended up having to explain our process multiple times to different team members. Although our on-call system is a bit nuanced, some promises were made by team members that weren’t entirely doable, which ultimately led to a very delayed go-live date. **What problems is Rootly solving and how is that benefiting you?** Our on call system and managing alerts for power outages **Official Response from Adam Frank:** > Lindsay, thank you for writing this. Nuanced on-call setups are exactly the ones that need one owner from first call to go-live, and we have changed how handoffs work on complex on-call migrations. Don't hesitate to reach out, we always want to hear from you. ### 16. Full-Featured Incident Management Without the Bloat **Rating:** 5.0/5.0 stars **Reviewed by:** Helen W. | Devops Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** July 29, 2026 **What do you like best about Rootly?** Rootly is the perfect balance of full featured incident management platform, without all the bloat and complications. Easy to set up, integrates with all the tools our team already uses, great UI, excellent support staff. **What do you dislike about Rootly?** Custom workflows allow for full integration, even with smaller, less popular ticketing systems and other tools. Not a bad thing about it. **What problems is Rootly solving and how is that benefiting you?** Rootly makes tackling alert fatigue easy for the whole team with alert grouping. Quick and easy user adoption with it's native slack integration for all incident management features. **Official Response from Adam Frank:** > Helen, thank you for writing this. "Without the bloat" is the harder half of the design, since adding features is easy and knowing which ones to leave out is not. Useful point about custom workflows reaching the smaller, less popular ticketing systems. I'll make sure that makes it back to the team. We appreciate your feedback. Keep it coming. You're a pleasure to work with. ### 17. Feature-Rich Integrations, User-Friendly UX, and Exceptional Support **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.) **Reviewed Date:** July 31, 2026 **What do you like best about Rootly?** There are lots of integrations available, which can help automate incident management workflows and make it easier to report and manage incidents directly within the collaboration tools I use most, like Slack or Teams. The UX is user friendly, AI has helped with root cause analysis and retrospectives and summaries. Support during roll-out and ongoing support from our Customer Success Manager has been exceptional. **What do you dislike about Rootly?** It's feature-rich, so it can be overwhelming at times to learn all the different tools and configurations available. **What problems is Rootly solving and how is that benefiting you?** Standardizing our incident response process and improving our awareness of incidents has made our overall approach stronger. In turn, this has helped us track metrics like MTTD and MTTR, so we can actively work to reduce them over time. ### 18. Great Slack Integration, but Metrics and Reporting Need Easier Setup **Rating:** 3.5/5.0 stars **Reviewed by:** Angelo H. | Incident Management Practice Lead, Mid-Market (51-1000 emp.) **Reviewed Date:** July 27, 2026 **What do you like best about Rootly?** I find Rootly’s integration with Slack really great, because it makes it easy to create incidents and keep everything in one place. **What do you dislike about Rootly?** I do not like the metrics / reporting currently available or the not so easy to setup / use this feature. **What problems is Rootly solving and how is that benefiting you?** Rootly is very good at listening to its customers and acting on suggestions and improvements. For example, the status page could be made more configurable, which they are currently attending to. **Official Response from Adam Frank:** > Angelo, thank you for the review and for being direct. Reach out and let us know the three reports you would build first, that shapes what we prioritize. We always want to hear from you. ### 19. Intuitive, Rock-Solid Incident Management with Fast, Deep-Dive Support **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Rootly?** I've been using Rootly for our incident management, and it’s honestly been fantastic. The platform manages to pack in a lot of robust capabilities while keeping the UI super intuitive, which is exactly what you want when you're trying to navigate a stressful outage. Integrating it with our existing alerting and monitoring stack was a breeze, and it’s been completely rock-solid—I really haven't noticed a single performance hiccup or stability issue on their end. What really stands out to me, though, is their customer support. They reply incredibly fast and are actually willing to dive deep into technical discussions when we have specific feature requests or workflow ideas. The pricing is very reasonable, and the ROI is a no-brainer once you realize how many engineering hours you get back. I’m also really impressed by how early they jumped on AI and how fast they iterate to make those tools genuinely useful. We've been able to use their intelligence features to automate the heavy lifting for our post-incident retrospectives, which takes a massive manual writing burden off our incident owners. Overall, it's just a highly reliable, well-built tool that makes life a lot easier. **What do you dislike about Rootly?** Powerful workflows tooling but learning curve is bit steep since too many configuration in it **What problems is Rootly solving and how is that benefiting you?** Rootly solves the issue of context switching and repetitive manual tasks during incident response. By offering an intuitive interface across both the web and Slack, it turns Slack into a one-stop shop where our engineers can collaborate and investigate outages together in a single place. It also automates minor routine steps that previously had to be handled manually, with its AI features making the entire workflow even smoother and more frictionless. **Official Response from Adam Frank:** > Thank you for writing this at length. Narrowing the first-run path without capping what you can build later is the work. Good to hear the AI features took the retrospective writing burden off your incident owners. That was the whole point of building them. ### 20. Rootly’s Slack Integrations Make Incident Response Seamless **Rating:** 4.5/5.0 stars **Reviewed by:** Mariana N. | Cyber Security Analyst - IT Project Management , Mid-Market (51-1000 emp.) **Reviewed Date:** July 23, 2026 **What do you like best about Rootly?** As an IMOC, I find Rootly’s integrations extremely useful. They enable seamless integration with Slack, creating a centralized hub for coordinating and managing incident response activities. Initially, I didn't find the AI feature very useful because the output wasn't appropriate for incident response. However, it has improved significantly over time. The responses are now much more accurate, context-aware, and aligned with incident response needs, making the AI feature genuinely helpful in my day-to-day work. **What do you dislike about Rootly?** There are a lot of noisy notifications in Slack when I’m handling incidents. When they come in, they can disrupt the flow of the chat while we’re dealing with an incident. **What problems is Rootly solving and how is that benefiting you?** resolving incidents faster and getting metrics **Official Response from Adam Frank:** > Mariana, thank you for writing this. Notification policies can be scoped per workflow and per severity today. It's worth 15 minutes to tune. We'd be happy to help. Reach out anytime. Good to hear the AI output improved to the point of being useful. ### 21. Intuitive UI and Rapid Support, works Out-of-the-box **Rating:** 4.5/5.0 stars **Reviewed by:** ISHAN D. | Corpsys[DevOps] Engineer , Enterprise (> 1000 emp.) **Reviewed Date:** July 23, 2026 **What do you like best about Rootly?** I really like Rootly's easy-to-use UI and how everything has been well thought out. All the features are accounted for and actually help in one way or another, not just being gimmicks. The layout is neat and it's been pretty responsive so far, without any lag or issues. A few small feature requests from our side were tackled very fast and we're really happy with the response. **What do you dislike about Rootly?** Nothing so far. Updates to Roolty seem to be coming faster than our requests, so we are happy to be seeing new and useful features. **What problems is Rootly solving and how is that benefiting you?** I use Rootly for on-call and incident management. **Official Response from Adam Frank:** > ISHAN, thank you for writing this. "Features that actually help rather than being gimmicks" is the bar we hold ourselves to, so it is good to hear it read that way from a DevOps seat. Shipping faster than you can file requests is the position we want to be in. ### 22. Modern Incident Management With a Standout Slack Bot **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer & Network Security | Mid-Market (51-1000 emp.) **Reviewed Date:** July 31, 2026 **What do you like best about Rootly?** It's modern, active development and include most features required to do incident management. The slack bot in particular is very useful **What do you dislike about Rootly?** While it being a newer product means it's modern and up to today's standards, it also means it falls behind a little in terms of customization and other small details that come from a longer time in the market **What problems is Rootly solving and how is that benefiting you?** We use the Slack bot for incident management and on-call, and it makes the whole incident lifecycle much easier to run. It also helps streamline workflows and makes retrospectives easier to put together afterward. **Official Response from Adam Frank:** > Thank you for writing this review. We appreciate your feedback. Being newer has edge cases and small conveniences that products with a decade of accumulated customer requests have and we do not yet... key word yet. We 're shipping quickly so feature requests from customers still shape what ships. Keep the feedback coming always. Good to hear the Slack agent is carrying both incident management and on-call. ### 23. Flexible, Highly Configurable Platform with Helpful AI Incident Management **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Automotive | Mid-Market (51-1000 emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Rootly?** Configurability, it is very flexible. The new AI tools in incident management are very helpful also. Seems to have integrations to most of what we need as well. **What do you dislike about Rootly?** We are not always made aware of new features in a timely manner and sometimes find that things we are looking for are already available under a config switch we could not access. **What problems is Rootly solving and how is that benefiting you?** Our alert routing and incident response workflow. Giving the teams the ability to control their own alert routing allows us to intercept generic alerts wile letting team specific alerts route on down the pipe for their needs. **Official Response from Adam Frank:** > Thank you for this one. Discovering that something you needed was already shipped isn't something we want at all. We'll work to get you better updates. ### 24. Vital for Incident Management, Stellar Support **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User | Mid-Market (51-1000 emp.) **Reviewed Date:** June 05, 2026 **What do you like best about Rootly?** I use Rootly for incident management, and I really appreciate how it enables a seamless Slack-based incident management process through its custom workflows and actions. Rootly is an all-in-one incident management product that not only helps with scheduling but also running planned maintenance windows, which I find very valuable. I believe the IM process shouldn't burden the incident responder, and Rootly achieves that. One of the main differentiators of Rootly is its team; they are always available for help and made the migration easy by providing comprehensive training sessions. I also like their powerful workflow engine and capabilities. The product offers a comprehensive package and delivers a more reliable, seamless experience. Plus, the great value for the price is a bonus. The initial setup can be time-consuming, but thanks to the Rootly team’s significant assistance, it was made easy. **What do you dislike about Rootly?** The Terraform provider can sometimes be tricky to set up as there are multiple ways of configuring things. The learning curve and initial setup might be time consuming but worth it. **What problems is Rootly solving and how is that benefiting you?** Rootly simplifies incident management and workflows in Slack, eases writing postmortems, supports planned maintenance, and offers valuable team support for migration and training. **Official Response from Adam Frank:** > Thank you for the review. The Terraform provider offering several valid ways to configure the same thing is something we're addressing as part of a big upcoming Terraform update. We appreciate your feedback. This is how products improve. Thanks again. ### 25. High-Performance Platform with Great Automation, AI, and Integrations **Rating:** 5.0/5.0 stars **Reviewed by:** Yilmaz C. | Production Support and incident Manager, Mid-Market (51-1000 emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Rootly?** The interface, support for automation, AI support, performance, product support, integartions **What do you dislike about Rootly?** rich text format. it would be ideal if it implements Rich text format **What problems is Rootly solving and how is that benefiting you?** it help us manage incidents timely manner. we also receive alerts when critial components are not functioning **Official Response from Adam Frank:** > Yilmaz, thank you for the review. Rich text is a reasonable ask. We always appreciate your feedback and help shaping the product. ### 26. Rootly Streamlines Incident Management with Seamless Slack Integration **Rating:** 5.0/5.0 stars **Reviewed by:** Sopio U. | Integration & Solutions Team Lead, Small-Business (50 or fewer emp.) **Reviewed Date:** July 16, 2026 **What do you like best about Rootly?** What I like best about Rootly is how it streamlines incident management from start to finish. It makes it easy to coordinate teams, automate repetitive tasks, and maintain clear communication during incidents. The Slack integration is particularly helpful. **What do you dislike about Rootly?** Some advanced configurations can feel overwhelming for new users, and navigating all available features may take time. **What problems is Rootly solving and how is that benefiting you?** Rootly helps us solve several key operational challenges related to incident management. It centralizes communication, automates repetitive tasks, and ensures incidents are handled consistently across teams. **Official Response from Adam Frank:** > Sopio, thank you for writing this review. The gap between "works immediately" and "advanced configuration" can feel deep. We appreciate your feedback and are working around the clock to improve every corner of the product, both for new users and advanced power users. Keep the feedback coming! ### 27. Modern UI with Many Customizable Features **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Internet | Enterprise (> 1000 emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Rootly?** Many customizable features and modern UI **What do you dislike about Rootly?** It can be complex to setup the way eng leaders want, but possible so it's a lot of work to customize to how your boss wants it setup **What problems is Rootly solving and how is that benefiting you?** Solves custom workflows for incidents that are relevant and tuned to each business vertical. As the central team we can manage shared workflows that need to be triggered **Official Response from Adam Frank:** > Thank you for the review. Managing shared workflows centrally while each vertical gets its own tuning is the model we design for, so it is good to hear that structure holding at enterprise scale. ### 28. Attentive Support That Made the Difference **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Hospital & Health Care | Small-Business (50 or fewer emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Rootly?** The support! The team, particularly Jason Myers, has really made our experience. Thank you Jason for being so attentive to our use case and needs. **What do you dislike about Rootly?** Onboarding was a bit challenging, with a few misunderstandings and changes in account point person. All resolved now, but was difficuly for a moment. **What problems is Rootly solving and how is that benefiting you?** Overnight call paging system for healthcare use case. **Official Response from Adam Frank:** > Thank you for the review, and Jason will see it, I'll make sure. ### 29. Customizable Incident Response That Helps Us Mature Over Time **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.) **Reviewed Date:** July 22, 2026 **What do you like best about Rootly?** It’s customizable enough to align with our existing incident response process, while still adding enhancements that help us mature and improve over time. **What do you dislike about Rootly?** It doesn’t always provide full Terraform support, so I can’t manage everything entirely through code. **What problems is Rootly solving and how is that benefiting you?** I’m impressed with Rootly’s approach to AI. The AI-enabled features feel thoughtful and genuinely provide real value. **Official Response from Adam Frank:** > Thank you for the review. Good to hear the maintenance window support is earning its place. We've got some big Terraform updates coming that will make things much easier and provide a lot more capability. We'd love to hear from you to help shape what we build and release first. ### 30. Standardized Incident Management in Slack with Fast, Reliable Escalations **Rating:** 5.0/5.0 stars **Reviewed by:** Art S. | Director, Platform Engineering, Mid-Market (51-1000 emp.) **Reviewed Date:** January 26, 2026 **What do you like best about Rootly?** Rootly has helped us standardize our incident management practices within Slack, which is our primary means of communication. It reduces context switching and lets operations engineers stay focused on the actual issue, rather than bouncing between multiple tabs trying to find the right one. It’s also easy to use and enables quick, reliable escalations when we need them. **What do you dislike about Rootly?** Rootly does not have as many out of the box integrations as some of its competitors. You are able to work around this using webhooks, but the native integrations are more powerful and feature rich. **What problems is Rootly solving and how is that benefiting you?** Rootly provides a single pane of glass for incident management. It’s an all-in-one solution for managing incidents from initiation through retrospectives. Rootly makes it easier to stay focused on the active problems themselves, rather than getting bogged down in the constructs used to frame the problem. **Official Response from Adam Frank:** > Art, thank you so much for writing this. The native versus webhook distinction is the right one to draw and we would rather you had the native version. Which integrations are you covering with webhooks today? Your feedback is always greatly appreciated. ### 31. Streamlined Issue Logging with Clean, Fast Functionality **Rating:** 4.5/5.0 stars **Reviewed by:** Modi M. | Product Specialist, Mid-Market (51-1000 emp.) **Reviewed Date:** March 26, 2026 **What do you like best about Rootly?** I like Rootly for its clean and fast functionality. It's not difficult to navigate, which makes interactions smoother and more efficient. The speed of Rootly makes my work more productive. I appreciate how Rootly creates a separate space and Slack channel for interacting on a single issue with multiple stakeholders from cross-functional teams. **What do you dislike about Rootly?** I think it could be improved by having a guided tour whenever there's a new change or update to the product. It would make navigation easier, instead of us having to guess the next step. **What problems is Rootly solving and how is that benefiting you?** I use Rootly for logging issues, which creates a separate space and Slack channel for interacting with multiple stakeholders across teams. **Official Response from Adam Frank:** > Modi, thank you for the review. We have released more in-product guidance and non-disruptive notifications to highlight new capability. Check it out and keep the feedback coming. ### 32. Effortless Incident Management with Seamless Integrations **Rating:** 5.0/5.0 stars **Reviewed by:** Jason N. **Reviewed Date:** January 14, 2026 **What do you like best about Rootly?** I like that everything is stored in one place and integrates easily with all our existing tools. The workflow feature enables the automation of many tasks, eliminating manual steps, helping us ensure consistency of our processes, and allowing us to quickly respond to changes. The setup was very easy, and I was able to get up and running in about 2 hours and have the majority of the configuration for our needs in a day or less. **What do you dislike about Rootly?** There have been a couple of minor issues with integrations but the support team was quick to respond to our issues and fix them in the platform. **What problems is Rootly solving and how is that benefiting you?** Rootly helps coordinate incident resolution efforts, tracks items, supports compliance reporting, and integrates with existing tools. It stores everything in one place, automates tasks, and eliminates manual steps, ensuring process consistency and quick response to changes. **Official Response from Adam Frank:** > Jason, thank you very much for writing this. Up and running in about two hours with most configuration done inside a day is the onboarding path we want everyone on, so it is useful to have it stated publicly. We appreciate you and your feedback. Keep it coming. ### 33. Easy Setup, Reliable Performance, and Helpful Support **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** May 08, 2026 **What do you like best about Rootly?** Ease of use and reliability. It was very easy to set up, and the support has been great. **What do you dislike about Rootly?** N/A, we're happy with the product, keep doing a great job! **What problems is Rootly solving and how is that benefiting you?** On call organization and shift planning have been the biggest benefits of using rootly. **Official Response from Adam Frank:** > Thank you for the review. We'll do our best to keep you happy and use easy. ### 34. Slack-Native Incident Response Without Context Switching **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** July 16, 2026 **What do you like best about Rootly?** Slack-native, so incident response happens where the team already works. No context-switching into a separate console like PagerDuty forced. **What do you dislike about Rootly?** Mobile app keeps logging out. Re-auth mid-incident is the worst possible time. **What problems is Rootly solving and how is that benefiting you?** Centralizes incident response in Slack. No more jumping between PagerDuty, docs, and chat during an active incident. ### 35. Engineering manager view: consistency + visibility **Rating:** 5.0/5.0 stars **Reviewed by:** Anthony P. | Sr. Manager Engineering, Mid-Market (51-1000 emp.) **Reviewed Date:** January 22, 2026 **What do you like best about Rootly?** From an engineering manager’s perspective, the biggest value of this product is the consistency and visibility it brings. It helps me stay aligned with the team and quickly understand what’s happening across the group, without having to chase down updates. **What do you dislike about Rootly?** Easier, more automatic shift changes linked to the Outlook calendar. **What problems is Rootly solving and how is that benefiting you?** As an engineering manager, Rootly has improved my visibility into incidents without requiring me to constantly chase down context. The incident pages and timelines are easy to read, and it’s much simpler to spot recurring themes across services. ### 36. Intuitive UI and New Features That Simplify On-Call Shift Planning **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Information Services | Small-Business (50 or fewer emp.) **Reviewed Date:** July 16, 2026 **What do you like best about Rootly?** UI, new features. On-call shifts planning. **What do you dislike about Rootly?** Alerts vs Incidents. Closing incident does not close alert. **What problems is Rootly solving and how is that benefiting you?** It helps us to get know on multiple channels when some serious things happen. ### 37. Effortless On-Call Management at a Great Price **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Electrical/Electronic Manufacturing | Small-Business (50 or fewer emp.) **Reviewed Date:** November 10, 2025 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** 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. **What problems is Rootly solving and how is that benefiting you?** On-call alerting and shift scheduling ### 38. Simple, powerful, and configurable incident management. **Rating:** 5.0/5.0 stars **Reviewed by:** Matt B. | Senior Infrastructure Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** August 05, 2025 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** 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. **What problems is Rootly solving and how is that benefiting you?** Incident Management On-Call Management Paging Alert routing Incident Retrospectives / Post mortems ### 39. Rootly Makes Incident Declaration Fast and Low-Stress On-Call **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** January 22, 2026 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** Some workflows took a couple iterations to match how we actually operate (not a dealbreaker). **What problems is Rootly solving and how is that benefiting you?** 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. ### 40. Slack-Native Incident Management That Speeds Coordination **Rating:** 4.5/5.0 stars **Reviewed by:** Deborah H. | NOC Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** February 17, 2026 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** Slack fatigue. Some teams prefer separating incident response from normal chat. Running everything in Slack can create notification overload during major incidents. **What problems is Rootly solving and how is that benefiting you?** Faster Response Teams recover from issues quicker because everyone knows the playbook and steps are automated. ### 41. Delightful setup **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** January 14, 2026 **What do you like best about Rootly?** It was so easy to set up. We got our entire engineering team onboarded to an on-call schedule in a single day! **What do you dislike about Rootly?** I can't say there's anything that jumped out as negative. **What problems is Rootly solving and how is that benefiting you?** An easy-to-manage on-call rotation is a hard requirement for our org. Rootly made it so easy to set up and manage. Thanks Rootly! ### 42. Smooth incident management with strong automation capabilities **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.) **Reviewed Date:** September 12, 2025 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** 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. **What problems is Rootly solving and how is that benefiting you?** Rootly helps us standardize and automate our incident management process. Before Rootly, our workflows during incidents were scattered across multiple tools and depended heavily on manual steps. With Rootly, we’ve automated incident creation, escalation paths, and notifications directly in Slack and Jira, which has saved us time and reduced human error. It’s also made postmortems much easier to generate, ensuring we can learn from each incident quickly. ### 43. Effortless and Responsive Integration with Slack **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** January 12, 2026 **What do you like best about Rootly?** Very easy to use and responsive, connects with Slack **What do you dislike about Rootly?** Often nagging behavior and inability to understand certain tasks - templates would make this better **What problems is Rootly solving and how is that benefiting you?** They are enabling us to create and resolve incidents much faster and cohesively as a team - it also increased discoverability through Slack integration ### 44. Quick & easy to use - Great customer service **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Public Safety | Enterprise (> 1000 emp.) **Reviewed Date:** September 03, 2025 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** We have no issues so far, Rootly just works with minimal admin. **What problems is Rootly solving and how is that benefiting you?** Rootly is currently being used for our on-call security incidents solution. ### 45. Effortless Incident Management **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** October 24, 2025 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** The only downside is that Rootly can feel a bit complex to set up initially, especially for smaller teams without dedicated DevOps resources. **What problems is Rootly solving and how is that benefiting you?** Incident Management ### 46. One stop shop for streamlined Incident Management! **Rating:** 4.5/5.0 stars **Reviewed by:** Allen J. | Technical Program Manager- SRE, Enterprise (> 1000 emp.) **Reviewed Date:** February 25, 2025 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** 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. **What problems is Rootly solving and how is that benefiting you?** Rootly helps streamline incident management by automating workflows across JIRA, PagerDuty, and slack by keeping everything organized in Slack, and reducing the manual effort needed to track and resolve incidents in other platforms. It makes it easier to follow a consistent process, ensures key updates don’t get lost, and speeds up response times. The built-in post-mortem feature also helps improve reliability by making it simple to review and learn from past incidents. ### 47. Game-Changer for Incident Management **Rating:** 5.0/5.0 stars **Reviewed by:** Richard H. | VP of Engineering, Mid-Market (51-1000 emp.) **Reviewed Date:** February 24, 2025 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** No major downsides—occasional minor UI improvements would be nice, but the team iterates quickly! **What problems is Rootly solving and how is that benefiting you?** Rootly is solving the challenge of fragmented and inefficient incident management. Before using Rootly, coordinating incidents required a lot of manual effort—tracking updates across different tools, ensuring the right people were notified, and maintaining consistency in response processes. With Rootly, everything is streamlined. ### 48. Streamlined Incident Management with Great Automation and Support. **Rating:** 5.0/5.0 stars **Reviewed by:** Kieran W. | Service Delivery Manager, Mid-Market (51-1000 emp.) **Reviewed Date:** October 04, 2024 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** 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. **What problems is Rootly solving and how is that benefiting you?** Rootly helps us solve the challenge of managing incidents efficiently by automating key parts of the incident management process. It enables us to streamline everything from incident creation to resolution, ensuring that nothing falls through the cracks. With its seamless integration into Slack, we can manage incidents in real-time and keep our teams aligned, reducing communication delays. One of the biggest benefits has been a significant improvement in our incident metrics. Rootly has directly contributed to reducing our Mean Time to Detect (MTTD), Mean Time to Mitigate (MTTM), and Mean Time to Resolve (MTTR) stats. Automation and clear workflows allow us to respond faster and work more effectively as a team. Additionally, Rootly’s automation enables us to update our status page in real-time, ensuring that our customer base is kept informed throughout the entire incident process without manual intervention. This keeps communication clear and efficient. The ability to automate SLA reminders, incident escalations, and post-incident reviews further enhances our incident management process, helping us stay on top of every incident and respond swiftly. ### 49. Fantastic Incident Management Product with Unrivalled Flexibility **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** February 19, 2025 **What do you like best about Rootly?** 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. **What do you dislike about Rootly?** 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. **What problems is Rootly solving and how is that benefiting you?** Incident Management. Our previous Incident Management process and tooling was very difficult to work with, and resulted in very low engagement. By using Rootly to reduce barrier of entry we've massively increased adoption of the process, and in turn have a large amount of incident data that we can use to make informed decisions both about our progress and our future directions. ### 50. Convenient tool for incident management in slack with great features **Rating:** 4.0/5.0 stars **Reviewed by:** Michel G. | Staff Software Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** July 01, 2024 **What do you like best about Rootly?** 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 - **What do you dislike about Rootly?** 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 **What problems is Rootly solving and how is that benefiting you?** Acting as the hub to the incident management process ## Rootly Discussions - [What is Rootly - Manage Incidents on Slack used for?](https://www.g2.com/discussions/what-is-rootly-manage-incidents-on-slack-used-for) - [View Rootly pricing details and edition comparison](https://www.g2.com/products/rootly/reviews?section=pricing&secure%5Bexpires_at%5D=2026-08-02+01%3A04%3A48+-0500&secure%5Bsession_id%5D=e0fedb0a-86e1-4d33-850a-a30c4bfe5dce&secure%5Btoken%5D=23c0460ba49ec9d88f0ed2dca59cff524c94a8740b293958d35862a189915d7d&format=llm_user) ## Rootly Integrations - [Amazon Elastic Container Service (Amazon ECS)](https://www.g2.com/products/amazon-elastic-container-service-amazon-ecs/reviews) - [Asana](https://www.g2.com/products/asana/reviews) - [Backstage](https://www.g2.com/products/backstage/reviews) - [Checkly](https://www.g2.com/products/checkly/reviews) - [Chronosphere](https://www.g2.com/products/chronosphere/reviews) - [Cloudflare Application Security and Performance](https://www.g2.com/products/cloudflare-application-security-and-performance/reviews) - [Confluence](https://www.g2.com/products/confluence/reviews) - [Coralogix](https://www.g2.com/products/coralogix/reviews) - [Cortex](https://www.g2.com/products/ledger-bennett-cortex/reviews) - [Datadog](https://www.g2.com/products/datadog/reviews) - [Dynatrace](https://www.g2.com/products/dynatrace/reviews) - [Fivetran](https://www.g2.com/products/fivetran/reviews) - [GitHub](https://www.g2.com/products/github/reviews) - [GitLab](https://www.g2.com/products/gitlab/reviews) - [Glean](https://www.g2.com/products/glean-technologies-glean/reviews) - [Google Workspace](https://www.g2.com/products/google-workspace/reviews) - [Grafana Labs](https://www.g2.com/products/grafana-labs/reviews) - [Honeycomb](https://www.g2.com/products/honeycomb/reviews) - [Jira](https://www.g2.com/products/jira/reviews) - [JumpCloud](https://www.g2.com/products/jumpcloud/reviews) - [Kubernetes](https://www.g2.com/products/kubernetes/reviews) - [Linear](https://www.g2.com/products/linear/reviews) - [Microsoft Outlook](https://www.g2.com/products/microsoft-outlook/reviews) - [Microsoft Teams](https://www.g2.com/products/microsoft-teams/reviews) - [MongoDB Atlas](https://www.g2.com/products/mongodb-atlas/reviews) - [New Relic](https://www.g2.com/products/new-relic/reviews) - [Nobl9](https://www.g2.com/products/nobl9/reviews) - [Notion](https://www.g2.com/products/notion/reviews) - [Openai](https://www.g2.com/products/openai/reviews) - [Opsgenie](https://www.g2.com/products/opsgenie/reviews) - [OpsLevel](https://www.g2.com/products/opslevel/reviews) - [PagerDuty](https://www.g2.com/products/pagerduty/reviews) - [Prometheus](https://www.g2.com/products/prometheus/reviews) - [Pulumi](https://www.g2.com/products/pulumi/reviews) - [Pylon](https://www.g2.com/products/pylon-pylon/reviews) - [Sentry](https://www.g2.com/products/sentry/reviews) - [Slack](https://www.g2.com/products/slack/reviews) - [Slack Connector for Jira](https://www.g2.com/products/slack-connector-for-jira/reviews) - [Splunk](https://www.g2.com/products/splunk-2025-01-30/reviews) - [Superhuman Docs](https://www.g2.com/products/superhuman-docs/reviews) - [Zapier](https://www.g2.com/products/zapier/reviews) - [Zoom Workplace](https://www.g2.com/products/zoom-workplace/reviews) ## Rootly Features **Monitoring** - Constant Monitoring - Timely Alerts - TIcket Accuracy - AI Monitoring **Reliability Objectives & Service Operations - AI SRE Tools** - Intelligent On-Call Workflows - Error Budget Tracking - SLI & SLO Management - Service Health Modeling & Reporting **Management Tools** - Ticket Assignment - Standardization - Lifecycle Visualization **AI Detection & Signal Quality - AI SRE Tools** - Cross-Telemetry Correlation - Change-Aware Detection - Adaptive Anomaly Detection - Alert Correlation & Noise Reduction **Generative AI** - AI Text Generation - AI Text Summarization **Investigation & Root Cause Analysis - AI SRE Tools** - Guided Incident Investigation - Live Debugging in Production - AI Root Cause Analysis - Runtime-Verified Root Cause Analysis **Agentic AI - Incident Management** - Autonomous Task Execution - Multi-step Planning - Cross-system Integration - Adaptive Learning - Natural Language Interaction - Proactive Assistance - Decision Making **Automation & Platform Controls - AI SRE Tools** - Automated Runbook & Workflow Execution - Human-in-the-Loop Remediation - Integration, APIs & Secure Access Controls - AI-Assisted Code Fix Generation ## Top Rootly Alternatives - [incident.io](https://www.g2.com/products/incident-io/reviews) - 4.8/5.0 (224 reviews) - [FireHydrant](https://www.g2.com/products/firehydrant-firehydrant/reviews) - 4.5/5.0 (142 reviews) - [PagerDuty](https://www.g2.com/products/pagerduty/reviews) - 4.5/5.0 (948 reviews)