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

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

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

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

Rootly is allowing us to customize how our teams surface alerts that are important to us and our customers. It allows us to be more proactive and allows us to create beneficial alerting to our teams.

Their internal Customer Support Team has also gone above and beyond on multiple occasions to help us navigate and customize to our needs. Review collected by and hosted on G2.com.

Rootly is highly customizable, which means you have to invest time in order to build out/configure some things. They have made great updates to help with this via their AI tools and templating options, which have both been game-changers for us. Review collected by and hosted on G2.com.

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

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

I like Rootly because of its automated scheduling, which really helps us replace tedious manual coordination with structured shift plans that keep the team aligned. The on-call automated phone feature is also a huge plus, providing customers with one number to call. Plus, its integration with Slack makes it even more efficient for our use. Review collected by and hosted on G2.com.

The initial setup for complex shift schedules with Rootly can be time-intensive. Although setting up basic shift rotations is straightforward, configuring non-standard, highly complex shift overrides or handling multi-timezone handoffs required some fine-tuning during the initial onboarding. The Operations team had a more intensive setup process due to the need to migrate more integrations. I think having pre-built out-of-the-box shift templates or an agent that you can verbally explain your needs to might improve the setup experience. Review collected by and hosted on G2.com.

The automation capabilities around alerting and on-call management are incredibly smooth. It eliminates the manual friction of paging the right team during high-severity events. Additionally, the status page engine is incredibly intuitive, making it painless to maintain transparency with our stakeholders and user base when things go wrong. Review collected by and hosted on G2.com.

It would be helpful to have even more out-of-the-box templates for multi-team on-call rotations, as configuring complex holiday overrides can sometimes feel overly granular. Review collected by and hosted on G2.com.

slackbot agent. very easy to access who's oncall without having to open the rootly app Review collected by and hosted on G2.com.

there is no option of my Team. I have to remember my teams official name and search it then I can see when I'm oncall. there should be a way where I could just see when I'm oncall(my bad if it's already there) Review collected by and hosted on G2.com.

I love how easily Rootly can be personalized and configured to match very specific requirements and team habits. I especially appreciate the automatic postmortem generation based on the incident channel content, which saves us a lot of time and effort. I also enjoy that you can seamlessly integrate your own LLM prompt into Rootly workflows, giving a lot of flexibility to tailor AI assistance to your organization's needs. Review collected by and hosted on G2.com.

While it's not its main job, having the possibility to retrieve context and insight by performing some RCA using MCP access to the organization's observability data to help identify the root cause could be a plus. Review collected by and hosted on G2.com.

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

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

One thing I really love about Rootly is the automatic JIRA creation. The automatic Slack channel creation is also very useful, and I especially like that it lives right inside Slack. Review collected by and hosted on G2.com.

I don’t like that when I run /incident, I have to fill out the initial incident report directly in the Slack UI. If there’s a way to complete that step through a web page instead, I’m not aware of it. Review collected by and hosted on G2.com.