We performed a comparison between OpenText Service Manager [EOL] and ServiceNow based on real PeerSpot user reviews.
Find out what your peers are saying about ServiceNow, Atlassian, BMC and others in IT Service Management (ITSM).
"Service Manager does what it should, but it's quite outdated."
"The initial setup is easy."
"Incident management is the most valuable because we're using it to manage tickets for an accounting system. With the reports that are available, it allows us to track and identify trends at the type and item level. It also helps us in managing the workload better than what we had in Remedy, which is what we were using before 2013."
"The solution will streamline productivity and also improve automation. That would bring efficiency as well the ability to handle a big number of enterprise-wide service needs. Productivity and collaborative capabilities are some of the key benefits."
"Service Manager's best features are flexibility and customizability."
"Sometimes, customization is simple. The version we are using now has a nice interface."
"It's pretty well-structured in modules."
"Service Manager gives us a single system where everything is centralized in one base."
"It's easy to integrate. For instance, yesterday we closed the integration with SAP for the IP business management module to manage the forecast of projects. We created an interface between ServiceNow and SAP to control projects for accounting and on the forecast of the project. It was really easy. We don't have any problems with ServiceNow at the moment. As a company, they are improving constantly."
"There are lots of modules around IT service management such as IT business management and human resource management (HRC)."
"We have found change management and CMDB to be very useful."
"ServiceNow is easy to use and has a user-friendly interface."
"I prefer ServiceNow to the competition because of its ease of use, installation and configuration."
"ServiceNow has been implemented to streamline team workflows across different departments in our company. Users, including traveling leaders, were able to approve requests and authorize additional rights through the mobile platform."
"The flow designer feature of ServiceNow has had the biggest impact on our productivity because it has helped me reduce manual efforts by creating automation and robotics."
"It's a straightforward and effective approach that minimizes the need for extensive explanations."
"We aren't able to take emails that come in and turn them into tickets, especially when it comes to attachments. When an email has an attachment, like a screenshot, it is a very cumbersome process, and it does not work very well. I shouldn't have been paying technicians to cut and paste attachments from an email into the ticketing system. It should do that automatically. Other solutions are able to do that. This is something that needs to be improved. Test manager and knowledge management areas are probably amongst the worst parts of this solution. We try to use this solution for knowledge management, but it is not user-friendly. Therefore, it has limited ROI as you need to spend time to try and fully capitalize on the knowledge management system."
"The solution does not interface well with other products and is difficult to implement."
"With the new version moving toward the codeless configuration is good, but it's losing flexibility."
"I think one area which is the most painful from my point of view is if you need to integrate a lot of the tools, and being able to make that a lot more seamless."
"The product's technical support services need improvement."
"The user interface is very clunky. It's only now beginning to be a web-based interface, but for now it's still very clunky."
"There's a lot of manual work, which is error prone and time consuming, in how the code gets transported from one system to the other."
"It needs to be easier to use for the end users because one problem we had was that we are handling different kinds of cases."
"ServiceNow's mobile app should be seamless and it is not right now."
"There should be fewer clicks and faster integrations between solutions."
"The level of complexity and the level of discovery are the two areas that can be improved. Its UI needs to evolve. They focus a lot on cool colors and other little things, which don't bring value in terms of functionality. They need to focus less on presentation and more on the functionality within the UI. Its discovery mechanism should be improved. There is a component in ServiceNow that discovers the assets, but it doesn't do an immediate discovery, and there is a lag. If I want to open a ticket for a laptop or an asset, that asset needs to exist within ServiceNow for me to be able to say that I need to have its disk space or memory increased. It is referred to as a CI or configuration item in ServiceNow. Sometimes, ServiceNow doesn't discover these items, and as a result, I cannot open a ticket and tag that system or asset. If a system was introduced to the environment last week and it is still not listed, it becomes a problem. I will either have to wait or manually enter that system or asset. So, if I have a laptop with only 8 GB of memory and I want to request 16 GB of memory, I won't be able to do that in ServiceNow because my system or asset hasn't been discovered yet. Discovery is not immediate, and there is a lag."
"This solution needs to be improved for global use. Currently, it's very oriented to the processes and needs of the US customer base, like their compliance solution or GRC (Governance, Risk, and Compliance), and not so much for customers from other parts of the world. Some users may like the things that ServiceNow is improving, but those are very oriented to users based in the United States and Europe."
"The capital expenditure neeed to get the tool up and running is extensive."
"I would like to see more functionality in terms of custom workflows, not impacting the overall platform health."
"It should enhance its offerings by providing the chance to obtain course certifications at an affordable fee."
"Complexities in the organization made the initial deployment complex."
More OpenText Service Manager [EOL] Pricing and Cost Advice →
OpenText Service Manager [EOL] is ranked 12th in IT Service Management (ITSM) with 48 reviews while ServiceNow is ranked 1st in IT Service Management (ITSM) with 212 reviews. OpenText Service Manager [EOL] is rated 7.2, while ServiceNow is rated 8.4. The top reviewer of OpenText Service Manager [EOL] writes "A solution that works out of the box. The solution's real strength is its ability to change for your organization's infrastructure". On the other hand, the top reviewer of ServiceNow writes "A stable and scalable solution that has excellent features and is useful for collecting data and building KPIs". OpenText Service Manager [EOL] is most compared with JIRA Service Management, OpenText Service Management Automation X (SMAX), BMC Helix ITSM and IBM Maximo, whereas ServiceNow is most compared with BMC Helix ITSM, Microsoft Power Apps, Pega BPM, IBM Maximo and Appian.
See our list of best IT Service Management (ITSM) vendors and best Help Desk Software vendors.
We monitor all IT Service Management (ITSM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
