The environment previously was for 60,000 users, 30 active users, about 2,000 servers, and it supported a $6 billion business. Today, in this job, I am working for a $15 billion business with 6,000 users, about 1,000 servers.

Some of the best features of ServiceNow are that you have a single data set and you don't need to re-enter data. You can reuse the data or grow from it, compact it, expand it as you move through different modules. That's the beauty of ServiceNow, and nothing else beats that.

The customization capabilities of ServiceNow have benefited my organization for workflow agility, which is very high if we use every module with ServiceNow. There are circumstances where we can't use every module for every operation we have. If we do use it, we use it with the ITSM, using all of it from CMDB with change management to incident management to problem management. We didn't use the project management; we used it for a little bit and then pivoted to something else.

I think that nothing needs to be improved with the product; you just need the user to commit and spend appropriate time to overcome that learning curve. Once that is done, the product itself is pretty wonderful. I've seen a very nicely built interface with ServiceNow, and I've also seen the ugliest version that feels outdated. ServiceNow does allow that team to exist. They should modernize their fonts and their layout, the UI friendliness. They did introduce AI, chatbots, and AI on the back end, so that's wonderful and extremely useful if you train it. If you don't train it, it's pretty useless.

Assessing the impact of ServiceNow's automation on service delivery times is complicated. The engineers who operate on ServiceNow find it isn't straightforward because the data set is accessible by everybody. The problem is that understanding how to manage that data set requires an enormous amount of engineering skill set to run the product. I would not hand the key to the customer; I would highly recommend that ServiceNow take control of that. Instead of offering support for the software, they should offer administrative support for the software. They should provide professional service or some kind of support system that allows us to use their product at a faster pace. I'm sure they offer something, but it's often outrageously expensive, or they rely on another company to resell their product and offer professional service. It makes no sense in my opinion, and they should offer the team at the front to help customize the product to fit each company's needs, as every company has different demands and forms of submitting a request that need adjustment over time.

I have closer to four years of experience with ServiceNow, about three and a half to four years.

If you reach out to ServiceNow for customer service or technical support actively, I would rate them a nine out of 10.

Positive

I still have experience with these products and I am currently using ServiceNow solutions in my work.

I don't have any recent experience with ServiceNow Automation Engine or Cloud Observability as I'm not in charge of that. My role today is that I am a prime user for the product, but I'm not in the engineering or support for ServiceNow.

I support the security side of ServiceNow. I deal with Security Operations as I support the security operation. The SOC team has their own leader that drives this, and I'm on the engineering side.

We integrate the ServiceNow Security Operations solution with the SIR. SIR is Security Incident Response inside ServiceNow, and it's a module within ServiceNow.

I don't know if ServiceNow is using a cloud provider AWS or Azure, but whatever ServiceNow is subscribed to is up to them. We don't know what the back end is. ServiceNow guarantees that themselves, so I'm assuming it's AWS typically.

I do use the incident management capabilities. They have improved IT incident handling because it's always been the best, second to none when it comes to their ITSM module.

The impact of ServiceNow's self-service portal on IT staff dependency levels has shown a dramatic improvement. Previously, they used a self-made dynamic system, which had no maturity. After adopting ServiceNow, we don't need to rely on another team to create reports. I always think that ServiceNow reporting is more advanced than anything, because the dashboarding is easy to use. To some people, it is not. I felt that if you need anything to manage your team, the ServiceNow dashboard is wonderful, but it does come with a high learning curve.

ServiceNow's AI-driven analytics helps with anticipating challenges by moving information faster. However, there's no clear-cut process, because deploying that technology was so hard, it made it a little bit difficult to deliver. The technology is great, but it requires a lot of knowledge and abilities to work with different parties to get the product to take off. ServiceNow claims to help a lot, but once you sell the product, it's as if you're on your own.

I am familiar with different types of IT asset management products. I don't remember what other products I used that I could compare it to.

On a scale of 1-10, I rate ServiceNow a 10.

I worked for four to six months with ServiceNow, and then I left it and am generally using more GenAI open-source platforms now.

It was just for one or a few projects that I implemented ServiceNow.

I mainly used it for the development of some no-code platform, but it was very limited usage, after which I moved on.

I didn't do any sort of incident management.

I used it for some sort of analytics to help overcome challenges and check what was wrong if something was wrong.

It did help me see some benefits from using it.

In terms of time, it helped me save time.

It would be more than 30% in time savings.

There were less man-hours in terms of automation capabilities. It helped me with faster service delivery times.

It was faster to develop with ServiceNow.

ServiceNow's customization is not too agile in those cases; it takes a little bit of time.

They should integrate open-source LLM tools and make it a further low-code, no-code build with GenAI. I'm not sure if it is there, but if they can make it a no-code, low-code with GenAI, that would be much better.

I worked for four to six months with ServiceNow, and then I left it and am generally using more GenAI open-source platforms now.

It was easy for me to initially set up this tool.

It took approximately a couple of days to set up ServiceNow.

There were no downtimes, and I never had any sort of technical errors or stability falls.

Regarding scalability, I didn't feel that at any point this tool was not scalable enough or that I had to increase my usage.

I didn't need to contact the technical support of ServiceNow.

Neutral

I didn't actually choose ServiceNow over something else on the market because this came recommended heavily by our CTO.

It was easy for me to initially set up this tool.

It took approximately a couple of days to set up ServiceNow.

I am using some of the no-code, low-code platforms which are more GenAI, such as L-Leverage and others when comparing ServiceNow to something else that I'm working with.

I can't remember any noticeable difference in features or performance when comparing those tools to ServiceNow.

ServiceNow was really good back then, but now there are many other tools which are working better if it was my choice.

I already gave feedback about ServiceNow some time back.

It was more Orchestration, but it was two or three years back.

On a scale from one to ten, I rate ServiceNow a six out of ten.

One of the main use cases for ServiceNow is implementing the complete ITSM module from scratch, which includes Incident Management and Change Management, ensuring that the CMDB is right, coming from Device42 or self-service discovery, and also includes the employee center, which is the end-user interface for ServiceNow.

Device42 is something that we integrated with ServiceNow, and the ServiceNow Discovery is something that we're currently doing.

One of the most powerful or useful features of ServiceNow is the AI features announced in the Now in Knowledge '25, specifically AIOps for ITOMS, which implements solutions for the infrastructure teams.

I have definitely seen a positive impact of ServiceNow on our company and customer processes, including time savings and money savings.

I don't have anything on top of my mind regarding improvements that could be made in ServiceNow, but AI features are indeed a step forward.

I have been working with ServiceNow for almost 8 years.

I have no complaints regarding stability, scalability, or deployment issues in ServiceNow; everything is perfect.

I have no complaints regarding stability, scalability, or deployment issues in ServiceNow; everything is perfect.

I have no complaints regarding stability, scalability, or deployment issues in ServiceNow; everything is perfect.

My experience with technical support of ServiceNow is that they are good, but they could be better.

Time to respond from support could definitely be better, as the global support timing sometimes causes delays in interactions.

Positive

I'm comparing the save in man hours, but determining how much it can save is a difficult exercise.

Manually, there are huge numbers that come up because these integrated tools help organizations make the right decisions with all the information in one place, while manual methods lack visibility.

The cost effectiveness of ServiceNow depends upon the organization size, as larger organizations might find more value, and while there are other tools in the market, comparatively, ServiceNow is more advanced and highly effective when it comes to ITSM, although it does come with a price.

The clients that I work with for ServiceNow are typically enterprise level businesses, which includes engineering companies and manufacturing companies.

I would rate the support of ServiceNow an eight on a scale from 1 to 10.

I would rate ServiceNow a 9 on a scale from 1 to 10.

I use ServiceNow for everything from ticket management to demand and more in my daily work.

As I manage the automation COE team, I've found that getting incident reports and handling demands from different markets is quite useful with ServiceNow. The dashboard helps us track data effectively and see the outcomes, making it very valuable. Although I'm not a heavy user of ServiceNow, I find the delivery for the COE team to be really good compared to previous tools I've experienced.

The features of ServiceNow that I find the most useful include the impressive handling of incident reporting requests, which go into the cab with types, priority types, and the SLA that we can set. The mobile client is also really good, allowing everyone to view demands, requests, and incidents through the mobile app, which has a great UI and user experience.

Overall, apart from not using it extensively in terms of API, as an end user, the demands, requests, service catalog, and incident reporting are much better compared to what we were using earlier.

I haven't thought deeply about improvements for ServiceNow or what might be missing right now.

There are so many modules and features in ServiceNow that I haven't explored them all, so it's hard to say what might be missing or should be improved.

I suggest making the cost more affordable for smaller companies.

I have been working with ServiceNow for about the last three or four years.

I haven't faced any issues with stability; I've rarely seen any downtime.

Downtime is something I've experienced very little.

I haven't faced many problems or challenges with ServiceNow; I haven't seen any downtime, except for scheduled maintenance.

Scaling ServiceNow is easy since it's on cloud, so there are no issues.

I have not contacted ServiceNow support personally, but my team has a dedicated team that reaches out when necessary.

Positive

Earlier we were using Cherwell for IT service management, and now we use ServiceNow.

It's easy to set up ServiceNow; they have guides and everything.

It's a great tool that I've recommended to startups here in Malaysia. It may be expensive for small companies, but for big companies, I think it's good. If there's a lighter version of ServiceNow that could be more affordable for smaller companies, that would be beneficial.

Within my company, I haven't seen AI functionality being used, but there's knowledge sharing happening and it's in process for assessment. We will get those AI capabilities into ServiceNow in the near future, but currently, it's not enabled.

I'm just using ServiceNow as an end user, and I have not utilized API for integration or anything.

The performance and customization areas are quite good; I have no issues there.

I would rate ServiceNow nine out of ten.

I am currently working in a previous organization as a second line support engineer, and while I am working there, I update my regular activities and support details in ServiceNow, so you can ask me regarding that without any problems.

My relationship with ServiceNow is as a user who creates requests regarding issues such as machines not properly connected to the internet or printers not working, and I have access based on the support profile.

I use ServiceNow to investigate issues, update my findings, and fix the issue directly, or if any on-site intervention is required, I forward it to my next level or escalation. For day-to-day activities, such as rebooting servers, we want to get a change request approved before proceeding after business hours or on holidays, and we keep the ServiceNow ticket in my queue, updating our findings with screenshots and details before closing the tickets.

The features of ServiceNow that I find most valuable include its ability to easily access ticket details if you know the ticket number, monitor the timeline of when the ticket was created, and see the current status, which makes ServiceNow the best tool I have ever used.

The integration capabilities of ServiceNow allow us to enhance our existing environment easily, so I rate it as a nine.

The return on investment from ServiceNow may be around 8.5, indicating time-saving benefits or fewer people needed to operate with this solution.

While ServiceNow has many options, the number of options can sometimes be confusing regarding where to click or how things work, as it is based on configuration provided by the administrator.

The initial setup of ServiceNow was easy for me, and I can easily access the knowledge base, pass tickets to another team through internal notes, and each individual will get a personal email when a ticket is placed into their queue, although sometimes the numerous options can be confusing.

My experience of working with ServiceNow is approximately one year.

I rate the stability of ServiceNow as a nine on a scale of one to ten.

I rate the scalability of ServiceNow as an eight on a scale of one to ten.

I might be unsure about how many users are using ServiceNow in my organization, but it could be around 500.

I rate the technical support of ServiceNow as a nine on a scale of one to ten.

Positive

I have experience with other solutions, such as Freshdesk, ServiceNow, Zendesk, ConnectWise, Azure platform, and Ivanti.

The initial setup of ServiceNow was easy for me.

The return on investment from ServiceNow may be around 8.5, indicating time-saving benefits or fewer people needed to operate with this solution.

Regarding the price of ServiceNow, I am not certain because our management team takes care of all pricing details, but I know it is quite high in the market.

Based on my experience, I would recommend ServiceNow to other people. I give ServiceNow an overall rating of nine out of ten.

The use case for ServiceNow was that one of our clients was using some other tools for the ticketing system, which was an on-premise tool that presented a lot of hassle with respect to infrastructure challenges. They contacted us, and we evaluated different cloud-based solutions such as Jira, ManageEngine, and ServiceNow. After the demos and evaluations, they adopted ServiceNow, and we migrated all their workflows from the legacy system to ServiceNow.

The key points, both pros and cons of ServiceNow in comparison to Jira or ManageEngine technologies, are that it offers an object-oriented architecture, which is more flexible and allows us to customize the workflows quite easily. Additionally, the user interface is very much aligned with the requirements of the customer.

Feature-wise, the object-oriented architecture of ServiceNow is very much helpful for designing the workflows and similar tasks.

I have seen ROI from ServiceNow, as the client I mentioned earlier is achieving ROI for adopting this cloud-based technology. They have removed the costs associated with on-prem infrastructure, including data center costs, power costs, and physical server costs.

There are things that I would like to see improved in ServiceNow, such as the pricing, as it is a very costly solution compared to other tools. Additionally, its presence in the local market is very limited; in Pakistan, for example, I don't see any vendor or distributor of ServiceNow available. They need to increase their sales spectrum globally so people can easily access them and engage them for client meetings and more.

From a functionality perspective, the features in ServiceNow are acceptable as, at the moment, the ITSM modules rank highly, being 13 plus Pink Elephant certified, which is a good aspect to have.

When providing advice to users, I would suggest they consider making strategic decisions about their per user pricing since it is very high. In our region, people normally start with 5 to 10 users, but the per user price is quite steep. Moreover, ServiceNow does not charge based on data uploaded or downloaded, so they should reconsider their pricing and data policies to align better with the financial capabilities of the region.

I have been working with ServiceNow for more than a year.

The initial setup of ServiceNow was straightforward; I did not face any challenges or complexities during the implementation process because it is instance-based, so everyone can sign up with the instance online and get it ready.

From a performance point of view, there are no limitations or performance issues with ServiceNow; it is cloud-based, so it is highly scalable and performs well.

From a performance point of view, there are no limitations or performance issues with ServiceNow; it is cloud-based, so it is highly scalable and performs well.

I would rate the technical support of ServiceNow a six on a scale of 1 to 10, where 10 is the best.

It is not difficult to maintain ServiceNow; it simply requires sending a request. However, obtaining support for maintenance is the current challenge because they don't have a presence in the local market.

Neutral

Our client was using other tools for the ticketing system, which was an on-premise tool that presented many infrastructure challenges.

The initial setup of ServiceNow was straightforward; I did not face any challenges or complexities during the implementation process because it is instance-based, so everyone can sign up with the instance online and get it ready.

It took me between 3 to 6 months to migrate from the legacy system to ServiceNow, depending on how many workflows needed to be migrated.

I have seen ROI from ServiceNow, as the client is achieving ROI for adopting this cloud-based technology. They have removed the costs associated with on-prem infrastructure, including data center costs, power costs, and physical server costs.

All the modules of ServiceNow are equally important, but initially, I can say that the change management and asset management modules are the ones that I recommend to our clients.

I have utilized automation capabilities in ServiceNow by introducing workflows. The main goal of designing automation workflows was to achieve automation.

It has been successful as my clients have completely gotten rid of that legacy system and are now using the ServiceNow solution.

I have not had any AI features or AI-driven initiatives with ServiceNow.

Regarding the integration capabilities of ServiceNow, I don't know as we did not use any kind of integration.

In terms of the size of the environment, there are more than a hundred workflows.

From the end users' perspective, there are around 75 users.

Overall, I would rate ServiceNow as a nine as a solution and product.

We mainly use ServiceNow for workflow definition, primarily for ITSM purposes. It is utilized across the whole organization for functions, from employee onboarding to various operational activities. We leverage different use cases for HR functionalities, IT applications, IT operations, IT support, finance activities, and project submissions.

The workflow management in ServiceNow is amazing. The integration with third-party business applications is extraordinary, providing compatibility with major vendors like Microsoft, Oracle, IBM, as well as with custom-built applications. Automation capabilities are impressive, bolstered by a vast repository of out-of-the-box connectors and plugins that facilitate integration with various applications worldwide.

The main area for improvement in ServiceNow is its support. Their customer support could make it a great solution, not just product support but also their relationship with partners and training initiatives in different regions. The official support is often distant, and many partners are not up to standard, which harms the product's reputation.

I have been working with ServiceNow for approximately six years now.

From a stability perspective, ServiceNow has almost no issues.

ServiceNow is a very scalable solution. I would rate it 10 out of 10 for scalability.

Direct support from ServiceNow is not very good. Most of the support comes from partners, and customers heavily rely on them. I would rate it 6 out of 10.

Neutral

We evaluated other options, like ManageEngine, and performed POC for multiple environments. We chose ServiceNow because of the wide range of use cases it offers. It is a one-time investment that takes substantial time and resources.

Setting up ServiceNow involves unique system requirements, and compared to other ITSM solutions, it's more challenging to implement effectively. The standard deployment takes at least two weeks if everything goes smoothly.

Professional resources are essential for setting up ServiceNow because the environment is substantial, and you need competent personnel to implement the numerous components efficiently.

We can easily quantify the return on investment during the six years with ServiceNow.

ServiceNow is expensive for all regions. The licensing cost per year per user is not precisely known but is considered high.

We evaluated other solutions like ManageEngine before selecting ServiceNow.

If someone decides to implement ServiceNow, they are taking on a significant responsibility. The success or failure relies on the time and effort planned. For a mature implementation, it may take two to three years, and investing in quality resources and understanding business requirements in advance is crucial. Overall, I rate ServiceNow 10 out of 10.

I use ServiceNow to log tickets, raise incidents, and handle change requests for different environments by utilizing various categories, situations, and service assignment groups. I track all tickets related to issues or enhancements.

ServiceNow helps us track tickets related to issues or enhancements efficiently.

The most valuable features of ServiceNow for me are its ticketing and reporting capabilities. Additionally, its integration is great; I have integrated several C# applications to track or update the ServiceNow situations, reference columns, or tagging, which is also very easy. Once I understand the process, customization and exploration become possible using my personal code, which is a significant advantage.

There is a need for bug or error tracking in ServiceNow. Although there are child incidents or tickets, tracking primary issues or bugs within enhancements is not present. The reporting features in the new portal could be more user-friendly. While it provides options to minimize chart and image sizes, actual implementation doesn't always reflect these changes.

I have been working with ServiceNow for four to five years.

ServiceNow is already a stable tool. There is no doubt about its stability, and no additional measures are needed.

ServiceNow is quite scalable within my company. My account fully utilizes ServiceNow, with no other tool in use. It is capable of vertical scaling with no issues.

I have contacted ServiceNow support multiple times and their response is very quick. The support is exemplary and deserves a perfect rating.

Positive

Before ServiceNow, I was using HP ALM, GitHub, and ADO. Reporting in ServiceNow is easier compared to these other tools. However, HP ALM and ADO have capabilities to create bug tickets, something ServiceNow lacks.

The initial setup is very easy due to its user-friendly interface. New users can understand it quickly without any problems.

Before using ServiceNow, I evaluated HP ALM, GitHub, and ADO.

I recommend ServiceNow due to its stability and good security. It integrates well with Active Directory, making it easy to manage users without separate licenses or access controls. 

The overall rating for ServiceNow would be ten out of ten.

I primarily use ServiceNow for client development. We have specific clients, and we offer consultation for them. Our tool also handles project management.

For our work, ServiceNow's service catalogs and SDK integrations are the most valuable features. It offers integrations like the mid server integration and others. ServiceNow provides a wide range of functionality, covering all the necessary modules, unlike Jira which is primarily for IT.

There are sometimes challenges with the portal being a bit confusing for new users. The implementation of the portal and workspaces is quite different, and improvements in this area would be beneficial.

I have been using ServiceNow for around two and a half years.

ServiceNow is stable enough. They provide good solutions if there are any issues.

We haven't faced any scalability issues. ServiceNow is scalable and meets our needs.

The tech support is good. I have contacted them four to five times over the past two years, and they have been quite helpful.

Neutral

I have only used ServiceNow solutions. I did not evaluate any other solutions before using ServiceNow.

The initial setup depends on the complexity of the project. It can take two to three months or even up to two years, based on the project's requirements. I would rate it seven point five out of ten for ease of setup.

The return on investment is good when implementing for ourselves and for other clients. The ROI for projects is favorable.

The pricing depends on the complexity. If only using modules like in Jira, ServiceNow can be more expensive, but it offers more functionality. ServiceNow's pricing can be justified if more functionality is required.

I recommend considering the functionality and user-friendliness before deciding on its implementation. 

I rate ServiceNow eight out of ten.

We're using ServiceNow for the entire chain process and all aspects of the module. It covers all modules and their associated problems.

It offers significant benefits due to its compatibility and comprehensive approach. Consolidating multiple functionalities into a single platform reduces the need to invest in various separate solutions. ServiceNow integrates ITSM, CMDB, Discovery modules, and more into one cohesive system. This unified approach provides a single view across all modules, reducing complexity and financial risk. By using a single technology, organizations can effectively meet their needs and address potential risks more efficiently.

This was very helpful in CMDP, particularly regarding extraction and workflows. The benefit lies in having a single console rather than multiple consoles, which significantly simplifies the process and improves efficiency.

ServiceNow has had a similar pattern, but when it comes to third-party integrations, Uddin appears to be more flexible than ServiceNow. ServiceNow might need to improve its capabilities to integrate with third-party tools.

Due to differences in naming conventions and data fragmentation between systems, we need to address compatibility issues by modifying naming conventions, altering fields, and making adjustments as necessary. ServiceNow has default field functionalities that may not align with those the MagOne system provides. Therefore, customization will be required to ensure compatibility and meet specific requirements.

I have been using ServiceNow for six years.

The product is stable.

Deployment depends upon the environment. For me, it takes three months to deploy the solution because it has different dependencies.

It saved 30% of the money compared to others.

We have three competitors. One is BMC product, the second is ServiceNow and the third is Atlassian.

ServiceNow provides insights into topology, though it may sometimes lack detailed understanding. We have correlated it with our monitoring tools to trace the hierarchy and determine its impact across various business lines. This is part of the AIOps information, consolidating all relevant details into a single ticket for easy access.

I recommend the solution.

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