ServiceNow Reviews

When we need to request a task from another team at my client's organization, we typically submit a request in ServiceNow. We provide all the necessary details through the ServiceNow platform, and any communication related to the request is documented in the form of comments. This approach ensures transparency by recording what was requested, actions taken by the assigned person, and the time taken to resolve the request. Using ServiceNow, we can easily track the progress of tasks, review the history of actions, and assess the workload of a specific individual over a given period, be it a week or a month.

It proves invaluable in tracking significant incidents within your work environment. It facilitates the monitoring of major incidents and provides insights into the effort expended to resolve each incident. This capability adds substantial value by allowing a comprehensive understanding of the incident resolution process and the associated resource allocation.

It should include information on navigating various user interfaces for creating diverse requests directed to different teams. Enhancing usability involves providing easy access to interfaces tailored for different types of requests across teams.

I have been working with it for two years.

It is proven to be reliable; we have not encountered any issues with it.

We have nearly one hundred to one hundred fifty users.

The initial setup is relatively straightforward.

It's effective, indeed. If you aim to monitor the number of issues you're handling and wish to understand the effort required to resolve them, this serves as an excellent ticketing tool. Overall, I would rate it eight out of ten.

We use ServiceNow for help desks.

ServiceNow is one of the few easiest platforms you can integrate with products like Ansible to automate your workflows.

The solution’s user interface could be improved and given a better design.

I have been using ServiceNow for more than three years.

ServiceNow is a stable solution, and I haven't experienced any downtime with it.

I rate ServiceNow ten out of ten for stability.

Around 500 to 800 users from the IT team and some of the business teams in our organization use ServiceNow.

Overall, I rate ServiceNow an eight out of ten.

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. 

We used ServiceNow for various functions like incident management, ITSM (information technology service management), and we also used it for CMDB (configuration management database).

I worked for a manufacturing company and we were using ServiceNow for managing the company's IT functions, particularly for ITSM.

In my current company, we use it for CMDB.

I found the reporting capabilities of ServiceNow really valuable.

The service catalog feature is also interesting, particularly because it is highly customizable. You can create anything you want to create. This is one of the good things I like about ServiceNow.

Its integration capabilities is also a valuable feature because you can connect ServiceNow with any other application.

What could be improved in ServiceNow is the response time or loading time. It's slower, but it could be based on the license you have. Everybody here in our company says it is slow whenever we access it, so that needs improvement.

The user interface can also be improved. They should make it better than what it is currently. It should be more user-friendly.

An additional feature I'd like to see in ServiceNow has something to do with its out of the box pattern. Currently, I'm using it mainly for CMDB. Each company will have different hardware or configuration items, but ServiceNow only provides certain scripts or patterns to discover all these onto the CMDB.

If there's any new device, we'll need to customize the out of the box pattern, so maybe that's a feature that can be improved. With any device you add, everything should be added on the CMDB using whatever out of the box pattern or script is provided in ServiceNow. Currently, that is not the case.

If we have a new device that is added to our company's network, we have to go and customize the existing ServiceNow pattern to discover that device. This is the problem we're facing.

I've been using ServiceNow for two years.

This tool is stable. It performs well, but like I mentioned, its response time can be improved, but overall, it's good. It's reliable.

I find this tool easy to scale.

Every now and then, we'll face some issues with scripting, pattern, etc. We always go to the HI portal which is the maintenance portal of ServiceNow, and there we ask for support by raising a ticket to ServiceNow directly.

The support is not 100% good, because sometimes we experience delays in their responses, but it's okay. It's not bad. They'll see to it that they resolve the issues, but it may not always be on time.

We used BMC Remedy, but since we were using a very old version, we can't compare it to ServiceNow. ServiceNow is a lot better and more user-friendly compared to that tool.

For large-scale companies, the cost of ServiceNow is not expensive, but for small and mid-scale companies, it is higher. I worked with large organizations and they never had a problem with the cost, so it depends on how large the company is.

I evaluated BMC Remedy.

I'm using the latest version of ServiceNow.

I was not involved in the initial setup of ServiceNow, whether in my previous or in my current company. I do not know much about it, but how easy or complex the setup is will depend on the company. If it is a large-scale company, the initial setup would be complex and it'll take a lot of time.

Even if it's deployed on cloud, it would still require maintenance. We just purchase the licenses and initially during deployment and training, they'll help. After that, it depends on the company to manage and maintain the solution. If we get into any issues, we'll definitely need to reach out to them.

We are 1,000 people in IT, so we have 1,000 IT users of ServiceNow. As for end users, we have between 30 to 40,000 employees in the company, and at least 30,000 employees will submit a request or incident using ServiceNow. We're using this tool on a daily basis.

I don't think there is any additional costs, as support is covered in the standard fees, but I could be wrong, as I was not involved in the initial setup or financial discussion, so I wouldn't know much about it.

My advice to others looking into using ServiceNow is that they can do their research and ensure that this platform is the one they're looking for. If after reading all the information and comparing different ITSM options available, they find that ServiceNow suits their business, then they can go for it. They should not go for it blindly, because there could be many others which are better than this solution. They should research well before they make their decision.

My score for ServiceNow is a seven out of ten.

We primarily use the solution for ITSM and a little bit of ITOM. However, we don't use it for ITBM.

Role-based access is a 'positive'.

ServiceNow has a feature called Orchestration. In that, you can utilize the tool to communicate with applications and systems to issue commands and perform actions. That's a positive, it's something that does exist in the tool. We are in our infancy in utilizing that.

There's a relatively new feature called performance analytics. It's supposed to provide a lot more information. It's got machine learning and some AI built into it. We're our infancy with that. 

For the nuts and bolts running of an IT organization, I can't really say there's anything lacking, feature-wise.

The solution is relatively easy to use.

One thing I don't care for is the reporting and the way it functions. Exporting a report, from a view,  initiates a rerun of the query in the background - highly inefficient.

In terms of the implementation, there seems to be a dearth of basic table joins, on initial install, necessitating the creation of your own database views to get seemingly related data to act like related data. In other words, it's popular to have incidents linked to changes, and linked to problems, and linked to other types of records. And vice versa, you could have an incidents caused by a change. You could have an incident that has a problem record built off of it. However, there are several modules where, if you don't create table joins - for example, for demand records and demand tasks - between those two, then the only option is pull two reports (one for Demands, one for Demand Tasks), and manually merge them outside of the tool. It's highly inefficient. That is something that is a deficiency within the tool design overall.

The initial setup is a bit complex (could have been designed to be profile-driven, as an alternative).

While I recognize that it's a popular thing to do, due to poor design, update sets have to be moved manually, from platform to platform, easily introducing errors (sequence, origin, etc.)  along the way. I've seen far better promote-to-production schemes with other tools.

I've been using ServiceNow for more than 5 years.

Scales 'up' well.  

Scales 'down' poorly.

The solution is not exactly scalable for a mom-and-pop shop (and SMBs). The costs would be too prohibitive for that.

Someone once said, a bird, no matter the size, has the same number of bones. If you're going to do incident change problem, asset config, things like that, for a mom-and-pop, technically, you have the same number of types of things you need to be concerned about. It's just the volume of how it's being applied. A mom-and-pop store might carry 50 items in its inventory. A large company is going to have thousands upon thousands. Therefore, ServiceNow would not be a good solution for a small organization with few assets. 

If you don't have a full CMDB to begin with it really makes a lot of things awkward within the tool. 

We have 4,000+ 

ServiceNow Technical support needs improvement.

One example - 

Order - (context - business rules) - ServiceNow allows you to have any number of rules with the same order number. 

ServiceNow's official answer to 'how does the database code decide which rule to execute first, when multiple business rules are assigned the same order level?': we have no answer 

(it goes without saying - use unique order levels)

We're just a customer and an end-user.

We started on-prem and then switched to cloud. We switched to the cloud about three years ago.

- fill out the CMDB before you start implementing the tool - make the time.

- plan out table joins as you implement new modules.

I'd rate the solution at an eight out of ten. I would just warn others that it's too easy to incorporate abysmally poor design.

Multi Tenant, Scalable, Flexible and Stable

It has improved out response time to the client

The reporting is very good. 

The solution has very good automation tools.

The solution has been extremely stable so far. 

The need to improve their technical support services. 

Their dashboards are very, very basic. Maybe if they could develop some sort of very good fancy-looking, visible, graphical, visible kind of appearance. 

The pricing of the solution could be better. It's a bit high.

When we are monitoring, for example, a device, an S-Switch, we can create insights. We can segregate the LAN, and create a VLAN. When we create those VLANs, we should be able to monitor those VLANs. The same with storage systems. The LANs, through the cable space level, should be able to be monitored. 

I've been working with the solution for eight or nine years so far. It's been almost a decade. I've used it for a while now. 

The stability is excellent. There are no bugs or glitches and it doesn't crash or freeze. I find it to be reliable. 

The solution works very well for large enterprises. If you have a very, very big setup, it's an ideal option.

Technical support could be better. We are not satisfied with the level of support they offer.

I've also worked with SolarWinds and ManageEngine. I prefer ServiceNow, as there's a lot of automation tools available in that and it's been a stable product. It's been in the market for a long time. It's got a good market reach also.

Very Complex, 13 companies, 9 Towers, 17,000 devices

First time we implemented it through Vendor and we took a training from the OEM and now we have a team to deploy the solution

Not calculated, but I would say 2 years we recover the cost 

Their pricing is relatively high. They are expensive.

Yes,

SolarWinds and ManageEngine

We are not a partner or reseller. I'm a consultant. Before that, I have implemented the products. I've migrated a lot of products, a lot of systems. That's how I have an association with monitoring tools and service test tools.

I differently would recommend the solution if a company is a huge enterprise. For example, if you are maybe looking at more than some 10,000 or 20,000 devices. There should be a minimum of 10,000 devices or 15,000 devices. I would recommend ServiceNow for those setups. For data centers and other things, definitely I would recommend ServiceNow. I would not recommend SolarWinds or ManageEngine for these types of setups. I don't see that much capacity in them. 

I'd rate the solution at an eight out of ten.

The solution is being used for our ticketing system.

It is user-friendly and simple to use. 

The solution could be made cheaper. Machine learning and artificial intelligence should be introduced in the next release. 

I have been using ServiceNow for two years. 

The scalability of the solution is good. Presently, ten thousand users are using the solution. I rate the overall solution an eight out of ten.

The initial setup is easy. The deployment was done within a month. 

Overall, I would rate the solution an eight out of ten. 

We used ServiceNow for change management, release management, and event management. We were also making use of the solution's CSI. The modules of ServiceNow were all available to you, and you could use them.

I have a problem with the way the solution's price is calculated.

I have been using ServiceNow for 10 to 13 years.

I rate ServiceNow an eight or nine out of ten for stability.

I would recommend ServiceNow for larger organizations. We used to have an organization with over 10,000 users. In our current organization, up to 3,000 users are using ServiceNow.

The solution’s technical support is fine.

We implemented the solution through an in-house team.

For us, ServiceNow was really good for keeping everything under control. Everything was documented, logged, and on point. The setup of creating things was quite straightforward.

The use and misuse of the CMDB is something important. Since CMDB should be the heart of everything you have, transforming the CMDB into a repository of information is good enough. If you don't use the full management tool, you can have problems. In three months, you will have to review the CMBD again, or you will have to update it once again in six months.

It differs from organization to organization. It will be taken care of in organizations that have clear processes in place. It's not about the tool but about the maturity of the organization using it.

We used to have lots of integrations with our systems to create tickets automatically. We also had some security related event management activities. When we requested to change something in ServiceNow, it was done rapidly in a couple of days.

Have some consultants that have worked with ServiceNow before, help you with the process. You should try to implement ITIL in your organization. If ITIL is not understood by the organization, then you cannot have expectations that they will follow the way of working as they should.

The solution's automation is quite straightforward. You just need to know what you want to automate. There are several ways to integrate stuff and several ways to have some triggers.

Overall, I rate the solution ten out of ten.