G2

christopher d.

Observability Staff Engineer

Mid-Market (51-1000 emp.)

8/27/2026

"Unified End-to-End Incident Response with Exceptionally Responsive Support"

5/5

What do you like best about Rootly?

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

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

What do you dislike about Rootly?

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

What problems is Rootly solving and how is that benefiting you?

Rootly solves the fragmentation that used to define our incident response. Alerting, on-call paging, and incident management previously lived in separate tools, which led to lossy handoffs and multiple integrations to maintain. With Rootly, it all comes together in one platform: an alert fires, our rules route it to the right on-call responder, and it moves straight into incident response with the context intact. The result is faster response and far less tool-wrangling when it matters most. The AI companion keeps improving, and speeds our ability to quickly and effectively respond to incidents with each iteration. Review collected by and hosted on G2.com.