No more typing reviews! Try our Samantha, our new voice AI agent.

Freshservice vs xMatters comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Freshservice
Ranking in IT Alerting and Incident Management
8th
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
40
Ranking in other categories
Help Desk Software (5th), Project Management Software (10th), Cloud Management (12th), IT Asset Management (4th), IT Service Management (ITSM) (4th), Configuration Management Databases (5th), AI IT Support (3rd)
xMatters
Ranking in IT Alerting and Incident Management
10th
Average Rating
8.8
Reviews Sentiment
7.5
Number of Reviews
31
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2026, in the IT Alerting and Incident Management category, the mindshare of Freshservice is 0.6%, down from 1.2% compared to the previous year. The mindshare of xMatters is 6.0%, up from 6.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Alerting and Incident Management Mindshare Distribution
ProductMindshare (%)
Freshservice0.6%
xMatters6.0%
Other93.4%
IT Alerting and Incident Management
 

Featured Reviews

RF
IT Service Delivery Manager at Symposiam
Automation and AI have transformed our service delivery and have made IT support faster and more efficient
I always keep up with Freshservice's roadmaps and new features. Freshservice has been very good at listening to feedback and adding those feature requests into their next iterations. I wish they would offer more granular data export options for utilizing in Power BI, along with predictive analytics for capacity planning and SLA breaches to enable more proactive support management and reduce firefighting. While the dashboards are effective, some users find custom reporting limited compared to ServiceNow or Jira. I would also appreciate deeper integrations, especially for niche apps requiring development coding work to enable advanced orchestration. Native integrations for DevOps pipelines such as GitHub Actions and Jenkins, along with stronger API flexibility for complex workflows, would enhance functionality. Although the CMDB and asset management are solid, they do lack advanced dependency mapping compared to other enterprise tools. My wishlist includes automated impact analysis for changes and improved visualization of asset relationships, enabling quicker resolutions from an agent's perspective when alerts come in. I acknowledge that Device42 may enhance this, but it is an extra cost beyond what we already pay. While Freddy AI is excellent for triage and suggestions, some users desire more proactive automation, such as predictive ticket routing based on historical patterns and AI-driven capacity forecasting. Lastly, the pricing tiers might seem rigid for mid-sized teams, so a more granular add-on option for features such as Device42 or pay-per-use for orchestration workflows could be beneficial.
reviewer1855452 - PeerSpot reviewer
Infrastructure Analyst at a financial services firm with 10,001+ employees
Helps in ensuring that everyone gets notified when needed, and provides the flexibility to integrate it and build what we want on top of it
They recently released an incident module that allows users, or at least teams, to track major incidents and other things, and you can send out communication via that one webpage. You can engage on-call teams and communicate to stakeholders as well, but one thing that is missing there is a group chat. If there is a group chat on the same webpage that all of the support teams could use, it would be a one-stop shop that all of the major incident managers would use as their product to manage a major incident. Without that, at the moment, they are mainly referring to teams and then adding data into xMatters as and when they can. Some of the workflow development work that we do for the in-house piece can be quite complicated if you don't have experience using the tool. You have to have to go through the documentation, but I suppose that's an expectation. When users first log on and they're configuring the rotas, it does take them a bit of time to get their heads around how to configure the shifts. Some of them do need guidance. We have got a support document, and xMatters also has a support page where they can go and read through the details. Our roles and access for each user are locked down, as opposed to just letting them access the xMatters portal because it can add more confusion because the support portal explains that they can do X, Y, and Z. So, we're removing that ability, but once the users get their head around how to configure the rotas, the overall intuitiveness of the UI is pretty good. It is simple and clean, and they don't have to do that many steps. There are probably one or two group supervisors that configure the rotas, and the rest of them log on. We've already pre-populated the contact details from our directory, so usually, they'll just go and add a personal device, if they do want to get called on a personal device, or they want to set up the app, which is pretty easy using the QR codes. The product looks nice and clean. The only thing is that it takes a little bit of work to get your head around the rotas, but once you do, it's pretty darn simple.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It has reduced the time to look up who is responsible for a service, and it has reduced the time to finalize a service request because it now goes directly to the person who is responsible for the service in that location."
"It's very handy and very easy to use."
"The solution has been stable."
"Ability to scan barcodes and a great search feature."
"It has allowed the client to implement service management processes that didn't previously exist in the business and to have more visibility and control of process tickets."
"Its ease of use is fantastic; it is just above and beyond, especially when you compare it to something like Cherwell, Salesforce, or anything like that, and it is on its own level."
"It has reduced the time to look up who is responsible for a service, and it has reduced the time to finalize a service request because it now goes directly to the person who is responsible for the service in that location. So, a service request is handled quickly and directly by the person responsible for it."
"Freshservice has automated a lot of our tasks, including ticket responses and call assignments, which has sped up our operations considerably."
"Probably the most important one is that it persists in attempting to contact to someone until someone is engaged on the event."
"Using xMatters to notify our IT and Emergency Management partners is vital for bringing back IT services and notifying our partners about emergencies."
"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."
"For our major incident management, it has expanded what we can do in terms of the format of the communication. People can subscribe, and they can receive delivery on multiple platforms, whether it's a voice message, email, or mobile app message. It enables us to deliver the right communication to the right people in the format they want."
"Simple features create flow sets and build APIs for integrations."
"​The ability to notify teams and monitor those notifications in real-time is valuable. Time-based escalation of notifications helps us resolve issues much more quickly."
"We're able to communicate better with specific groups or offices. We didn't have that capability or granularity before. It has helped in that regard."
"The two-way integration between ServiceNow and xMatters allows us to assign tickets to support personnel faster and respond to incidents faster."
 

Cons

"Freshservice could improve the delegation and workflow management features."
"You can't implement a complicated delivery workflow. We don't have the same problems with incident and change workflows. It's only for delivery workflow. They have a mechanism for modifying your incident or change workflow. There's a visual interface for that, so there's no reason not to have the same function for request management."
"There is room for improvement in reporting for project management."
"In hindsight, Freshservice isn't the solution we should have chosen, as it's just not customisable enough."
"The only thing I would have against it right now is that the workflow automation is not as granular as we would like it to be, at least for the size of our organization."
"Currently, we can have only one plan per subscription. All users have to be on the same plan."
"Freshservice has limitations in the discovery part of the solution. In order to automate the process of bringing information from your infrastructure to the database of the solution, it has a lot of limitations."
"The reporting and management information (MI) are very limited, and stopped realistic and timely reporting on outstanding incidents."
"When you are not using the conference bridge from xMatters and you are using an external one, it is a little bit hard to get the person whom xMatters calls to jump directly to the external 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."
"Some of the workflow development work that we do for the in-house piece can be quite complicated if you don't have experience using the tool."
"We have to create an Excel sheet for onboarding users and then upload it. But if an employee resigns, we don't have any checkpoints to validate whether the user is still active or not. We have to do that manually every week: Check who has left the organization, and do a cross-check, whether this person had any licenses or signed in to xMatters."
"An additional knowledge-sharing program could be helpful and part of the demo workshops (right now, these only provide partial information)."
"We would like to see 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."
"The user interface could be more intuitive. When you are not familiar with integrations and you're starting fresh, looking for where to begin, it is a bit daunting and not as clear as it could be."
"One of the shortcomings or room for improvement is that their mobile application seems subpar. They could really revamp it and make it function a lot better."
 

Pricing and Cost Advice

"There are some additional costs but not that many. For example, we have unlimited assets, which is something for which we pay extra. We also paid for additional orchestration. I would rate it a three out of five in terms of pricing. They are right in the middle."
"Freshservice's licensing costs are pretty good, and it has different categories of pricing based on what modules and features you choose, which gives a lot of flexibility."
"It was a middle tier. It wasn't an expensive one. It was a tier model usage. Licensing costs varied between admin users and regular users."
"Its price is great. Its pricing is supposedly a lot less than ServiceNow and other alternatives."
"The solution may be around 20,000 euros a year."
"It is good for the price you pay. It has different plans. If you need all features, you need to go for a higher plan. Currently, with the second tier plan, you cannot completely separate the group of agents. So, the agent in each group can see another person's ticket. You also cannot modify the rules based on the viewable, readable stuff and cannot have a custom role in this plan. If you want to do that, you have to go for a higher plan. It works in our case because it doesn't matter if the other group can see our ticket because it doesn't contain anything sensitive. We also didn't need the project or change management features. That's why we didn't go with a higher plan."
"Freshservice is a fairly cheap solution. Though monthly payments can be made towards the licensing costs of the solution, my company prefers to make annual payments."
"I don't think it's expensive for the US or some European markets. Still, when I used Freshservice in Mexico, some customers found it a bit pricey, especially considering the platform's features. I think the pricing is fair for use in the European market, but it might be perceived differently in Latin America."
"This is a subscription-based, SaaS solution."
"This is our biggest issue: licensing. Our customer has only purchased a set number of full licensed users, and we are constantly running up against our license limit. To mitigate licensing concerns, we completely control at the admin level user additions and removals, and do a monthly cleanup process driven by security contractor removal reports."
"xMatters shortens the time to resolution, so the amount saved in potential lost revenue and productivity has justified the cost for our organization.​"
"Then, in pricing, you are limited on your number of SMS messages that you can send a month and the licensing cost annually."
"I am not really privy to how much my client is paying for this service. They just tell me the number of licenses that they have. Every time that I say, "I need extra licenses to make sure that all Level 1 and 2s have their own xMatters account," they keep telling me that it is too expensive. If the only purpose is to call people, it doesn't justify the cost of paying more than the number of licenses that they already have."
"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."
"The pricing is too high... we procured 150 licenses and we have almost 1,500 users in IT. We had to come up with a few ideas for determining which users get a license and which users don't need one. Due to the limitation of the number of licenses, we were unable to integrate the user profiles with Active Directory."
"The cost depends very much on the company's size and usage. We're a very high use case compared to many companies, so we had to consider licensing costs carefully. If we added all our users, that would be 30,000, and that's no good; we wouldn't have been able to afford it. For example, we had to put in customization to sync across on-call users. For the license per user, the price is very reasonable and comparable to ServiceNow when factoring in everything that needs to get up and running."
report
Use our free recommendation engine to learn which IT Alerting and Incident Management solutions are best for your needs.
885,311 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
University
10%
Manufacturing Company
9%
Educational Organization
7%
Construction Company
7%
Performing Arts
12%
Financial Services Firm
8%
Manufacturing Company
8%
Healthcare Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business24
Midsize Enterprise5
Large Enterprise15
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise24
 

Questions from the Community

What is your experience regarding pricing and costs for Freshservice?
I do not have any experience with pricing, setup costs, and licensing, as it was assigned to the infrastructure team.
What needs improvement with Freshservice?
Freshservice has an AI agent that needs improvement for finding knowledge base articles. When issues or incidents are received in Freshservice, new users should be able to receive direct help from ...
What is your primary use case for Freshservice?
Freshservice is used to redirect ticket handling and acknowledge tickets and incidents received. Tickets are redirected with their short description and subject line in Freshservice, which allows f...
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

Flint
xMatters IT Management
 

Overview

 

Sample Customers

Sinclair Broadcast Group, Western Carriers, Judson University, Golf Canada, Travix, Proxama, Paymentez, Ready Auto Transport
Over 2.7 million users trust xMatters daily at successful startups and global giants including athenahealth, BMC Software, Box, Credit Suisse, Danske Bank, Experian, NVIDIA, ViaSat and Vodafone. xMatters is headquartered in San Ramon, California and has offices worldwide.  Visit our website to see how business like yours found solutions with xMatters.
Find out what your peers are saying about Freshservice vs. xMatters and other solutions. Updated: March 2026.
885,311 professionals have used our research since 2012.