The best is the code-free workflow builder, which is easily my favorite feature. It allows me to design automated response chains, like automatically opening a Jira ticket, spinning up a dedicated Slack war room, and paging the primary responder, all without having to write or maintain custom script wrappers for every new tool we adopt. This automation and workflow make it easy because it removes the manual, high-pressure tasks that usually occur during an outage. I have more free time to focus on critical tasks instead of manually updating the status. Additionally, everything is linked, with context prepopulated in the notification, and the incident response happens almost entirely in the background, significantly lowering our mean time to resolve and keeping our engineering team focused on building rather than firefighting. Connecting xMatters to our existing DevOps stack was remarkably fast. They have an extensive library of out-of-the-box integrations for tools like Jira, Slack, and our cloud monitoring platform, so we didn't have to build custom hooks from scratch. We could authenticate our API keys, import our on-call schedule, and have our first automatic alert loop running in just a few hours. Review collected by and hosted on G2.com.

Areas that need improvement is the on-call scheduling interface for complex multilayer rotation. Because that can be quite confusing to use. While it is powerful navigating the UI to set up overlapping groups within groups or handling temporary holiday coverage. For global team across different time zones often involve too many clicks and hidden menus. It feels like it was designed for a static hierarchy, and it could definitely benefit from a more intuitive drag and drop calendar view to manage dynamic shift changes. Review collected by and hosted on G2.com.

Things that work well with xMatters is the automated internal status page paired with a situation-specific responded template. It's phenomenally executed, allowing us to construct a preapproved messaging framework for different business crisis tiers. This helps us maintain a centralized system health dashboard for our entire workforce. It makes my work easier by eliminating the burden of ad hoc status reporting during high-pressure situations. Instead of manually drafting updates every thirty minutes, the software lets us group corporate services logically and publish them instantly with a color-coded health indicator to our secure internal portal. Review collected by and hosted on G2.com.

I don't really like the sub notification management and trigger view filters. They can feel overly complex when managing nontechnical stuff. Setting up granular routine rules for specific regional directors without accidentally grouping them into global IT background noise requires digging into heavy, complex web logic. I think they really need to add a cleaner, more visual administrative grid for business subscription management to make it easier to audit who received the alert without needing technical system engineers to configure it. Review collected by and hosted on G2.com.

The best tools is with the conference bridge integration in xMatters, which our incident commander relies on to bring together the right people quickly during major incidents. When an incident is declared, it automatically dials out to the on-call engineers and drops them into a live bridge, eliminating the need to call each person individually. The first few minutes of an incident used to be confusing about who was on the call, but now, with the bridge already populated, people are talking while the coordinator is still getting up to speed. The Slack channel integration is also really important, as it automatically updates the incident communication, ensuring everyone is informed instantly. Review collected by and hosted on G2.com.

I think they need to make some improvement with user interface because it has been slow to come. The platform works really reliably, but navigating certain aspects still feels like it was designed for a different era. Configuring notification rules for individual users is especially buried in a way that causes confusion for new team members. Every time we onboard someone new onto the on-call rotation, we end up walking them through the same settings manually. It isn't intuitive enough to figure out independently. Review collected by and hosted on G2.com.

I really appreciate how xMatters tightens coordination when infrastructure issues crop up unexpectedly. It decides which engineer picks up the incident, cutting out duplicated effort. The visibility that xMatters provides, showing who has acknowledged an issue and where it sits in the escalation chain, is invaluable during a live incident. The acknowledgement and escalation paths are clear, keeping our team aligned and focused. It's been quite easy to set up, and I mainly integrate it with Datadog for alerts and Jira for incident tracking. Review collected by and hosted on G2.com.

My main gripe is the upkeep of on-call schedules whenever our rota shifts. We often have engineers covering across projects, so I have to double-check the schedule configuration to confirm the right people get paged. Get it wrong and an alert lands on someone who is off rotation, so I always verify the setup before changes go live. Review collected by and hosted on G2.com.

What I love using is the Flow Designer in xMatters. It's easily the best part of the platform. The drag-and-drop workflow builder connects our different tools into automated chains without needing to write any code. For example, we set it up so that when a critical crash happens, xMatters automatically opens Jira tickets, creates a dedicated Slack room, and patches through to the primary responder. This makes my work so much easier because it handles all the chaotic coordination during an outage. It really saves everyone time, and only the specific person needed for the problem has to attend to it. Review collected by and hosted on G2.com.

Managing complex on-call scheduling overrides can get pretty frustrating. If a responder goes on vacation and you need to set up temporary holiday coverage, the configuration scheme feels clunky and buried. It's too easy to accidentally leave gaps in coverage if you don't carefully double-check the calendar view. They really need to make the schedule overriding tools more intuitive. Review collected by and hosted on G2.com.

The incident management automation logic is accurate to the hilt. When there's a system outage and we need to know who the primary responders are, it's important to us. We have advanced notification routing rules, so that our core microservices architecture has zero downtime. Review collected by and hosted on G2.com.

There are too many clicks required to change the configuration of the schedule. Sometimes, the mobile application notifications become unresponsive for as long as a few minutes during peak traffic times. The permission management for new team members requiring restricted access is still overly complex. Generating custom reports is too long to produce simple performance metrics that are accurate. Review collected by and hosted on G2.com.

The intelligent escalation paths are great, when our monitoring tools trigger an outage, xMatters does not hit the entire team, it follows our on-call rotation, attempts to reach the primary engineer first and then the backup if they are not reached. The integration with Slack and PagerDuty is two-way, so we can triage incidents without having to switch between applications, and when we're out on a call, we can still receive persistent alerts and notifications on the mobile app, even if it's on silent mode. Review collected by and hosted on G2.com.

It's not the most user-friendly setup in the beginning – getting a complex workflow and integrating with our legacy systems was quite a bit of work for their professional services team. Review collected by and hosted on G2.com.

I like the visual automation and workflow features, which are quite intuitive, as well as the ability to link technical monitoring events directly to alerts for the relevant teams. That’s what I really liked about xMatters. Review collected by and hosted on G2.com.

Managing the volume of notifications can feel overwhelming if you don’t set aside time from day one to fine-tune the filtering rules. Review collected by and hosted on G2.com.

I appreciate most about xMatters the structure it brings to our incident response. The automatic routing helps immensely with ownership during incidents, resolving what used to be a recurring pain point. Before xMatters, alerts created confusion with some team members assuming others were handling them. Now, there's clarity on who is on-call and what happens if they miss a page. This has lightened the mental load that used to rest on me. I find that xMatters makes excellent use of the on-call schedule to ensure the right person responds, and the escalation path kicks in as needed, which really streamlines our process. An incident like a sensor outage at 3am on a Sunday previously would have been chaotic, but last quarter it went from page to triage in just four minutes. The initial setup was pretty smooth, and we didn't face any major issues. Review collected by and hosted on G2.com.

The biggest friction point for me is managing rotations, since our schedules shift often with vacations, swaps, and coverage for new joiners, and keeping the system in sync takes work. The escalation path editor is powerful, but even a small change can mean clicking through several screens. A quicker way to handle routine swaps would save real time. Review collected by and hosted on G2.com.

What makes they helpful and reliable is the two-way notifications with xMatters. I didn't realize how valuable they were until we faced a live incident. It's great that when an alert fires, it doesn't just send a message and hope for the best. The responder can acknowledge, escalate, or decline directly from their phone, and the platform handles the response automatically. If no one acknowledges within a set time, it moves to the next person in the rotation. This is really helpful because not everyone gets paged, so someone not involved with the incident won't be disturbed, giving everyone more free time. Review collected by and hosted on G2.com.

The search inside the platform is not very good. I'm trying to find a past incident or a specific workflow and it takes longer than it should, and the results are not always what you were looking for. For a platform that logs everything, it feels like finding things should be easier. Review collected by and hosted on G2.com.