We changed our name from IT Central Station: Here's why
Jorge Ambrosio
Quality Management Office (QMO) Manager at a comms service provider with 10,001+ employees
Real User
Top 5Leaderboard
Flexible configuration, integrates well, and can improve productivity
Pros and Cons
  • "The solution is easy to use, simple to make queries, flexible to configure, integrates well, and supports all of our companies needs."
  • "When we are using the solution on mobile phones on their networks the performance is reduced with a delay of approximately 8 seconds. There is less delay using the desktop computers connected to the WiFi or to the network directly."

What is our primary use case?

We were using ServiceNow to collect data in problem areas in operations. Most recently we are using it for our internal hardware tracking. For example, if someone requires a change of computer system, new headset, or any other hardware defects.

How has it helped my organization?

ServiceNow has helped improve our organization by making it more efficient. Since we only need to manage the cloud service and not other aspects, such as infrastructure or software, this has freed up 30% of our human resources that can be utilized on other tasks. The solution has added value to the company.

What is most valuable?

The solution is easy to use, simple to make queries, flexible to configure, integrates well, and supports all of our companies needs.

If you want to do analysis about a problem or collect information and export the data on a spreadsheet or a BI system is very easy. The data is able to be selected very fast which is very good because, in general, to export or to restore the information with another tool was terrible. You practically needed to go directly to the database and export it from there instead of having the ability in the menu of the application. With ServiceNow, the options are in the menu and you can do all your queries directly and export them in different formats. This saves us a lot of time and makes our work a little easier.

The solution is always updating and you are able to see the road map of what is going to come in the future.

What needs improvement?

When we are using the solution on mobile phones on their networks the performance is reduced with a delay of approximately 8 seconds. There is less delay using the desktop computers connected to the WiFi or to the network directly.

For how long have I used the solution?

I have been using the solution for approximately three years.

What do I think about the stability of the solution?

The solution is very stable. We have never had an issue with ServiceNow, I do not remember a time we had a problem with the application. However, there are problems with the network, internet connection, and mobile networks, but not in the application. If there is a connection issue once the connection is established again the recovery is very good because the data automatically start to flow without any problem between both applications.

Azure has had only one incident in three years of use in our experience. 

What do I think about the scalability of the solution?

The solution is scalable. It is in the contract of the SaaS we have the ability to scale the solution in the cloud. We have never experienced problems because if we demand more capacity for processing we automatically receive it from Azure.

How are customer service and technical support?

We have 24 hours a day, 7 days a week support. However, I have never needed to use it.

How was the initial setup?

The installation or deployment is easy because this is a Software as a Service (SaaS) solution and it is managed by ServiceNow.

They analyze the use of the tools they provide us with and they do the new deployments in a slot time when we do not use the tool or have minimal use. They inform us typically more than a week in advance and they send several friendly reminders when the cloud service has to do a change, a new deployment, or an upgrade. They are very flexible to keep the downtime of the service at a minimum and at a time that the tools are not being used.

What other advice do I have?

The color scheme we are using is not good because sometimes the background is difficult for me to view. However, this is a company decision and can be changed.

We use a SaaS solution because the service has improved performance and maintains the up-to-date security of the application. As a company, we do not need to worry about doing upgrades because everything is looked after by ServiceNow. It is a very good solution and has worked very well for us.

I rate ServiceNow a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
ITSM Process Owner at a financial services firm with 10,001+ employees
Real User
Allows for role-based access, with integrated machine learning and AI
Pros and Cons
  • "For the nuts and bolts running of an IT organization, I can't really say there's anything lacking feature-wise."
  • "One thing I don't care for is the reporting and the way it functions."

What is our primary use case?

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

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the scalability of the solution?

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+ 

How are customer service and support?

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)

How was the initial setup?


What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Learn what your peers think about ServiceNow. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
564,997 professionals have used our research since 2012.
Director at a tech vendor with 1,001-5,000 employees
Real User
Can assign sub-tasks to different teams but lacks metric monitoring
Pros and Cons
  • "The feature that I have found most valuable from ServiceNow is the ability to assign sub-tasks to different teams, including problem tickets and the regular and chain tasks."
  • "The major area for improvement for our needs would be monitoring the metrics of the times to acknowledge and resolve issues and escalations."

What is our primary use case?

We mostly use ServiceNow for incident management. There is a team which interacts with the customers and logs customer issues as incidents. Then those incidents are taken care of by my team. I work on the escalation side of that team.

That is one aspect of ServiceNow. The second thing we use it for are any economic, long-term or repetitive problems. We log problem tickets which are resolved in ServiceNow.

The third use is for changes in the system. All the changes to the system are logged in ServiceNow with their associated tasks. Those are the three major use cases for ServiceNow.

What is most valuable?

The feature that I have found most valuable from ServiceNow is the ability to assign sub-tasks to different teams, including problem tickets and the regular and chain tasks. For example, if there is a chain which requires different steps of execution validation or execution steps, those task divisions, as well as the assignment and ownership of the tasks, is something that is really useful in ServiceNow.

What needs improvement?

The major area for improvement for our needs would be monitoring the metrics of the times to acknowledge and resolve issues and escalations. For example, if there is an incident which is not acknowledged within a certain period of time, or the resolution of the incident exceeds a certain period of time, it can be escalated to the next levels. That is one of the things you're looking for which is not available with ServiceNow.

The second feature I would be looking for is integration with different tools, like Bugzilla, Microsoft Informer, and Jira. Jira has integration, in fact. Teams in different organizations use different tools, so integrating those tools would be really helpful.

For how long have I used the solution?

I have been using ServiceNow for two years.

What do I think about the stability of the solution?

It is quite a stable solution. In the last couple of years we probably had around one or two outages and only one major outage. So it's very stable.

What do I think about the scalability of the solution?

ServiceNow is quite scalable. 

I would say there are about 400 people using ServiceNow in the organization. That includes administrators, users and those who maintain ServiceNow. Currently, ServiceNow gets daily usage.

How are customer service and technical support?

I don't usually get in touch with support directly because I am not an end user.

Which solution did I use previously and why did I switch?

In my previous company we used a custom-built tool which was not available on the market. It was called My Article Support and was built internally specifically for big biotic collection. It was highly customized and it catered to a lot of our needs.

One of the features in that tool was based on the customer engagement level and not on the revenue impact that customer had on the organization or the number of users impacted, etc... It would generate the incident prioritization score, which determined how quickly we were supposed to work on the incident. So the prioritization of incidents was automated, which I do not find in ServiceNow. But that tool was very customized and it was internally built so the development was done in-house. The second thing was the ability to track and close escalations because it was a custom-built tool and there was a process for it. The process was defined and was in the documentation.

How was the initial setup?

I was actually not there when the setup was done so I can't answer that.

What other advice do I have?

You need to find a tool that suits your needs. For example, the ServiceNow tool has certain advantages but at this point, one of the major things I'm looking for is tracking an escalation based on acknowledging the resolution. Meaning, I'm looking for something which is different compared to ServiceNow. It probably depends on your needs but for certain use cases, it does work very well, and maybe you need to do a deep dive or evaluate it before you buy anything.

On a scale of one to ten I would rate ServiceNow a seven.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Director de Servicios Profesionales at a tech services company with 11-50 employees
Real User
Gives freedom to change processes and offers advanced automated solutions for a change advisory board
Pros and Cons
  • "For change management, I find the CAB workbench very useful. I haven't seen any other solution that has a CAB workbench or advanced automated solutions for a change advisory board. ServiceNow also has the Workflow Engine which works very well and is very intuitive."
  • "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."

What is our primary use case?

We use this solution mostly for ITSM, but we also have customers who use it for customer service management and item discovery.

What is most valuable?

The features I found most valuable in this solution are usually also found on other platforms like the Visual Task Boards.

For change management, I find the CAB workbench very useful. I haven't seen any other solution that has a CAB workbench or advanced automated solutions for a change advisory board. That's one of the perks of ServiceNow. Other perks include the Visual Task Boards and the Virtual Agent. ServiceNow also has the Workflow Engine which works very well and is very intuitive. Some of the development tools give you a lot of freedom in terms of changing processes. That's what we like.

What needs improvement?

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.

In Latin America which is the geographical region we work in, it's not very useful. Some of the customers are more interested in other solutions. Sometimes they put aside ServiceNow because it is focused on the needs of the customer base in Europe and the US. This is one of the disadvantages I see.

Another disadvantage is the level of maturity that the customer has to have to get value from a solution like ServiceNow. The customer needs to have a great level of maturity. A company that is starting its journey with ITSM wouldn't find ServiceNow very useful, because sometimes there's a considerable amount of code you need to know to be able to implement ServiceNow. This will depend on the complex needs that a customer may have, for the customer to find ServiceNow as a useful solution. Depending on the level of maturity they have, they would need that amount of customization. I don't see the need for coding as a problem. The problem I see is that the level of maturity that the customer needs to have is high.

There's quite a lot of features in ServiceNow. Currently, we haven't had any sort of need that ServiceNow and the features that they already have, don't resolve. There's no feature that I can think of right now that I'd like to be added in the next release.

There are some guidelines that ServiceNow has that automate the implementation, but they're available only for ITSM and ITOM. It would be good if those automated guidelines are also made available for other ServiceNow solutions like customer service management, configuration management, and asset management.

Another area for improvement is the lack of clarity in terms of how this solution is licensed. It is usually very complicated for customers to know how they are being charged for the licenses that they consume. In most of the ServiceNow solutions, this problem is persistent.

For how long have I used the solution?

There might be some bias because we are ServiceNow partners and we're also Freshworks partners. We're not users. We're partners. We implement both solutions for customers.

We used cloud-based deployment.

We've been working with ServiceNow for quite some time.

Which other solutions did I evaluate?

I evaluated BMC.

What other advice do I have?

Some of the customers are interested in Acquire when they think of ServiceNow.

My advice to others looking into implementing ServiceNow is for them to really know what the objective of the implementation is: what they're trying to fix and what problem they're trying to solve. They have to be very conscious of these things because if they are not, the solution may not be a good fit. It's going to be too big of a problem to solve. They need to have a high level of maturity to get everything they need from a platform like ServiceNow.

I'm rating this solution a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Director of IT at a local government with 201-500 employees
Real User
Top 20
Scalable, extremely efficient, and integrates well with other solutions
Pros and Cons
  • "The workflow makes things extremely efficient and it improves effectiveness."
  • "It became kind of complex to set it up without a general lack of knowledge of the particular feature-function capabilities. Features and capabilities could have been explained better to the end-users."

What is our primary use case?

We primarily use the solution for change management and program management. Let's say, for example, if someone across our state needs a license. My team will send the request to me and I would approve it. For other tasks, they might send me a ticket and I would either approve it or add additional comments, however, that's it. 

How has it helped my organization?

The workflow and the general effectiveness of the processes have helped improve how our organization functions.

What is most valuable?

The workflow makes things extremely efficient and it improves effectiveness.

The product integrates well with other solutions. 

The stability has been very good so far.

We have found that the product can scale. 

Technical support has been helpful.

What needs improvement?

One of the areas that need improvement is when the product was implemented, they did not do a very good job of explaining all these features and functions, and capabilities of the tool. That could have been an implementation issue on our organization's side. This could have happened by not including end-users in order to get their input or to understand what this tool offers. It was kind of just pushed out. For example, while the tool could potentially do a hundred things, only 20 of the capabilities were explained. The other 80 we have to figure out on our own. It could have been explained and rolled out better, however, that could have been just an implementation issue on our side as well.

It became kind of complex to set it up without a general lack of knowledge of the particular feature-function capabilities. Features and capabilities could have been explained better to the end-users.

For how long have I used the solution?

I have used the solution for about a year.

What do I think about the stability of the solution?

The stability is good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

What do I think about the scalability of the solution?

The product definitely can be scaled. We're working now to integrate it with other workflow products, so it's definitely scalable.

How are customer service and technical support?

We've dealt with technical support in the past. We have a service desk. Since it's on-prem, it's been pretty good. Tech support has been helpful and we have no complaints. 

Which solution did I use previously and why did I switch?

We did previously use a different solution, however, with ServiceNow, we find that it offers better scalability, ease of use, features, and functions.

How was the initial setup?

My team did not implement ServiceNow, we do not maintain it and we do not service it. We just use the product.

I don't know what they had on the setup and the implementation part in terms of setting up servers and configuring servers and things like that. I don't know what that entails. We just know when we got it, we got a product. So what difficulties they might've had setting in up with, I don't know. I can't speak to that.

What's my experience with pricing, setup cost, and licensing?

I don't handle any aspect of the payments or licensing process. I can't speak to it from personal experience. 

What other advice do I have?

I'm just a customer and an end-user.

I go in and approve service tickets, however, I am not a hardcore user of that platform. My team sends me a request, I open it up and I review the ticket and I approve it, and then it moves on. I don't follow the workflow or anything like that.

Our team uses the most recent version of the solution.

I would advise potential new users to make sure that in that user community, end-users are involved in the implementation from beginning to end and make sure that the end-users fully understand the features and capabilities of the tool before it is implemented across an organization. Their involvement is key to a successful implementation and very important.

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

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Advisor at a energy/utilities company with 201-500 employees
Real User
Awesome support, good stability, provides visibility, and helps us in meeting our SLAs
Pros and Cons
  • "It enables us to meet SLAs, track issues across the environment, and report those issues."
  • "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."

What is our primary use case?

This solution is used for ticketing, reporting, and changes as well as for operations and incident handling. We always use one version prior to the latest one within the environment.

How has it helped my organization?

It provides us visibility into how we're responding to business needs. If somebody requests a new user account, a new computer, or something else, there are SLAs that have been agreed upon between different departments and business organizations. We can run weekly and monthly reports to get visibility into how we're responding to business needs.

What is most valuable?

It enables us to meet SLAs, track issues across the environment, and report those issues.

What needs improvement?

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. 

For how long have I used the solution?

I have been using this solution for around four years.

What do I think about the stability of the solution?

It is a stable solution.

What do I think about the scalability of the solution?

We're a small company with less than 10,000 endpoints. I would be able to tell you about scalability only if we had more endpoints, such as over 100,000. Currently, its usage is 100% because everybody is using the tool. On a daily basis, we have less than three percent usage, which would be 300 use cases on daily basis.

How are customer service and technical support?

They are awesome and great. I wrote the API bidirectional connector from Splunk to ServiceNow, and I've worked with them, and they are awesome.

Which solution did I use previously and why did I switch?

I have been with this company for four years. When I came into the company, this solution was already in place.

What about the implementation team?

I was not here when implementation was done, so I can't provide information about the challenges that had to be overcome when the solution was implemented, but I do know that it was implemented by a third party called Accudata. We did not implement it in-house. It was a managed service initially.

What other advice do I have?

I would advise having a close relationship with the people who are implementing it and staying on top of it. You should meet every day to address any problems that are encountered. 

I would rate ServiceNow an eight out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Gagan Pattanayak
Chief Revenue Officer at a tech services company with 51-200 employees
Real User
Top 5
Improves our incident reporting and resolution, but the integration capabilities need improvement
Pros and Cons
  • "ServiceNow gives us a lot for free: workflows, organizational structures, service portal, forms, reporting, disaster recovery, and so on."
  • "Integration capabilities can improve."

What is our primary use case?

Our primary use case is comprehensive reporting for our business and our regulators.

We began by extending ServiceNow capabilities within IT, which gave us a clear understanding of what we could do with it, and then expanded from there. We had many business processes that ran on legacy systems and spreadsheets. That created unacceptable risk and cost. That means we can focus on core functionality rather than having to build all of the application scaffolding and platform capabilities by ourselves

How has it helped my organization?

ServiceNow is the central hub for our data services. It takes in orders from our front-end CRM system and drives end-to-end fulfillment workflows. That starts with entitlements, which is checking whether a customer has all the necessary contracts in place. For example, if we’re providing access to third-party content, does the customer have appropriate contracts with the content vendor?

Then, we use ServiceNow to orchestrate the actual technical fulfillment process. This includes ordering circuits to connect to the customer’s premises and configuring our own backend systems, which ties into our core IT processes on ServiceNow. Once the service is up and running, ServiceNow provides reporting and notifications to support billing and financial forecasting.

What is most valuable?

ServiceNow gives us a lot for free: workflows, organizational structures, service portal, forms, reporting, disaster recovery, and so on. That means we can focus on core functionality rather than having to build all the application scaffolding and platform capabilities by ourselves. That saves us at least 50% on development effort, and because we’ve got a consistent platform framework, we also get a lot of reuse. That makes it easy to consolidate and retire applications built on legacy tools.

For example, Lotus Notes; we can modernize and save costs. In fact, since we started out, we’ve built more than 20 custom ServiceNow apps and our team is still fewer than 10 people, including QA.

What needs improvement?

Integration capabilities can improve. ServiceNow has a roadmap, however, native integrations in addition to the citizen-developed scopes would be ideal.

The pricing seems confusing, with the integration hub being most confusing.

I believe our firewall rule change request form is a custom form, but it has a serious drawback. If I submit such a request and need to make a correction to it before it is approved, there isn't any way for me to do so. The request has to first be rejected with the creation of a sub-task in order to edit it before it is resubmitted for approval.

For how long have I used the solution?

We have been using ServiceNow for two years.

What do I think about the stability of the solution?

Stability-wise, this product is very good.

What do I think about the scalability of the solution?

The scalability is good.

How are customer service and technical support?

The technical support is very good.

How was the initial setup?

This is a SaaS product. The customization and development of custom apps bit time-consuming.

What about the implementation team?

Our deployment was vendor assisted. It was expensive but good.

What was our ROI?

I am not in the finance department; however, incident reporting and resolution have been much better.

What's my experience with pricing, setup cost, and licensing?

The setup cost is high compared to others, especially when the scope is not fixed.

Which other solutions did I evaluate?

We looked at several options and decided that ServiceNow was the best choice. And it was because the rollout was highly successful.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Raj Bartakke
Director Customer Success and ServiceNow Practice Lead at CoreSphere, LLC
Real User
Top 5
Straightforward to setup with a low-code approach and offers excellent ROI potential
Pros and Cons
  • "ServiceNow is an industry leader in multiple areas and provides an excellent ROI."
  • "Like all other IaaS, PaaS, and SaaS subscription cloud providers, ServiceNow is constantly improving by building new capabilities to expand the breadth and depth of its offerings while increasing its activities with partners to build more capabilities."

What is our primary use case?

We primarily use the solution in a variety of ways, including the NOW platform (CMDB, Workflows, Service Portal, Service Catalog, Reporting), Custom AppDev, SecOps (Vulnerability Response with Tenable integration and Security Incident Response), Governance Risk and Compliance (GRC), IT Service Management (ITSM), IT Asset Management (ITAM), IT Operations Management (Service Mapping, Discovery, Event Management), IT Business Management (including Project Portfolio Management (PPM)), HR Service Delivery (HRSD), Software Asset Management (SAM), and Facilities Service Management (FSM).

How has it helped my organization?

We can now transform operations from excel spreadsheets and emails to a central system of record/truth. ServiceNow can either replace or integrate with a prospect/customer's existing solutions - especially if such integrations are common.

ServiceNow ensures a customer's investment by having 2 releases per year.  Prospect/customers considering implementing or expanding its ServiceNow investment should enlist the help of ServiceNow partners to support their effort throughout their journey.

ServiceNow is an industry leader in multiple areas and provides an excellent ROI. 

What is most valuable?

The platform (PaaS) is a low-code/no-code platform on a secure Infrastructure as a Service (IaaS - Government Cloud Computing environment (GCC)), with a single data model and a single system of record. Its applications (SaaS) can easily be extended with workflows and other built-in APIs together with the ServiceNow Integration Hub and other applications available on the ServiceNow Store. The platform is very flexible and built to be integrated.  

ServiceNow is an industry leader in multiple areas and provides an excellent ROI.

I have no further information to add to this, however, there is much more information offered by Forester, Gartner, and ServiceNow to augment this input.  

We are a ServiceNow partner, as well as Salesforce and other cloud-based IaaS, SaaS, and PaaS transformative solutions, and have been for over 10 years. Often, we are engaged with our customers for years, helping to build roadmaps that allow them to expand their solutions over time because resources are limited and organizational change management takes time.

What needs improvement?

Like all other IaaS, PaaS, and SaaS subscription cloud providers, ServiceNow is constantly improving by building new capabilities to expand the breadth and depth of its offerings while increasing its activities with partners to build more capabilities. As ServiceNow and its partners/customers expand the capabilities, I see new vertical applications being created (currently underway for TELCO and other industries). Stay tuned for more updates that not only provide new capabilities but also enhance existing ones.

For how long have I used the solution?

I've been implementing ServiceNow for over 5 years for various clients.

What do I think about the stability of the solution?

The solution has excellent stability and we're working with a client that has one of the largest implementations of ITSM and SecOps in the world.

What do I think about the scalability of the solution?

The solution offers excellent scalability. For example, currently, we are working with a client that has one of the largest implementations of ITSM and SecOps in the world.

How are customer service and technical support?

The product offers excellent support.

How was the initial setup?

Yes, the process is straightforward, but using an experienced services firm is best - especially if implementing the product for the first time.

What about the implementation team?

CoreSphere, LLC - CSAT scores are published on the ServiceNow partner page. Other are reviews completed in the US Federal government's Contractor Performance Assessment Reporting System (CPARs).

What was our ROI?

The ROI a company can get depends on the customer and the investment.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: CoreSphere, LLC is a ServiceNow Specialist Sales, Service, and Public Sector partner.
Flag as inappropriate
Buyer's Guide
Download our free ServiceNow Report and get advice and tips from experienced pros sharing their opinions.