ServiceNow Reviews

We use this solution for incident management, change request management, and service request catalog. These are our three primary use cases.

Within our organization, there are roughly 15,000 to 20,000 employees using this solution. We have two staff members that handle all maintenance-related issues. 

As our mission over the next couple of years is acquisition, we definitely plan to increase our usage of this solution. 

We aligned several different service desks onto one platform. There is a cost savings in not maintaining multiple systems. 

I find the incident management part to be the most valuable. That's how the service desk tracks tickets.

They could be more competitive with their licensing. We went to roll out asset management discovery and at the time they charge per network device only and you didn't get a price break until you were at 5k devices. To me, I would change the licensing to discovery of all devices. We made do with SCCM instead, but the limitation with using that is that we can only discovery over one domain. 

CreatorCon is an event for Servicenow customers to show off what they've done with the tool. Servicenow benefits because they can partner with the customer to make a solution a permanent solution in the tool. 

I have been using ServiceNow for 11 years. 

In the 11 years that we've been using it, it's not gone down more than once; and we started with just one help desk on it — we now have five.

If you get the right person, the technical support is pretty good. 

We used to use E-Service — it was horrible. 

Deployment took four weeks. 

A vendor helped us with the implementation. That made things pretty easy. 

Our licensing is on a yearly basis. We normally end up doing a true-up payment because we tend to acquire more people and use more licenses.

Yes, Remedy (Salesforce), SysAid, Cherwell, TopDesk. Cherwell came in a close second. 

My advice is to use a third-party vendor to help with the installation. Keep in mind, some are good, some aren't. You would have to send your staff away for training for about six months before they could even attempt to implement this solution. 

Overall, on a scale from one to ten, I would give ServiceNow a rating of nine. There's always room for improvement, but it's the Cadillac of ticketing systems.

We use the product as an incident management tool and receive alerts via email. 

In my experience, ServiceNow's most valuable feature is its flexibility. If you have a DevOps or development team, you can customize it to meet your specific needs. The tool's dashboard categorizes incidents, making managing it much easier.

The installation and deployment of ServiceNow can be a bit challenging. One major issue I've encountered is that ServiceNow doesn't provide the same mobile responsiveness or features that we used to enjoy with other tools. For example, with Splunk, our response times were about five minutes, and we could manage alerts and incidents directly from our mobile devices.

Our development team has been trying to implement similar functionalities in ServiceNow for the past three to four months, but so far, these features have not been successfully integrated. Splunk even provides a wireless call feature from the mobile. 

I have been using the product for three years. 

The tool is scalable. My company has 80 users. 

We haven't contacted the technical support team yet. 

The solution is expensive. 

If you're starting with ServiceNow, you don't need to worry too much about documentation or complex setups at the beginner level; it's not overly difficult. I'd advise you to start exploring it. Focus on customizing your homepage to suit your needs using ServiceNow's filters. For instance, if your homepage currently displays twenty fields, you can adjust the filters to show only the five to ten fields most important to you.

I rate it a nine out of ten. 

The most valuable features of the solution are the ease of use and the sensor for ticketing systems. In terms of the reports generated out of the metrics, specifically operational metrics, along with the dashboard, are very good in ServiceNow.

From an HR standpoint, if users can have a very integrated onboarding or offboarding process between ServiceNow and Workday, then it can give a very good employee experience.

I have been using ServiceNow for four years. I am a customer of ServiceNow.

I have had no issues with the tool breaking down or bugs. Stability-wise, I rate the solution an eight out of ten.

I had no issues using the tool's scalability feature. Scalability-wise, I rate the solution an eight out of ten.

In our company, we have formed an in-house ServiceNow support team to help us.

I have no experience with other solutions before ServiceNow.

The product's initial setup phase is a bit technical in nature.

The solution is deployed on the cloud.

The solution can be deployed in six to twelve months.

My company has a dependency on ServiceNow partners who can be part of the implementation process.

To those who plan to use ServiceNow, I would say that it is always good to use the system for case management. ServiceNow is a platform that allows a company's customers, including the employees and stakeholders, to connect with the services revolving around HR or digital technology.

I rate the overall tool an eight out of ten.

We use ServiceNow for configuration management. We're currently setting up the CMDB as well as the help desk.

Flexibility is the most valuable feature of ServiceNow, that is, being able to modify it to do what we need it to do.

The biggest complaint I have is that the ServiceNow search engine is not very robust. The term has to be typed correctly. It has to be exact. For example, if you misspelled a term in Google, it will give you suggestions indicating that this is what you may have been looking for. ServiceNow does not do that. I would like to see something like that. It would make it a lot better and a lot easier to use.

I've been using ServiceNow in total for about four years.

The solution has not gone down yet.

So far, the scalability has been very good. We have not run into anything that we can't do yet.

We hired a company to do the initial deployment.

My advice would be to have a good plan to start with. There's a lot you can do with ServiceNow. Therefore, plan out what you want to do, and then you can always revise your plan. Don't go in there blind, but know what it can do.

On a scale from one to ten, I would rate ServiceNow at eight. I'm very satisfied with it, but there's always room for improvement.

Many organizations use this solution for event management. They integrate their monitoring systems with ServiceNow for events and incidents. ServiceNow is also used for the automation of tasks such as the launching of AWS or Azure.

Operations and maintenance costs have been reduced using this solution. We have been able to deliver faster solutions to our customers and track progress using live data. 

ServiceNow is a platform you can use to build an ecosystem. It will help your finances models and can be used for ITSM and ITBM.

I have been using ServiceNow since 2010.

This is a stable solution. 

This is a scalable solution. 

This solution offers good customer support. If there are any issues, their engineers will guide you on how to solve it.

Positive

I am an expert and know how to gather requirements and complete implementations. The initial setup is not complex but someone who is new to this technology, may need assistance from an expert. The time it takes to deploy the solution depends on an organization's requirements. If they want to only implement event management, the timeline would be shorter.

We required an internal architect for implementation and one project manager to maintain the solution. We needed four ServiceNow senior developers and a ServiceNow QA for testing. For a bigger organization, you would need six people. This depends on the number of completion items. If you are using between 100 to 200 completion items, it is easier and you may need fewer people for installation. If you have more than 40K completion items, you would need six to 10 people. 

We have seen a return on investment within three to six months when using this solutions. 

The licensing cost is based on your partnership with ServiceNow and what you have selected for implementation. There is an annual license cost which is calculated based on your number of devices.

You cam purchase ServiceNow for approximately $60 along with one additional day environment, one pro and one day. The ITSM license will be calculated based on the end user and is free of charge. It depends if you are purchasing the enterprise ITSM or standard ITMS. Once you connect with the ServiceNow account manager, they can explain exactly how this will work for your business. 

Before implementing this solution, you should have the ITSM model in place for chain management requests. That is a prerequisite because you cannot perform tasks without it. 

I would rate this solution a seven out of ten. 

I have two primary uses of ServiceNow:

1. As our ITSM Platform for providing Application Managed Services (AMS) to Enterprise clients who have solutions on Oracle, Workday, Coupa, and ServiceNow.  NOTE: Other groups within my firm also use ServiceNow to provide IT Service Management to clients on Microsoft, SalesForce, and other major vendors.  We have multiple production instances for delivering Service Desk support to various client install bases, including this one for my above mentioned AMS business.

2. As the ITSM platform for our internal, global support framework. This is a separate instance of the one I use for my UK clients and is 'owned' by our US member firm. Said US firm uses this instance to support not only our internal global Management Consulting business but also to provide AMS to US-based external clients.

ServiceNow has enabled us to rapidly deploy Application Managed Services for new clients, with the ability to configure, extend, and tailor our ITSM Platform to meet individual client needs. ServiceNow's multi-instance model helps enable that flexibility. For example, we recently took on a new Workday client by modifying our ServiceNow instance (configurations and workflows) within 5 months, with successful go-live afterward.

ServiceNow has also enabled our Management Consulting business to provide Digital Transformation services for our clients the world over, as we use the platform as an accelerator for doing IT Target Operating Model transformations.

ServiceNow's Customer Service Management (CSM) Pro & DevOps modules in particular - including ServiceNow's strong interface APIs (to Jira in particular in my case) - have allowed us to:

1. Automate some of the more menial tasks while accounting for our need to develop 

2. Deploy a lot of new features and functionality that get continuously and rapidly introduced by the major vendors via their regular upgrades (e.g. Oracle 4 times per year, Coupa 3 times per year, Workday 2 times per year, etc.).

There are no outstanding gaps or deficiencies that I face at the moment for my business or operational needs. That said, I am interested to see the firm's strategic plans for Artificial Intelligence (AI) and Machine Learning (ML), and how the particular areas it will expand on from its existing investments (that feature, for example, in its ITSM Pro and CSM Pro modules). Our AMS business will benefit from further automation of the more mundane tasks as we continue to develop the platform's configurations - including the streamlining / automation of our change control workflow for faster deployment (critical when tackling the very frequent upgrade cadences of Oracle, Workday, Coupa, etc.).

4 years

Very stable so far. I have yet to experience an outage of any of the ServiceNow instances my operations/teams use.

Scalability is good on the production side. It could be better performance on some of our lower environments, notably UAT for our global support estate - although I suspect that is partly down to how our Dev team manage their workloads and the access set up they have (too many users floating in/out?). I have not called for an audit however, so my view here is not qualified.

Minimal need for support - from my personal vantage point - and for the few times we have needed support, the turnaround time and quality of support has been good.  No complaints.

We used Jira initially for our internal Help Desk platform, but it fell far short of needs for the underlying service management workflows we employed.

I entered into already established estates, so was not exposed to the efforts in setting up the ServiceNow instance sets.

All has been in-house. We have full capabilities, as we do service implementations of ServiceNow for our clients and have invested in having internal development and support skills/capabilities.

We moved directly to ServiceNow for two reasons:

1. It was already the production ITSM platform for our US member firm who was given the (internal) contract to support our global management consulting business; and

2. We knew from our multi-year use of ServiceNow for (a) delivering IT Target Operating Model digital transformations to clients AND (b) delivering our Application Managed Services to external clients that this solution would easily meet our ITSM requirements.

There are multiple use cases associated with ServiceNow. The major use case is IT service management, incident management, and IT operations management. ServiceNow offers GRC and solutions that integrate with other security systems for cybersecurity. I have been involved in both ITOM and ITSM.

ServiceNow offers a range of ITSM, IT incident management, and PRCPs. The entire platform makes it an excellent product for users. Its capability to manage end-to-end ITSM is necessary because no other competitor is offering such a comprehensive solution.

The utilization of AI in ServiceNow needs enhancement. Their incident management system requires attention. If you examine it closely, there's an extension available in the market for future consideration. ServiceNow is quite advanced in incident management solutions. If ServiceNow aims to improve its incident management capabilities by incorporating AI/ML and other general components, it would advance the product and enhance its use cases, ultimately boosting productivity. This would lead to improved overall value for enterprise customers.

I have been using ServiceNow for eight to ten years.

ServiceNow is a very stable product. I have heard a couple of integration issues in some places.

ServiceNow can be easily scalable. However, scaling down may pose a problem because, if someone has purchased a certain quantity of subscription-based licenses, they cannot be reduced. You have to complete the term of those licenses whether you're scaling down or up.

We cater the solution to enterprise customers.

Our delivery team used to interact with ServiceNow, and they used to receive support from them. They are responsive. Most of the time, issues are resolved. They ensure a smooth delivery process and quick response. In certain complicated situations, such as new integrations where ServiceNow is not supported, there is a lot of email exchanges.

Positive

ServiceNow offers a very comprehensive tool that covers end-to-end IT services and IT operations management. This is where enterprise customers seek an end-to-end solution. ServiceNow is being adopted by numerous customers. I have experience with BMC Solutions.

BMC also provides an IT service management platform called BMC Remedy. Remedy is less comprehensive and user-friendly compared to ServiceNow. I've encountered support and configuration issues with BMC Remedy.

There is a large pool of trained workforce available for ServiceNow. Considering their market share, which exceeds 60%, there are ample skilled resources in the market. ServiceNow technology has been established. I haven't encountered challenges with ServiceNow projects in terms of implementation or configuration wherever I've worked. However, the deployment can vary depending on the company and partner, and how they've structured their practice teams and training resources.

If it's a Greenfield project, then a new deployment is necessary. For enterprise customers, integration becomes the key focus. ServiceNow offers a substantial integration portfolio to address these needs.

Return on investment is good because once the overall comprehensive solution is deployed, it offers a lot of ROI to the end customers. If a customer opts for a point solution to manage their ITSM and adopts different technologies to integrate, it is going to cost them, and then it will add up to their complexity.

The solution is expensive compared to other tools but holds value for money.

Overall, I rate the solution a nine out of ten.

We use ServiceNow for ticketing, integrations, automation, and event management.

The solution has an innovative technology that keeps on changing. 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. The solution's automation capabilities save time for our customers by resolving issues quickly and reducing human intervention.

The solution's integration with existing tools is quite straightforward. The way they set up the integration using the low-code/no-code model is very straightforward, and any developer can pick it up easily.

The solution's user experience could be improved concerning its UI and portals.

I have been using ServiceNow for more than three years.

We have mostly faced stability issues for the on-premises model. We haven't faced any downtime for the SaaS version.

ServiceNow is a scalable solution. We have different customers using ServiceNow, with more than 100, 500, and 1,000 user bases.

The solution's overall technical support is quite good. Sometimes, the technical support team lacks understanding of the issues.

I rate the solution’s technical support seven and a half out of ten.

Neutral

The solution’s initial setup is very straightforward.

The solution's on-premises deployment depends on the customer's requirement. It depends on how exactly the customers want to set it up in terms of users, what modules they want to integrate, and what integrations they want to have. An out-of-the-box deployment will take a week's time. The solution's SaaS model is already pre-bundled. You just need to switch it on and start working on it. You can start working on the solution's SaaS model in a day.

Our customers are extremely happy with their return on investment with ServiceNow.

ServiceNow's pricing is comparatively higher than Helix's.

ServiceNow is interactive, user-friendly, and easier to set up than Helix. It adds a lot of modules integrated within the tool, and you don't need to have different components installed separately, like Helix.

ServiceNow provides the best practices to streamline our IT service management processes. We have customer processes, and the tool helps to follow the process and reduce the meantime and resolution.

I work with both the on-premises and cloud versions of ServiceNow. The on-premises model requires some resources because we have to maintain the databases and applications. We don't require any resources for the solution's SaaS version.

Maintaining the on-premises model has its own challenges. It's a little bit difficult unless you know how the whole technology works. We don't need to worry about any maintenance for the SaaS version.

Overall, I rate ServiceNow a nine out of ten.