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

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

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

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

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

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

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

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

Rootly has made our incident response process much more organized and consistent. It gives the team a clear workflow to follow during high-pressure situations, helps keep communication in one place, and reduces the manual coordination that can slow down a response.

What I appreciate most is how naturally it fits into our day-to-day engineering workflow. Rootly makes it easier for responders and stakeholders to stay aligned, while also capturing the information we need for follow-up and continuous improvement. Review collected by and hosted on G2.com.

The main drawback is that Rootly can feel a little click-heavy, especially when configuring or managing more complex workflows. Getting the platform running smoothly also requires some upfront investment in integrations and customization. Once everything is connected and tailored to the team, the experience improves significantly, but the initial setup can take time and iteration. Review collected by and hosted on G2.com.

The Rootly alerts integrations with different providers is really useful. The UI Interface is very seemless, easy to use and easy to debug any issues. Performance is good as well, don't see much latencies in getting the alerts when the monitors fire. Not sure about the pricing though, since that is managed by the Platform team. Review collected by and hosted on G2.com.

The alert default sound is very painfully loud and noisy. The visibility to some of the AI tools could be better though so that they are more useful to the team. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

I don't have anything right now that I dislike in rootly. Going really good so far. Review collected by and hosted on G2.com.