ServiceNow Now Platform Reviews

Incident management, change request management, HR-related features, product management, and asset management are all valuable features.

We do analytics on top of these features as well.

The Robotic Process Automation features are not mature enough. ServiceNow could work toward that because we can leverage RP only from this platform.

Predictive intelligence could be fine-tuned as well.

All of the features are already there in ServiceNow, but they need to be mature enough to be utilized by bigger organizations.

We partnered with ServiceNow almost 15 to 20 years ago.

It's quite stable, which is actually the reason why we use it heavily.

It's quite scalable.

ServiceNow's technical support has been quite helpful. They assign account managers, and we are able to escalate issues as well.

The initial setup is straightforward. Because we are using the cloud version, we don't have to install it on the end user's machine; we just provide the URL and access to it.

We have a technology and operations team with 25 to 30 people for the global maintenance of the solution.

Some parts of the implementation process are done in-house. For others, we partner with consultants.

Most of the features are included in the licensing cost. However, if we need extra plugins that are not available at the ServiceNow Hub or store, then we have to pay extra for those.

ServiceNow Now Platform is quite useful, scalable, and flexible. The user interface is very good.

I would recommend it to other organizations and rate it at eight on a scale from one to ten.

Our primary use cases for ServiceNow Now Platform include use incident management, problem management, case management, and our asset management. 

It's not used much for the business management part of it, though it's being assessed for it. We have other tools to manage that. In my organization we have the scenario where we will integrate with a couple of other tools which we have already purchased, which are used for the information management part of it. These will be integrated with this Now Platform. 

Another area which is currently being looked into but not yet implemented, is the compliancy part. They might go for it in future. One more thing is the security part. Though it is not yet being employed that much, it has a lot of interest. I can see a lot interest in this area. At times there is strategic interest in digitalization, so we might look into the analytics. There are more improved analytics features which are coming with the new versions of ServiceNow, which are also interesting.

ServiceNow offers a lot of features when it comes to IT service management and IT operations management. What interested me in ServiceNow was that a lot of service management, mostly our IT service management, are using ServiceNow as a tool.

I really doubt that we are making full use of the out-of-the-box features which ServiceNow provides in the sense that we have the tickets assigned to one of the assignment groups. People are taking a lot of time to really work on the ticket and provide a correct solution. I was looking at different features, including the machine learning and predictive analytics features available in ServiceNow, which can help solve the current issues we face.

In Power Apps, there is a central area which works on the automation part of it. Even though in ServiceNow I see a lot of features in the process automation part of it, when it comes to large teams with a lot of "in development areas," we're just getting into how we can automate the mundane processes. Plus, there is a robotic process automation team using UI who is looking into those areas.

Also, as part of the development tool, I analyzed to see how their domain expertise was. With a little knowledge of the technology and coding experience, they can make your software domain expertise come up with solutions very quickly. 

However, since we are already using Microsoft extensively and we already have Microsoft Office 365 and since we have adopted Microsoft as the Cloud provider platform, it made sense to take the Power Apps subscription. Even though ServiceNow has some integration capability with Azure, Power Apps was more in line with developing apps and the development of UI.

When it comes to ServiceNow, I haven't done much research on the UI part. I think that you can do different coding in ServiceNow. It was more about usage of tables, creating API's, and creating application codes for when you work on tables. But in Power Apps I could see features having a use, so I can work with this, and you create UI's out of it. Maybe my knowledge is limited and I may not have explored all of the features in ServiceNow, but this is one thing which on a high level I have noticed.

Also, with Power Apps you can attach it to multiple data sources, just like in ServiceNow.

I think that both have their own features and pros and cons. I don't think that Power Apps can fully replace ServiceNow when it comes to all the features ServiceNow provides in terms of service management or operation management capabilities.

Power Apps is mostly if you want to develop a web application or a mobile application and if you have some data source. If you have a back end already. If you have a database and you specifically want to develop a front end or a UI for that. Then I would prefer Power Apps.

Power Apps is mostly for the use cases where you want to give an API further uses to get specific data from the back end. When it comes to ServiceNow, there are not many purposes I can see regarding the service management part of it. It can be used as a ticketing tool that we can use for operations management. It can be used for server monitoring, like for our infrastructure management and monitoring purposes.

As I told you, we have within the organization a lot of tickets for cases which are being raised for problems with the application or the infrastructure or even for knowledge related issues. I am from the architecture central system, and if the people need help to find the architecture or they need a suggestion, they raise incidents of tickets using the ServiceNow Now. I have noticed that cases are not getting assigned to the critical people if there are so many different teams. A case for a problem which arises might fail to be worked on by some other members in the team. These are the areas that I feel the machine learning capabilities of ServiceNow offer.

It can give you a lot of improvement in the way the tickets get properly assigned to the right group. It saves a lot of time which saves the end user a lot of frustration, and they will be getting the correct group who can help them on their problem very quickly, preventing a delay and then after lot of time it come back to the admin group, and then the person who's working on it will do a relief study of the problem. 

It leads to a faster resolution of the problem.

That is my own experience. Then, if we can have chat bot services, that is another area of network manual intervention. That is what really attracted me when I was into the features of the latest ServiceNow.

As for what can be improved, the licensing and the pricing models are confusing. At least I found it a bit confusing. There are a lot of hidden costs in all these.

It's a bit costly. But as a cloud application platform and a service provider, I think ServiceNow is now really improving. When comes to the cost part it is a bit tricky to understand. It's not that straightforward.

Like other tools or other platforms, when we are in touch with the ServiceNow team, we talk about including everything from the information management in the entire software development. I feel they are doing well.

It has a lot of good documentation and a lot of good training available which helps the end user.

The programming language is currently limited to JavaScript. So I would like to see more programming languages available, especially since they have come up with the machine-learning features. Some more languages would be an additional improvement.

I see that there are so many connectors available for connecting it to other service providers and other platforms, for example OpenText, which we are using. There are out-of-the-box connectors to connect to OpenText and others. That is something that I'd like to see.

Other areas of improvement are support for more programming languages and much more capability-building when it comes to the machine-learning part of it. There is especially a need for a scope of improvement in the analytics and the machine-learning part of it, because they are always adding more modules. 

I have been using ServiceNow Now Platform for about five, six months.

I have not found any bugs or glitches. I have tried looking into the IntegrationHub features. I have tried looking into the APF features with ServiceNow. I was involved in setting up the SSO for ServiceNow across all the instances that have a card. It is not ready. We have still some migration to do, but SSO set up is ready. I set up the mail server.

I didn't find problems. My experience was good. It was not was complicated for me to understand. The tutorials and all the trainings which ServiceNow provides for us to set up the infrastructure or to try out the new features ensured it was not that complicated.

I tried these new features which have not yet been adopted in the organization. But I can not blame the platform for that, because I was trying the Virtual Agent features with my own personal developer on that.

The problem is you really need to have data to work on. If you want to train a model, you will be able to train it only if you have sufficient historical data. That is sometimes an issue, because when you work on your personal developer instance, the kind of data you have will be very limited and you will have to import some data from your production instance or some other instance to your personal developer instance.

When ServiceNow gives training, they provide a simulation platform. For this core training you will not be able to use the platform after that. So you need some time to really catch up and try different things to get a grip on what you're learning. The MS data was for working with the shape and I'm trying to get some data exported from our own production instance and import and try to work on that data. That is one issue I face.

So far, so good. But I cannot claim to have a very good knowledge of the entire platform. I have analyzed some areas and I found the experience good.

In terms of scalability, I'm impressed. I'm happy with the capability of the Now Platform. We have some dependencies on the vendors. But with the current investment we are learning the full benefits of the platform. I am positive that as time goes on we will be able to rate the real benefits of the platform.

I have interacted with a few of the technical support guys from ServiceNow and my experience was good. I found most of them really very professional and very technical people. I'm happy with the kind of service and the kind of value they are bringing to this engagement.

I cannot comment regarding the initial set up because we had the ServiceNow team help us with it.

Although we wanted to use the out-of-the box features as assets, the processes in the organization were not that straightforward so it required some amount of customization and that lead to us having discussions with the team from ServiceNow. I cannot say that it was really smooth and easy. Because of the complex workflows and processes being followed in the organization, there were a lot of discussions involved, and a lot of customizations done. The ServiceNow team was able to give us a lot of insight, including where the improvement can happen, but then we couldn't add up everything, as the workflow is a bit complex and it involved other vendors.

It's not over yet. We are still in the development phase because the old one we were using was being managed by an external vendor who is responsible for all our time activities for the maintenance of Infosys and others.

It depends on the assignments you have in your organization. Our organization is very process oriented and it faces the drawbacks of that, in the sense that it is not very agile. I think for such organizations, ServiceNow could bring in some improvements, provided we really understand how to use the tool to really ensure that the different services in the business can work together.  And to understand what your problem areas are and how this tool can help you.

People from different departments and different areas, especially from business and IT, should really join hands and work together. They shouldn't be working in silos.

If that is the case, then you have a tool to support you. It will help bring that unity and the visualization of whatever you have in the mission. Otherwise, I don't think you'll be able to improve anything.

On a scale of one ten I would I would give ServiceNow Now Platform a seven.

They would get a 10 if there were more programming languages available and if it was more clear to use. Also, if they offered more UI features. Also, when we are trying out the system, if there was a toolkit which could help guide us when it comes to navigation.

I am actually a development expert within the ServiceNow platform. So I implemented ServiceNow for some of our customers as well as within our company. I help them to implement some applications customers and configure what they need from the suite of management applications available within ServiceNow.  

The most important thing we use this solution for is IT service management where users implement processes like incident management, problem management, or chain management. Incident management and problem management at its simplest can be a system whereby any user in an organization can report a defect. Say I am a user and my email is not working and I want to raise a ticket to get the problem solved. I use ServiceNow for raising that ticket. Another example is that if I want to implement new software, I need may need to raise a change request, so I do that in ServiceNow. 

We are always on the latest version. There is a new version every six months, so there are two releases every year. That means every time there is a new release I have to upgrade, update my knowledge about the changes by becoming familiar with the changes, and then we have to upgrade the program for the customers as well.  

The workflow feature really has a lot of value because you can create workflows in a simple, intuitive way. With a few clicks, you can actually develop quite a complex workflow using tool and product life cycles and so on. So, the workflow feature, in my opinion, is the strongest feature in the ServiceNow platform.  

There are several areas of the product that could use improvement. From a vendor point of view, I had an opportunity to work with them on their licensing model. It still needs some improvement in the way the licensing model works because it is a little bit complex and difficult to understand. They change it from time-to-time and sometimes they do not communicate those changes effectively to their partners. Put simply, the licensing model is something that can be simplified and made more visible to both the partners and the customers or end-users. Currently, the product is comparatively quite expensive and lowering the cost would likely produce a better response from customers.  

I know that the company is at work on many new things right now. But one thing I would expect to see in the next few releases is vertical-specific solutions. For example, say solutions for banking or healthcare-specific solutions. I believe they are going to come up with at least a draft version of this type of solution for some industries over the next few releases.  

We have been using this solution since about 2016. So it is almost four years now.  

I have complete confidence in the stability of the platform. It is very stable.  

ServiceNow is very easy to scale — that is if the customer has the money to spend. It is quite easy to take on new licenses. It is very scalable.  

Our customers can be any size business but in my personal experience, I work with medium to large customers. The solution is something that is used on a daily basis.  

We have been in touch with their technical support and it is quite responsive and they are very good about providing solutions. We have a dedicated technical support desk that is quite approachable. For now, everything is quite good.  

Before ServiceNow, I used other solutions, but mostly they were custom-built applications. For example, I used to code and develop an application from scratch. ServiceNow is the first product I have used software that is a dedicated service desk product.  

I would say that from my point of view that configuring ServiceNow is pretty simple. But there are also a lot of things to consider. If you want to build a complex system, the configuration process can be complex as well. If you understand the software, you get a standard set of functionalities, but you can configure that for your own needs. For example, I had a situation where I knew a particular customer had some different requirements than what was provided out-of-the-box for the standard version. In this case, I was able to configure ServiceNow to match their needs. I can write complex scripts or I can do programming to build new processes within ServiceNow. But the implementation is different for every customer.  

How long the implementation takes becomes a very open-ended question because they have so much existing functionality already in the product that may need to be configured and the need for customization depends on the user's requirements. There are so many factors involved that I can not really define an absolute amount of time required for standard implementation. It depends on the use case. The basic installation of the application itself can be done in ten minutes and the solution can be made to be up and running within three months. However, if you want to have a complex, custom-built chain management process, it can take years.  

I am from a software development company and I work as a consultant as well as an architect for projects. Our operating model is that we work directly with the customer and we do the consultancy, we get into workshops with customers and discover their requirements and then our development team starts working on those requirements. So we have two levels. One is as a consultant who helps to finalize the requirements and the other is as developers who satisfy the requirements that have been defined.  

As far as how many people it takes for the deployment of the platform, that can not be determined as a set number either as it requires knowing the scope of the project and perhaps other factors like the expected timeline.  

We use a public cloud, but as our customer, you get a private instance. So you can think of it as an environment you can have in the cloud that is indicated for a particular customer.  As a customer, you do not get visibility as to whether it is in a public or private cloud. From a customer point of view, you do not know that or it is invisible to you. But in the backend, it now maintains their data and the platform using both AWS and Azure in the background and they use the cloud for that.  

The licensing price for ServiceNow is somewhat high. The pricing depends on the number of users. For a similar type of application, the price of licensing for ServiceNow is on the high side. Actually it is 20% to 30% more than the nearest competitor.  

There are technically not any additional costs besides the licensing fees from a customer point of view for the product. But, if they want to implement an application in ServiceNow, they may also have to pay for a developer's team to implement the solution. Once development is complete, they probably have to spend some amount for supporting and maintaining the application and customization, so that will also be included as an additional cost for the company using the solution even if it is not a direct cost for the product.  

We have evaluated other products but within my company, I only work with the ServiceNow project and I have been doing this for the last four years. Sometimes part of our customer engagement requires that we do comparative studies. For example, we had a request from a client to do a feature comparison with the Pega platform. I got some detailed information from Pega's product development and other resources to compare with ServiceNow and did the comparison in that way. But in terms of development or implementation experience, I do not have any direct experience with Pega.  

The foremost thing I would like to recommend to people considering ServiceNow is not to try to reconfigure or customize the out-of-the-box process too much. Stick to the out-of-the-box processes that are provided as much as possible and use minimal customizations. We used to say to our customers to use maximum configuration but minimum customization.  

On a scale from one to ten where one is the worst and ten is the best, I would rate the ServiceNow product overall as at least an eight.  

We use this solution for taking calls, logging calls, and assigning calls.

We have just moved over to ServiceNow Out-of-the-Box, which is the general platform.

This solution is deployed in a hybrid-cloud environment.

In the past, we only had a solution that we could use locally. This solution has helped us to go global with our IT service management support. We were able to scale it much quicker and support the organization globally.

We have seen a big improvement in the experience that we want to create for our end users. The catalog used to be separated from the IT service, but now we have both of them running from the same platform. This means that we can quickly deploy solutions based on the request from our users.

The integration makes it easier for the end-users, as they can track the status of their incidents and their requests, and they can put in a new request. This one platform, where the end-users can manage all of their demands and see all of their devices, including their cell phone contracts, makes our lives easy. The end-users used to have multiple reference numbers and now there is one that a request or incident is linked to. They get updates, similar to the Amazon platform, where you can see the status of your order and you know how far away they are.

The most valuable feature of this solution is cataloging the requests, which allows us to speed up the process and improve the user experience.

The knowledge management feature is now continuously learning from incidents.

In the next release of this solution, we would like to see mobile capability.

We would like to see AI used to automate some of the functionality in this solution.

We are impressed with the stability of this platform. We are part of Europe, the Middle East, and Africa. Even with multiple languages, it was easy to adopt and to provide users in their respective countries with language enabled according to their needs.

This is a very scalable solution.

Technical support for this solution is excellent. We have had the technologists visit us. They were part of the implementation. Overall, the support we are receiving from this vendor is excellent.

When we implemented and set up this solution for the first time, we did some customization. Now that we have adopted the Out-of-the-Box version, it means less customization. We are taking an "As-Is" solution so that we can use more capabilities for customizing it.

We made use of a service integrator to assist us with the implementation and deployment. We didn't deploy with our own team. These people were qualified and know the product very well, so our experience was very good. The platform providers were also supporting the service integrators.

We did evaluate other options before choosing this solution, but we found this to be an excellent product. We call it the SAP of IT Management.

We chose this product mainly because of the capabilities that it offered, and how they matched what we needed.

The biggest lesson that we learned through implementing this solution is that it is important not to customize. Rather, take the product offering best practices and adopt it with its own processes. This makes scaling much easier. Whereas if you customize it and if you build your own version, it becomes difficult to scale, support, and do the official upgrades. This is why we have taken the Out-of-the-Box version and have adopted the processes that come with it. It is working and we don't have to change it too much.

This is a very good solution, but there is always room for improvement.

I would rate this solution a nine out of ten.

We use the solution for incident management to receive emails and support.

The solution is very comprehensive. It has a very big scope. I never heard any complaints regarding the product.

The solution is very expensive.

We are currently using the solution in our organization.

The product seems to be stable. We use it for very critical applications.

The solution is scalable. We are responsible for an examination in Brazil. We have around one million subscriptions for which we give simultaneous access to the users.

The solution is more expensive than other products. I rate the pricing a nine or ten out of ten.

I work for the government, and we deal with a lot of contracts and services. The companies we contract for services bring the tool they would like to use and the margins they need to provide the services. Our use case for the product is very restricted to the infrastructure sector, but we'd like to use it for different areas of IT. We would like to use the product for portfolio, knowledge, and project management. The contractors implement the tools by themselves. Overall, I rate the solution a nine out of ten.

We use the product to provide our customers with a custom-built platform for their software and other requirements, such as patient detail management.

The solution provides a single platform for multiple systems and software to operate from.

The solution doesn't allow users to create custom tables, which would be a big improvement.

We have been using this solution for almost seven years.

We have found the solution to be stable.

The product is scalable.

The technical support team are very helpful, we contact them whenever we are unable to fix an issue.

Positive

The initial setup and deployment of the solution was very easy.

The licensing models are for this solution are based on the modules that are being utilized, the number of users, and other factors. 

I would recommend this product to businesses who are using multiple systems across different departments, and are looking for a single point to operate them from. I would rate this product as 10 out of 10.

It's part of a suite of other ServiceNow solutions. 

There are multiple valuable features:

• Ticketing tools
• Customers have access to this and they use it. We have an overall contract for it.

We work on it directly to send out tickets. It enables us to work seamlessly, we don't need to send them out manually. We can create a ticket and assign it in the system.

It is a good tool and we can do customization with it. Most areas are quite customized. 

The cost has room for improvement. It is currently expensive.

Some of the features are very particular to the core. The workforce management is another area that can be improved. 

Our customer portal is there but when a ticket comes it requires an additional tool. It would be helpful if they could have better integration with those tools. More standardization can be brought in. 

My company has been using ServiceNow Now Platform for more than five years. 

Overall, it is a very good product. There are bugs that could be improved.

Scalability is not an issue or a big challenge. You can verticalize efficiently. 

I haven't needed to contact customer support. We have our own team that maintains it. 

The initial setup is complex but it depends on the industry. It's not just following steps, it's change management. You have to get it standardized. Overall, though, it's okay. 

The initial setup takes around a month, it's not a matter of days. It's a setup that can take time even if you know what needs to get done. In a larger organization, it's a major challenge. It will take more time to roll out.

I would rate it an eight out of ten. 

My advice would be that it's quite good but make sure to first look at the process. That is the most important part of the implementation. Look up ServiceNow and look at the process. 

I would recommend this solution. It is an easy to use platform. 

We are a service provider and this is one of the solutions that we work with to offer services to our clients.

The main reason that people use ServiceNow is that performance is very good.

There is support for a lot of different services using any kind of device including desktops, laptops, and mobile devices.

This platform is used more by large companies because it is a little bit expensive.

I have been working with this platform for approximately two years.

We have not experienced any bugs or other problems with stability.

We are satisfied with the scalability of the ServiceNow Now Platform.

We have been in contact with technical support and they are good. They have good technical skills.

I have used other ITSM solutions and they often focus on just IT services, whereas the ServiceNow Now Platform focuses on a wider range. The services cover facilities, security, operations, and more. Other solutions are cheaper but they are too focused on IT services.

If you are familiar with this solution then the initial setup is straightforward. However, there are a lot of options so it can be complex. Some of our customers have found it unclear. It takes between three and six months to deploy.

The suitability of this solution depends on the size of the company and the scope. For large companies, this is a product that I recommend.

I would rate this solution an eight out of ten.