I appreciate how xMatters resolves the confusion around accountability when our systems falter by routing alerts directly to the on-call technician and escalating to me if unacknowledged. This ensures nothing slips past us during critical times. The value of xMatters for me lies in its ability to impose order when things go sideways, especially in a legal consultancy where confidentiality is key. The certainty of knowing who is responsible and that there's no duplicated effort or crossed wires is incredibly valuable. The on-call schedules provide clarity at a glance, ensuring alerts reach the right person immediately, which saves time and effort. Integrating xMatters with Jira Service Management and Datadog also enhances its functionality, tying alerts back to logged incidents and automating notifications. The initial setup was quite simple and without major issues, which I also appreciated. Review collected by and hosted on G2.com.

If I were to put my finger on a drawback, it would be managing team rotations. Our staffing shifts more than I would like, and keeping those changes current within the system requires a watchful eye. The escalation features are comprehensive, which is a double-edged sword, since even a minor adjustment can call for several steps. Review collected by and hosted on G2.com.

I really like the incident console features of xMatters, which have made a big difference in how our team handles live incidents. It automatically surfaces relevant history, identifies who owns the affected service, and allows us to draft updates directly from the incident console. This automation is a huge time saver as we no longer need to manually gather contacts and suggested resolvers during an incident response. It's particularly valuable during events with multiple simultaneous alerts, where the quick access to necessary contacts and information shortens the response time drastically. Additionally, the platform's reliability since transitioning to the cloud has noticeably improved, eliminating the maintenance burden of managing updates and infrastructure ourselves. Review collected by and hosted on G2.com.

Our ticketing system required the technical team to write the integration between IT and Smedes because the out-of-the-box connector did not support it. This dependency means anytime we needed a correction or an update to how the integration works, we had to go back to them, which was a reliance on vendor involvement for specific integration. This stands out as an inconsistency for a platform that promotes its low-code approach in most areas. Review collected by and hosted on G2.com.

I find xMatters incredibly helpful in tightening coordination when unexpected infrastructure issues arise. The platform makes it clear which engineer an issue has been assigned to, eliminating the confusion and duplicated effort that used to slow us down. I appreciate the organized communication during service disruptions, as it spares everyone confusion at already tense moments, enabling me to see the acknowledgment status and escalation paths clearly. This visibility means I always know whether an issue is being actively worked on, allowing me to keep customers informed confidently. The initial setup of xMatters was quite easy, and using it alongside tools like Microsoft Teams and Zendesk integrates well with our workflow. Review collected by and hosted on G2.com.

The one area that tests my patience is managing on-call schedules when our operations team rotates. Because our engineers sometimes shift duties depending on the project at hand, those schedules need careful checking within the platform to be sure the right people are the ones being alerted. If that isn't kept up to date, there's room for an alert to land with the wrong person, so it takes a watchful eye. It would help if the platform automatically adjusted on-call assignments when engineers switch projects and gave me a clear visual overview of who's covering what, so I could confirm the right person gets alerted without manually checking after every rotation. Review collected by and hosted on G2.com.

We're very impressed with xMatters and how it allows us to manage all of our global infrastructure's complex incident response processes. The automatic escalation paths guarantee that key alerts on all systems are immediately conveyed to the appropriate persons and with no human intervention. The intuitive drag and drop interface for creating flowcharts of communications is greatly appreciated by our engineering staff. Review collected by and hosted on G2.com.

Set up is extremely confusing, with a long process of complex steps. It is an utterly exasperating process to create a customised report that is frustrating and pushes users to export raw data out into a separate spreadsheet application. Review collected by and hosted on G2.com.

I consider the biggest benefit of xMatters to be the fact that I no longer waste time trying to figure out who should handle an alert. It centralizes all the alerts from our monitoring tools and routes each one to whoever is on duty. The on-call scheduling is rock solid, which won me over. I set up my rotation once, wired it to Slack, SMS, and voice calls, and the system takes it from there. The real strength is the integration. It hooks into Jira, Datadog, Zendesk, and pretty much every system in our stack, so alerts flow where they need to go without manual wiring. The escalation logic seals the deal: if someone doesn't acknowledge a page, xMatters bumps it up to their manager automatically. It means alerts from across my stack land in xMatters automatically, keeping my incident response fast and saving me from babysitting each tool separately. Plus, the initial setup went pretty easily. Review collected by and hosted on G2.com.

The interface is the weak spot. The on-call calendar has a handful of cosmetic quirks, and telling users apart at a glance is harder than it should be. These were sore points when we first rolled it out, and they haven't moved much since. Licensing cost is another thing that gives me pause. Review collected by and hosted on G2.com.

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.