xMatters Reviews

We're not using it for the rota aspect. We specifically use it to send communication out to the business and also to arrange calls at the bridge where people can join the bridge. We have integrated it with other applications that we use heavily, such as Workplace by Facebook and Slack. Once we've sent out our communications via xMatters, it sends an email and text message to users or the intended people who are supposed to receive the message. That message is also posted on Slack and Workplace.

It is an efficient way to deliver communication to a large number of users across a number of different applications. It has helped in getting the right information out to the right people on time. We are able to ensure that they all received the information in a timely manner. 

It is helpful for us in getting the communication out to multiple users on different platforms in a timely manner. It brings ease of use in terms of us inputting information only into one system, as opposed to three or four different locations, and that includes being able to contact people. If we need to have everyone on a call, it is easy to open a bridge, and the relevant people would receive a phone call who can join automatically through the bridge.

Workflows and messaging are most valuable. Workflows are very useful. They are important for consolidating information or stopping duplication from happening. We put all the information into xMatters and then the workflow will push the same information in the correct format directly through to other applications that our end users frequently use, such as Slack, email, and Workplace. 

The other main part that we use is messaging. We use it for our major incident communications and our change freeze communications. We also run our testing through there. So, when we're doing test incident communications, we run those as well through xMatters.

We have integrated it with other tools such as Slack and Workplace. It is straightforward to integrate, but the first couple of times, you do need a level of understanding in terms of what you're doing. However, it is not difficult to get that information. There is lots of information held on xMatters knowledge base itself, which is very useful. There is always someone else who has implemented the solution that you are looking for. You can pretty much find anything you need within xMatters. There have only been a couple of instances where we haven't been able to find a solution. In such cases, we contact our account manager, who is very helpful. They help us with any particular difficulty that we're having, but once you are familiar with the workflow builder and how it works, it is very easy and straightforward to create new workflows and integrations.

One of the main reasons why we don't use xMatters for monitoring and alerting is that it doesn't use the rota to call the person who's on-call. It doesn't look up the rota to find out who's on-call and then contacts that person directly. I am not sure if this has changed now, but the last time we checked, this functionality wasn't there. This is one of the main improvements. We're happy with the rest of it.

I've been here for three years now, and it has been used for longer than that.

Its stability is excellent. I've never had a situation where xMatters has gone down at all. I never look at it as a tool about which I'm concerned that it may not work. I'm always able to get access to it. Whenever we needed it, we were always able to get the communication out. It is very reliable.

It is definitely scalable. We have our incident communication that goes out, and we also use it for our business continuity, which is specifically set up for emergency purposes where we are able to send text messages out to the entire company. In terms of scalability, it is highly scalable. It is nice because you can tailor it to your own specific requirements even as they change. The one main thing for us would be the scheduling part of it so that if there was an incident, it contacts the right on-call person. However, our technical teams use PagerDuty for that. In our team specifically, which is the service delivery department, we use xMatters to notify of major incidents.

On our side, it is my team, which is the service delivery team. There are four of us, and then there is the services team as well. So, the services team uses xMatters for business continuity, which is to notify people. For example, in a fire emergency, everyone has to leave the building. So, there are two specific teams that use xMatters: the services team and the service delivery team.

I've never had a problem with xMatters, per se. The only thing for which we contact xMatters is if we're trying to set something up specifically that we cannot find through a knowledge base article. The response is great, and we always get to where we need to be. We always end up implementing the solution that we set out, so we always achieve what we wanted to. So, they provide great support. On a scale of one to 10, I would definitely rate them a 10.

PagerDuty is probably the only other solution that I have used. xMatters tops PagerDuty in terms of ease of use for sending out communication to the business. I like the workflows and the layout of xMatters. It is very easy to use. PagerDuty isn't so user-friendly. The only thing that is better in PagerDuty than xMatters is the scheduling.

I wasn't involved with setting it up from scratch. I've set up new workflows for which you obviously need your users and groups and then you create your workflow with whoever you want to send it to. It's relatively easy. As long as you follow the initial user guide and you have a clear understanding of what you're trying to achieve, you can set up some of the basic functionality easily in order to get going by yourself. The rest is all available in xMatters' knowledge base.

It doesn't require any maintenance. There isn't any maintenance on our side. It's all cloud-based, and we just log in and carry on using it. xMatters does regular updates, and they notify us when there is an update, which is often quite useful. That's it.

I don't make the decisions on the cost aspect. We haven't had any complaints. I think it has a reasonable price. 

My advice would be to have an idea in mind of what exactly you are looking for. You should look at the different ways that other businesses use incident communications because a lot of companies may not think of certain solutions that others are using. So, rather than evaluating the product based on what it can do, it's always useful to see how other businesses are already using it. That's most helpful in my opinion.

Its logging capability is very straightforward to use. It is not difficult, and it is very informative. From the information contained within the logs, it is not difficult to find out where the failure occurred. We don't use xMatters logs as part of our operations. We only use logs to find out if we've implemented something that doesn't work, or when something breaks and we're trying to figure out where exactly it has gone wrong. They come in handy when we are trying to figure out where something has gone wrong, or when specific people have run certain tests, they are used to see which messages were sent and when. So, mainly, we use logs when there is an issue in xMatters, and we need to figure out where it failed.

We don't use call scheduling and rota aspects of xMatters. We also don't use coding to expand the flexibility or functionality of xMatters workflows. We used to have to do some coding, but once there was the introduction of the workflows, it kind of eliminated that side of it, so we didn't need that any longer.

xMatters workflows haven't helped us to address issues proactively. That's because we don't use it in that way. We don't use it for monitoring. It is only for alerting but not in terms of incident management or our teams being alerted of an incident. It is only in terms of alerting staff members of an issue or an incident. So, within our setup, we don't use xMatters for monitoring.

I would rate xMatters IT Management an eight out of 10.

This solution integrates with the service desk tool to allow for the appropriate notification of support teams. You can set up a queue of people and you can assign their devices, their priorities, and the order in which they are called. It allows for shift work and it can all be automated once it is set up. If somebody has to be contacted then it happens automatically through the interface.

The system works by allowing for support queues, where you can define who is available and who is on-call. Then, based on ticket priority, you can define what kind of notifications take place. For example, if it is an urgent ticket or a priority-one incident, then you need to make a phone call. In contrast, if it is something minor for one individual, then it's typically going to be an email and that's the extent of it.

The automation provided not only expedited communication, and therefore the ability to address issues, but also ensured that the data used for communication is managed.

The most valuable feature is the automation because it reduces the demand on resources. It automates the escalation of a ticket if the person doesn't answer within a certain amount of it, and it passes it on to the next person. People are required to respond, for example, by pressing the one key on the phone to acknowledge the call. If it was an email then it would require a reply or similar type of acknowledgment.

Having this level of automation is a great benefit to being able to more quickly contact people. It reduces the amount of oversight required, and consequently, the amount of time to assign and get a response on a ticket.

The integration with other systems needs to be more flexible.

The interface is a little bit rigid and can be improved. For example, it tends to operate on the attribute of a record. So, if a group has a name, it tends to want the group names as opposed to, for example, the ID of a record. It creates a problem because if you rename the record then you lose all of the connections.

The data validation and verification need to be enhanced so that when data is changed, it reviews it in an automated manner and catches all of the anomalies. Otherwise, all you're doing is shifting the workload from an operational standpoint to an administrative one.

We began using xMatters IT Management in 2014.

PS, I am no longer with the firm and do not know if it is still in use.

This is a stable solution. This system runs 24 hours a day, every day of the year, and stability is not an issue.

This solution is fairly scalable. In the organization where I had this running, we were handling up to 150,000 incidents per month. There were 5,000 incidents a day and an IT staff of 1,000 people. I'm not sure if it would even be cost-effective in a smaller organization.

I would say that their support is above average, although not exceptional. It depends, in part, on who you were speaking with. However, part of the reason that we sometimes struggle with support is that we are outside of the norm for what is expected.

The initial setup was complex. The reason for this is that the interface is not as sophisticated as our needs.

The configuration is partly done in the service desk tool, where it gathers the contact information or it reads it dynamically. xMatters stores the method and the parameter for contact. As an example, if the method is to contact via email then the parameter would be the email address. If the method is a phone call then the parameter would be a phone number. You can set up other methods, too, depending on how sophisticated your environment is.

Implementing and deploying the system took six months to complete, including testing to makes sure that it worked.

The cost of this solution was less than the cost of staff required for the same job, so it is saving money.

This is a subscription-based, SaaS solution. There were some additional costs during the implementation because it was well beyond their standard configuration.

At the backend, this service is initiated internally, but the notifications and alerts are sent externally to the vendor through web service calls.

My advice for anybody who is implementing xMatters is to be sure that they have a very clear plan on how they want to process whatever communications they're doing. The tool can do almost anything but you have to come to the table with the process well-defined, before you being implementation.

I would rate this solution a seven out of ten.

To notify our employees of system events that might result in an outage on our website.

It has improved our time to respond. Prior to the use of xMatters, it might take hours or even a day to get someone involved on a problem. Now, it's down to minutes.

Probably the most important one is that it persists in attempting to contact to someone until someone is engaged on the event.

Then, of course, there's the ability to define rotations and schedules for people who would be on call to handle those events.

The ability to support custom devices. We have a lot of users who use Slack, which is another tool for communication. xMatters currently does not support Slack as a communication method. It can't send events to Slack and respond to them.

Three to five years.

We're using their cloud-based service or hosted service. We've never had any problems.

We've never had any issues with scale. It's always met our needs.

I would give them an excellent rating. They've been extremely responsive and always work an issue until it's fully resolved.

We did not have a solution prior to xMatters.

We've always used their hosted service, so we've never had to set it up. The only thing we have to do is train our users on how to use it. It's been pretty easy to do so. They've actually made many improvements over the years to make it even easier to train people.

It is worth the cost.

You need to know the number of users that are going to use it, which is usually pretty easy to calculate. It's on a per-user license.

We evaluated two other solutions. One was an internal solution that was provided by our IT department, it was a proprietary solution. Then, we also evaluated xMatters vs PagerDuty. We chose xMatters because of its cost and ease of use.

DevOps means that the person who's developing the software supports the software. When an event occurs that might result in an outage, xMatters engages people on that event so they can resolve it before there's an outage.

Certainly, it's been a very stable solution, very reliable, very flexible. It comes from a company that practices Agile development, so they're very fast to deliver new features, as well as any bug fixes, should any arise. I think the only challenges we've ever run up against is some compatibility with mobile devices and the providers they've had. Usually, that's the mobile device provider's problem, not xMatters'.

I would give it a nine out of 10, only because there are some devices that are not supported.

We no longer have to manage the notification process manually.

• The ability to notify teams and monitor those notifications in real-time.
• Time-based escalation of notifications helps us resolve issues much more quickly.

Some features that have been around a while could be refined or updated, in the same way other features of the product have been updated.

Beyond the typical grouping, xMatters has what is referred to as dynamic teams.  Dynamic teams are criteria for setting up and targeting a group of people that meet specific criteria. The good thing about this setup is that you do not have to specifically target a person, or add them to the team. If they meet the criteria that has been configured for that dynamic team, the user will automatically be added to that team, and receive the notification.

The bad thing about this setup is that you cannot alter those criteria through the typical xMatters import/export process. The attributes that create the criteria for dynamic teams can only be altered via the Web UI.  So, if you want to create a new dynamic team in a mature xMatters environment (one that is already populated with hundreds of users), and you want to add, say, 100 users to that dynamic team, you have to do it manually.

In contrast, if you want to alter a custom field, you can do so via import/export. But you can't have an unlimited number of custom fields, so in a large environment with a lot of teams, team provisioning becomes more difficult.

If custom attributes could be exposed to the import/export process, provisioning of these dynamic teams would be much easier.

Three to five years.

No issues with stability.

No issues with scalability.

Technical support at xMatters is very responsive and knowledgeable.

There were some issues with user-adoption, but those have been mitigated over time.

Licensing varies widely, depending on usage. It can be cheap or quite expensive, depending on volume and features.

Put together a comprehensive knowledge base to help your end-users get acclimated with xMatters.

We have two primary use cases. One is alert notification and escalation. The other is major incident notification.

In the past, when there was a major incident notification, which is an outage for one of our products, we had one tool that we would use for email notification to our internal stakeholders, another tool for a voice blast going out to their phones, and then another tool for a conference bridge. All of those needed to be kicked off individually and managed individually by our enterprise operations center. It was very difficult to manually maintain call lists - who was on call when - and up-to-date contact information. So, when there was an outage, we didn't have the right people on the bridge, it took forever to get people on the bridge, it took us a long time to notify people there was an issue.

By using this tool, it's a one-stop shop. Through one tool, we're able to generate email notifications, voice notifications, mobile push notifications, Slack channel notifications, all managed from one place, simple and easy to use. People are able to join the conference bridge directly from the phone call by pressing one button instead of having to dial into a bridge and remember a conference code.

Everyone's contact information is up to date, people are able to go in and update their contact information and even set things like when they're going to be on vacation and who their backup is. 

It has dramatically cut the amount of time that it takes to get people assembled during a major incident.

Its ease of use and self-service are important to me. It's very easy for users to go in and modify their own contact information, for managers to go in and manage their own on-call rotations and shifts, so that is a very valuable feature to me. 

And the ability to notify and get everybody on a conference call, rapidly, is also very important. 

It serves as our communication hub. We're able to point all of our alerting tools at xMatters and have it route alerts to the right people at the right time. We're able to generate major instant notifications for product outages, get all of our people on the bridge at the same time, and include information from our monitoring tools with that. So everyone is speaking the same language and seeing the same information.

We're able to route those notifications not only to people, but also to other tools like Slack channels, where everyone can get in and collaborate.

While the documentation is good, the knowledge base - the collection of user supported community forums - is a little weak compared to some of the other products I've used. If I have a problem that I can't find the answer to in the documentation, there are very few places to go after that, because the user base, the community forums, are not strong for me to find someone who's had the same issue as me, and find out what the answer to their problem was. That's somewhat of a weak point.

Regarding issues with stability, none that I can recall. There have been some scheduled maintenance and downtimes, of course, but we've always been told ahead of time and have been able to plan accordingly. I honestly can't recall an unscheduled outage that we've experienced with the product.

In terms of scalability, there haven't really been any issues. We use the On-Demand version, which is the cloud version, not the on-prem, and we've never had any issues with the scalability.

Maybe, if there are a lot of people to be notified during a particular incident - if we're talking a couple of hundred people for instance - it takes a little while for everybody to get called, which I would expect. But I've never really thought about that as a scalability issue. In the end, everyone who needs to get notified gets notified.

I've used tech support a couple of times. I have worked with support before, to change permissions and roles that we don't have permissions to change, but mainly, when I do have questions about actual solution implementation, I typically will work with our technical account manager, and reach directly out to them and not go through support. And that's been successful for us.

We originally used a tool called AlarmPoint. We used it for about the first year and a half I was here. We were planning on punting it because it wasn't very useful, and when we contacted the team to tell them that we were going to not use their tool anymore, they said, "We're no longer AlarmPoint, we're xMatters, and the tool that you're using is years old. Why don't you see what our new tool can do?" That's actually how we were introduced to xMatters. So, we previously used an old iteration that was very outdated.

We also did use PagerDuty a little bit, which is a competitor of xMatters. And the reason we chose to go with xMatters over PagerDuty was that, while both were very good at alert notification and escalation, when we did our assessment, PagerDuty did not have the ability for the major incident notification process that we needed to implement as well. It's more just for alerting on-call people when there is an issue with the server, and not necessarily for assembling a large group of people, whether they be business, technical, management, on a bridge to actually provide information and collaborate.

It was pretty easy. It took a little while because we have a lot of products and a lot of different teams that need to be notified for different products, and a lot of different policies. The implementation wasn't difficult, it just took time.

I would definitely say it's worth the value. I wouldn't say it's expensive, but most people who pick xMatters are not going to select xMatters based on price. There are other lower-priced competitors that are out there. But I would say for what we're getting, it's worth the money.

We did evaluate PagerDuty, as I mentioned earlier. We had originally evaluated directly PagerDuty against xMatters, and we used each of the tools for about six months on a smaller scale, and ultimately we found that xMatters was going to be the right fit for us. That's when we really expanded the usage and bought a lot of licensing.

I would say, before you begin with implementation, you should really have a good idea of what your notification standards and policies are. Completely irrespective of a tool or technology, if your process isn't rock solid, and if you haven't really thought out your process and what you're trying to achieve, it's going to make it much more difficult to try to implement the product itself.

So before you begin implementation, really plan ahead of time. Understand what it is you're trying to achieve, understand how you're going to measure the success of the project, and have all of your standards and policies laid out beforehand. It will make the implementation that much easier.

I would say it's a nine out of 10. And to bring it up to a 10, once again, if the user community knowledge base forums, were a little better, and it was easier to find answers to some very difficult questions without having to engage our technical account manager, I would give it a 10.

• Major Incident Management
• Hosting conference bridge calls.
• Managing IT Support on-call schedules.

We have reduced the time it takes to resolve major incidents through xMatters’s conference bridge management solution. Instead of a service desk agent sending an email or manually calling multiple resources to join a bridge, xMatters directly calls the appropriate resources simultaneously. In addition to streamlining the conference bridge process, xMatters fully logs all notifications to show who was contacted, how they were notified (phone call, text message, email, and push), and if they responded. This helped change behavior across the organization to improve accountability.

Conference bridging and on-call schedule management. xMatters allows us to define scenarios that notify only the necessary people when we need to open a conference bridge.

Reporting is the weakest point of xMatters. Since xMatters has very limited reporting and only maintains logs of events for a short period of time, we export event and conference logs to our ITSM solution, so we can maintain event history and link it to Incidents.

We have had a couple occasions where xMatters was not available, but these were short events. For business continuity, we backup all users and schedules to an Excel file weekly.

No. We chose xMatters over other products because we felt it could grow with our organization. We have expanded its functionality, but there are still features we plan to use later, like geographic location-based notifications.

Technical support is very responsive. We have needed assistance building forms and have always received prompt and knowledgeable responses from xMatters support.

We had no prior solution.

Initial setup was fairly simple. The biggest challenge is that you need to define your process first, which is true of any tool (rules before tools). xMatters is a fairly open sandbox, so it can seem a little overwhelming until you start to dig into it. We started with a simple goal of hosting conference bridge calls through xMatters, then evolved it into targeted conference bridge scenarios based on the priority and system impacted.

You pay for the user, not the number of alerts. Therefore, xMatters provides a better ROI, if you can leverage it for notifications based on alerts from other monitoring tools.

xMatters is pricey, but you have to consider what a critical incident costs your organization. xMatters shortens the time to resolution, so the amount saved in potential lost revenue and productivity has justified it for our organization.

We evaluated HipLink, Everbridge, and PagerDuty.

xMatters had the best interface and the most functionality.

Consider the functionality you are looking for based on your organization’s need. Also, consider the integration options with your ticketing system and other alerting systems your organization uses. 

We use xMatters for alarming infrastructure outages and failures of batch jobs (post-processing).

• xMatters made it easier to implement our roster of people who receive alarms using the REST API. 
• The cloud solution reduces alarming to the core, which means no need to provision your server, which is great.

• The REST API has given us the chance to move away from manual work to fully automated updates. 
• The app gives way more information than a standard text message, making it more comfortable to interact with.

• The REST API is still missing some important functionality, which we require. 
• If you are not one of the big players of their customers, the chance that one of your minor wishes will granted are very small.

The tool itself works well, but when you try to apply real world use cases against it, it comes down a rating scale quite significantly (hence why it is a five out of 10). The feedback we get from our team managers to modify their schedules, it is very complex, hard to use, hard to navigate, and reschedule things. Therefore, my team ends up having to do this. From a scheduling standpoint, this is actually causing more work than what we had with Excel spreadsheets.

It has not improved our organization.

• The UI: It is easily navigable.
• For our organization, sending notifications out via subscriptions for outages.

• On-call management scheduling is difficult. 
• We would like to see the integration between our ITSM solution and xMatters.

We have had outages with the product. We have experienced functionality (defects), such as conference bridges can only be opened for four hours at a time and people get kicked out. That has caused some issues during some of our longer outages.

We have not contacted tech support regarding this, because usually by the time we get a chance to do it, the system is already back online. We have had some outages in the Asia Pac region. We have had only about two outages in the North America region regarding messaging. Most of the outages have been in the European or Asia Pacific region.

If you are willing to pay for the licensing of it, it is able to scale out. Also, the integration that they currently have with ServiceNow is very limited.

The customer service is quite responsive. They are quick to answer your calls or emails. They do provide good support. Even the customer service tech support side of things is fine.

It was complex in that the integration was very basic in order to apply it to real world situations. It had to be significantly customized and we have three integration points right now with our one ticketing tool which only handles for incidents. It does not handle any of our other processes. It is also very complex in that xMatters does not have the ability to clone what I have built in production back to our Dev environment to do any other further testing or development of the tool. It all has to be manually created and manipulated. So, that is a huge miss.

I do not think it is worth the value. I think it costs too much. It does not do anything significant over what some out-of-the-box functionality of the ITSM tool can do.

I would advise people to really look at their use cases to make sure that the scheduling portion of it meets their current business requirements as far as rotation goes. This tool works great if the team rotates on a perfect rotation. If it is a small team, it will rotate weekly or rotate daily. If you have any complex leave through it at all, it will not work very effectively. Then, you have to apply bushwhack-type solutions to it.

Then, in pricing, you are limited on your number of SMS messages that you can send a month and the licensing cost annually.

This product was already purchased by the time I came to the company. I just had to implement it. Because of budget and our mandatory upgrades in ServiceNow, we just have not had time to devote to developing the functionality within ServiceNow.

Be very careful on what type of use cases you have. It is going to require a lot of customization in order to meet real world requirements for sending out notifications. It seems to work decent for major incidents as long as the major incidents are short and sweet. 

Again, it does require custom code to notify on subscriptions and a limitation on your subscription templates is an issue as well.

We use this tool for our primary IT and Emergency Management notification tool. We use it to send incident notifications from ServiceNow. Our datacenter command center uses xMatters to send out outage and emergency notifications. 

The automation of the tool and the way it integrates with ServiceNow has improved out IT operations. Also, users can manage their own devices, which has saved our datacenter time because they do not have to manage on-call devices or rotations anymore. 

Using xMatters to notify our IT and Emergency Management partners is vital for bringing back IT services and notifying our partners about emergencies. Having our users manage their own notification devices within xMatters is huge, since it takes the burden off our datacenter. In the past, the datacenter would have to keep up all the on-call lists and rotations. Now, it is all automated in xMatters, which is a huge win. 

We have a two-way integration with ServiceNow, so incident notifications go directly to xMatters. Then, when the on-call person accepts the notification, it communicates back to ServiceNow and updates the ticket with the person who accepted the xMatters notification and puts the state to work in progress. This automation allows our datacenter to see the ticket has been accepted and is being worked. We also key our SLAs off the incident ticket being accepted and work so it keeps everything running smoothly. 

I suppose there is always room for improvement, but we have been very happy with the product. I suppose they could make the product more customizable, but they have been working on this with forms and scenarios that you can modify. We have not really taken full advantage of this new feature since we went from on-premise to the xMatters SaaS version. 

We have not encountered many stability issues. There was a couple times in 2017 where notifications were delayed, but this was resolved quickly by xMatters. 

No issues.

Support has been great. They responded very quickly to all the support cases that I have submitted.

No, we did not have a previous solution. We have always had xMatters and have been satisfied with the product.

The SaaS solution was straightforward, but we did have to migrate all of our on-premise data to the cloud (xMatters helped us with this). The integration with ServiceNow required some configuration changes, but they were not too complex. 

I do not get involved with pricing, since I am on the technical side of the tool.

I can’t remember if we evaluated others. It has been 16 years since we purchased xMatters.

I would recommend them to use the SaaS solution and tie it into their ITSM tool.

On-call notifications.

This has made it much easier to send notifications to a group or individual, as you just need to know the name and the message to send. xMatters handles the communication methods (phone numbers, preference of text, email, phone call, etc.).

One of the most valuable features is the integration with our ITSM solution. This allows P1 and P2 incidents to automatically do notifications to the group that they are assigned to. The groups can maintain their on-call rotations and methods of notification in xMatters. This will automatically go through a list until an alert is acknowledged, which will assign an incident to the person that acknowledged the alert. 

Having this automated has led to a significant improvement in incident resolution time (resolution can now occur quicker than the time to previously contact the correct person). All attempts are also logged to determine what occurred when and if they are successful or not.

Being SaaS-based is also a plus. Regardless of the state of our network or infrastructure, xMatters will still be available via a mobile device.

Integrations seem to be the most difficult part. Once setup though, they work well.

No issues.

No issues.

Good, but not excellent. They are courteous and professional, but may take longer than desired to resolve some issues. Integrations may require professional services.

We used manual methods previously, so this was a great improvement.

As this is SaaS based, xMatters does the environment setup. Adding users, groups, and on-call rotations is pretty simple. Roles are a little confusing as they seem to have too many. 

The most complex parts are the integrations. For us, this was the integration to ITSM and LDAP, both of which we used their professional services for.

Pricing is pretty straightforward and listed on their website. I recommend starting small and expanding later.

No. One of the biggest issues for us was an ability to integrate with our ITSM solution. As xMatters is a partner of our ITSM vendor, integration was not a concern. Being totally SaaS-based was a big plus. I have worked at other places that used xMatters and were happy with it. With reasonable OpsEx pricing and a product that met our needs, we did not feel the need to evaluate other options. I have used other notification solutions at other companies, and this is one that I am most familiar with.

It has been easy to use and very reliable.

The only potential concern is professional services. They are capable, but like to bill on an hourly basis. I would recommend having what you want them to do clearly defined upfront and keep close tabs on their progress as the hours can go by quickly if you do not keep on top of them.