ServiceNow Reviews

We use ServiceNow for our internal IT and end-users. When I first started with it, I was simply a user. I've now started to manage the functionality, as well.

Very soon, we will be upgrading to the Paris version.

The most valuable features are its ease of use and capabilities.

ServiceNow is a pretty versatile product.

It is robust and very user-friendly.

I would like to see more functionality in terms of custom workflows, not impacting the overall platform health.

I have been using ServiceNow for between four and five years.

This is a really stable solution.

It is possible to scale, as needed.

I have not had direct experience with technical support, but they have been very helpful for us.

The initial setup is quite straightforward. Ours is a pretty large implementation, so it took approximately two weeks. This was due to the complexity.

This is a pretty expensive product, so the licensing could be better.

This is a product that I absolutely recommend. My advice is to use as much of the out-of-the-box functionality as possible.

I would rate this solution an eight out of ten.

We build out video knowledge bases, how-to knowledge bases for self-service support and agent use. We integrate into a number of different ticketing systems, service management platforms, helpdesk platforms, and call center systems.

We are a ServiceNow partner and we have a ServiceNow instance. We use it for ticketing support, ticketing systems. It has worked really well for what we do.

We have set a standard around the way we build content. We have found that if we build for ServiceNow, it will pretty much import anywhere. The format is very similar. ServiceNow seems to be more of a standard interface and their knowledge import specs are pretty consistent with everything else. We have had a few we have had to tweak but, generally, if we build it for ServiceNow, in a lot of cases we can take a ServiceNow file and import it into any other system and it will work fine. That's the biggest benefit.

The biggest feature is that it is cloud-based, so it's always updated, it's always current. We don't have to worry about patches, revisions. We're always working with the latest version.

The features continue to improve. We get new features and we can choose to turn them on or not, but we're always getting them. That is part of the program.

Some enhancements to the self-service platform would be helpful. That part is still a little barebone. There are some things that they could do better that we have suggested to them.

Also, the mobile app is not bad, but it's limited. They are going to be working on that, I'm sure, over the years.

It seems to be very solid. We have not run into any errors or problems, although we're not a very heavy user. If somebody was processing thousands of tickets a day, maybe they would run into something, but for us, it's solid. There are no issues at all.

It seems to be able to accommodate any number of clients, agents, admins. We're a small company, so we don't stress it very much with the number we have in the platform. But everything that I see there, I think it will go. They have large, global corporations working on it, so I think it's pretty solid. That is what I've seen, but not what I've experienced.

Their technical support is very good. We're in the partner program so we have a different development program. We access a different group within support compared to the support a regular client would access. When we need help, the people we work with are very good. Things get resolved, things don't linger.

First, decide what your processes need to be. Determine what your environment needs, what's important, what your priorities are, what your process methodology is, and find a platform to fit that. If you are trying to find a platform and you don't go through that exercise first, you're just tying yourself up in knots. If you choose the platform first, then you are going to match your processes to the platform. If you haven't been through a process, an internal system environmental analysis, to see how things work and what you need, you'll never be happy and you'll wind up changing platforms every couple of years or every time your CIO changes.

When selecting a vendor the most important criteria for us are that they

• are cloud-based
• have ongoing development
• provide API capability so we can integrate whatever we need.

There has to be the ability to write APIs as you need them, so you can hook in whatever you need to connect to it.

I would rate ServiceNow at eight out of 10. They're good but they can get better. From what we've seen, they are making improvements, they listen to feedback. They're not sitting still, they continuing to evolve, continuing to develop, add features, add capacity.

The analytics - we like to keep track of how much work everyone is doing. We need to make sure that everyone is being efficient and being utilized. At the same time, regarding hardware, we want to make sure all the hardware is being utilized.

The other valuable feature is the asset management. It is the same thing, but with hardware. We want to know how much hardware - computers and anything else that we have in stock before we actually order them. Again, it probably boils down to the cost.

We're getting a good cost-efficiency. In my line of work, we deploy between 50 to 80 computers per day, break/fix new computers, laptops, you name it, we have it. We want to keep track of whether or not we need to replace a whole laptop, or just replace a hardware component that's failing on it. At the same time, we also want to make sure that we're keeping on par with the new technology, so that way we don't get left behind.

Most people are discussing UIs, but I'm a developer. I would say 80-90% of the people would appreciate that, that's easy for them, but from a developer perspective, it's hard for me, because for me it's clunky. Just give me a spreadsheet or give me a Notepad and I can write it down. For me, I would rather have that - give me an option to do that, maybe a CLI, instead of a UI.

Earlier today we were doing things such as merging data. What happened was I tried to merge one company to another. It's the same company, it's just a misspelled name. There was a bug - that there was supposed to be an undo button, but it wasn't there. It's one of those things, but then I asked a person how to do it, and they can't figure it out.

ServiceNow is such a complex piece of software. It's trying to be everything. The way I look at it, sooner or later, it's going to fail, because it's trying to do a lot of stuff. I can't say what or where, but it will. We've seen it a lot of times already with other products. You can't be everything, and that's what they're trying to do.

We don't really use much of ServiceNow except for the ticketing system, for now, so we don't have any issues. If there's a new hire we can add them fine, and it's quick. If there is new hardware, our admin just creates a new hardware form, and it's there, so I don't see any problem with that.

From my standpoint it's easy. As long as you attend an event where they teach you how to do it, you'll pick it up right away, because before I attended one, I had no clue how ServiceNow worked. I went to one for three days and now I at least have, about 25% knowledge of how ServiceNow works. I guess if you attend an event, you'll pick it up right away.

Right now we use ServiceNow, we use SCCM, we use Case. It's three different bits of software but basically what we use them for is as a reporting tool, like I said for the analytics of how we need hardware or tickets are coming in, but ServiceNow is mostly just for tickets.

Granted there's pros and cons in being everything that it wants to be. In our experience, we have Case, we have SCCM: sure, you're generating a report in SECM, and then you're generating another report in Case, there's a slight chance that the result will be different. If you have one thing, one software that's doing everything for you, the reports and the results will be consistent. I see that it's not done yet, it's not complete yet, but in the long run I also see it coming up with a bunch of problems.

The ability to get in there and create stuff without worrying about setting everything up first. I like that we can get in there and kind of start developing right away, we don't have to worry about getting instances set up, we don't have to worry about getting everything provisional, all the networking stuff done, just get up and go.

Everybody can access it, and that's great. They take care of security.

They seem to be answering a lot of our problems that we've been having in trying to control the development, trying to control our other developers, and it sounds like they're giving us that. I definitely want to see Scoped get built out more though, it's great that they've got the Scoped functionality but, I want to make sure that we're able to do all of the same things we're able to do in the global inside the Scoped applications as well.

I've been using ServiceNow for about three or four years, but I've really been developing in it for about two years.

We've never really had too many issues and anything we have had has been self-inflicted, so it's not ServiceNow's fault.

I don't even know that we've had too many issues with trying to scale anything, it comes right ready for everybody to access it in the company. The only thing I would say we've encountered, we've come up with our own creative ways to kind of prevent certain people from accessing things. It's really scalable, it comes ready to go for the whole enterprise.

I think they're pretty decent. Sometimes you have to finagle their help best to get the right answers. We've had to escalate some issues before but for the most part we've gotten everything taken care of.

It's pretty straightforward, and every now and then we have to go in and make some changes, but really it's not that big of a deal and it kind of helps us keep modernizing our stuff too, so not so bad.

• The way it can integrate with other applications.
• How it can be a central hub for anything we need to do
• The fact that it's cloud based. That's huge for us.

It'd be nice to maybe have some help features or some nice how to's to where if you need something, this is what you do. If something broke, this is what you do. Have that more readily available and more straightforward.

I've personally used it for about a year.

I haven't had any problems. No latency. No issues.

I believe so. We're going to use this as our central point for so many things.

Very knowledgeable and very quick. The questions that we've had to have, or issues that we've had, we've had them answered extremely quick. I'm very happy about that.

We're slowly integrating it. They're still using Heat for incident management. They had nothing for project intake, for onboarding, or service requests so we're bringing those on now as well.

Our initial setup was not the best. We had some issues with it with the company that implemented it for us. We're with a different company now and it has been just fantastic. They've taken us through the whole thing, they've helped us out and they've worked with us step by step.

I would highly recommend it. I would say first thing you need to do is sit down and figure out how you're going to start with it and then, where do you want to expand from. Obviously, you don't want every module to start with. Start off with what's your biggest need or what's the easiest to implement and then go from there.

The platform as a service and the capability to build our own custom apps. Also, the built in work flow engine as we're able to create our own work flows, but that the engine is already there and it speeds application development.

We are using ServiceNow to replace some applications on systems that we're hoping to be able to retire. It's helpful to be able to get new applications up and going quickly, and the work flow engine helps a lot with that.

Using it as our ITSM solution, it has helped us to move a lot of our different processes onto the same platform, which helps with reporting and tracking and that sort of thing.

We still have some issues with some of our ITIL users, like some things aren't as intuitive as they could be. Related to being able to see things, like what tasks are assigned to them. Service Catalog and request fulfilment is the main module we use right now, or effects the most people, and so the learning curve for some of our ITIL users is a little higher than we would like in some cases.

We have had some issues over time. I think at times, they've ramped us up or given us more processing power. A few times we've had outages lately here too. Sometimes it does seem slow. We've kind of learned not to bring up a list with a thousand items in it. Sometimes there's something that you run that you expect to get a response in a couple seconds and the counter counts up to 45 seconds before you get your response back, so there's certainly some issues. We've seen a few bugs, but no show stoppers.

We're on the small side of ServiceNow installations. It's just for our plant, so it's not like our whole operation. So, we haven't had any scaleability issues other than we've seen some latency sometimes. I don't know how much of that might have been related to needing to scale up a little bit.

We had a custom Lotus Notes database that we were using for request fulfilment before, but some of the other pieces that ServiceNow fills in we had various solutions for. We switched because ServiceNow gives us more capabilities as far as giving us one platform to be able to have a lot of our systems on and it has a lot of functionality there just out of the box. A lot of plug-ins you can just turn on and have some functionality, which of course, we want to customize. But, being able to roll out something like that so quickly helps.

The initial implementation did take a while. It was fairly complex. We engaged ServiceNow to help us with that. Our ServiceNow also engaged a business partner to help us with roll out initially. Going through that process did take a while, but we had the workshops and training in place to help make that easier.

It was through ServiceNow, but they were busy at the time, so we had a ServiceNow project manager. To help, ServiceNow also brought in a third party and the third party was stronger than our ServiceNow program manager or project manager was, and wasn't nearly as strong as the business partner was.

ServiceNow is not cheap, especially as we continue to pay for it year after year, but it is helping us be more efficient from the perspective of taking less time to make sure that our requests are fulfilled and to bring out new features and functionality.

It would help to know more about a specific situation to give advice, but it is nice that there's a decent sized ServiceNow community and Wiki that you can find what you need. If you see a demo or see some of what ServiceNow can do, it's certainly worth looking into. However, to give more specific advice, I'd need to know more.

I think there's some things about that that ServiceNow could have implemented better, but the software in general is good and solid.

ServiceNow can be deployed for everything, in terms of ITSM, CSM, facilities management, HR, financials, CMDB, asset management, and orchestration. You name it. It's really used for everything.

What I found most valuable in ServiceNow is that it's a cloud-based platform, so people won't need to worry about investing on hardware to host it. Being a cloud-hosted platform also means ServiceNow is available 24x7 on any internet-connected device. You can also try the platform for free by grabbing a free developer instance from the ServiceNow website.

Customization, data import and export, and data backup are also features I found most valuable in ServiceNow.

There's always a room for improvement in terms of the ServiceNow UI. For customers, the UI is something that is a continuous improvement, so the UI would be the only thing in the platform that needs improvement.

I've been a partner of ServiceNow for three years now.

ServiceNow is a stable platform.

ServiceNow is a scalable platform.

I find the technical support for ServiceNow good. It's rock solid.

The initial setup for ServiceNow was straightforward.

I don't have the numbers on the ROI from ServiceNow, but we have experienced ROIs from some of our customers ranging between six months and one year, depending on the models they have.

I'm dealing with the new version of ServiceNow: San Diego, and I'm also dealing with its previous version: Rome.

I find ServiceNow a solid platform, and I can't think of any area for improvement. If anything, the San Diego version is even better than the Rome version, and Rome has been solid, so I wouldn't change anything about ServiceNow.

The maintenance of the platform is automatic, but for maintenance in terms of fixing or reconfiguring things inside ServiceNow, we offer professional services for that. For maintaining one project, we need 10 dedicated maintenance personnel, out of the 21 maintenance personnel we have within our company.

My advice to anyone looking into implementing ServiceNow is "Go for it", especially because the platform does everything. ServiceNow is a system of record. It's really everything, e.g. everything is a record today. A ticket is a record, an asset is a record, a bill or an invoice is a record. Everything is a record in a giant database.

The platform is also cloud-based, so people don't even need to think about investing on hardware to host the platform. The platform is hosted on cloud, so it's available 24x7, on any device that has an internet connection, e.g. laptops, computers, mobile phones, etc.

If people need to try ServiceNow, they can enter the developer mode in servicenow.com, and just grab a free developer instance for a couple of weeks and give it a try at no cost. ServiceNow is a no-brainer.

I cannot think of anything that needs to be improved in the platform, because if there is something that ServiceNow does not do out of the box, it offers a way or a means for you to build it from scratch in the application builder. Even if the platform would not offer something commercially available to be deployed with no hassle, e.g. without the need for building it by yourself, or programming it by yourself, or hiring someone to do it for you, it has the means to create it almost codeless. It already has sufficient customizations. It has data import and export, including data backup features. I cannot think of anything that ServiceNow cannot do at the moment.

I'm rating ServiceNow nine out of ten, only because I never give a ten to anything.

I use it for incident management. For the part of the business I'm in, it is used for end-user incident management. There are other parts of the business where it is also used for customer data collection or customer engagement data collection.

Remote access is most valuable.

It needs a more intuitive interface for identifying issues. A bit more natural language processing or something like that would be helpful in understanding my queries.

There should be greater integration with other enterprise applications. We're using Microsoft, Oracle, and other applications, and it would be good to have a greater integration on some of the immediate hiccups that you have with these services. It doesn't mean that when we have a problem with using another application, ServiceNow should be able to fix it, but ServiceNow should be able to alert us to things. There should be a bit more automation or integration.

I have been using this solution for at least five years.

It is stable.

It is scalable.

We had minimal tech support.

I am using it in a managed IT environment. As far as I know, it was satisfactory, but our department manager would know more.

I would recommend this solution because I make good use of it. I would rate it an eight out of 10.