ServiceNow Reviews

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.

We use a ServiceNow for ticketing.

We support multiple use cases across several tracks: the database, middleware, ETL, and Abolition track. As a DevOps team, when we receive requirements from the production team related to production issues like memory or infrastructure upgrades, we initiate the process by raising a ticket, an incident, and a change request.

For example, when we procure new servers, whether physical or managed VMs. We submit a change request for the Go-Live, including business tasks requiring approval from different teams, such as our L3 support and service delivery teams. Once all tasks are approved, the appropriate group of approvers authorizes the change. The change occurs during the weekend, provided it falls within the green zone, which refers to a maintenance window designated by the support team. This will follow the same process for submitting a change request. For certain incidents, we also need to raise a separate incident request. For example, if we need to check the table space in the database, we might have to raise an incident to request access or additional permissions.

ServiceNow is a lightweight utility. You can always customize it, which filters out your data and gives it to you based on the selected filters.

As a team lead, the functionality I use most is reporting, where I pull reports on overdue changes to ensure no SLA breaches. Self-service is another feature. The change management feature is crucial, allowing me to track all changes requested or coordinated by my team. Lastly, incident management is also a key feature I use frequently.

We are not supposed to access outside our network.

I have been using ServiceNow for two years.

The product is stable.

I rate the solution’s stability a nine out of ten.

Even if it's a new user, it's a very easy tool for anyone to get hands-on quickly. It is a very user-friendly user tool.

I rate the solution’s scalability a seven out of ten.

I have used BMC Remedy.

We have to submit a marketplace ticket, and it gets installed automatically. So, it's a very smooth and lightweight process.

Our organization uses a bot that interacts with ServiceNow, which helps us create ticket templates. ServiceNow doesn't have AI integrated into our current setup.

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

We use it for IT Service Automation, specifically for managing requests, network management, knowledge base management, problem resolution, and change control processes.

ServiceNow has enhanced the efficiency of our IT service management procedures. Currently, we utilize it to streamline request handling and centralize all requests within the ServiceNow platform. Additionally, we're exploring integration with Microsoft's pilot program, which will soon feature bots seamlessly linked with ServiceNow. We aim to consolidate all channels onto one platform, ensuring a streamlined process for all involved.

ServiceNow facilitates our incident response and resolution workflows, meeting nearly all of our requirements and KPIs.

We use ServiceNow's integration with the MDB, linking it with the MC for discovery decisions. Our database management is handled within ServiceNow.

Our integration of ServiceNow with existing systems and tools is progressing smoothly, primarily facilitated by APIs.

One of the advantages lies in the implementation of the ITIL process, which becomes more scalable and readily integrated within ServiceNow. With predefined processes, the transition is seamless and ensures efficiency moving forward.

It offers ready-built automation and simpler configuration for workflows.

Some features within ServiceNow have negatively impacted productivity, particularly in managing the entire process. Transitioning from Jira to ServiceNow has proven challenging for end users, as requests now involve multiple tasks, IBM numbers, and request numbers, which can be confusing. The ticketing system is also complex, causing confusion among teams and complicating reporting. Regarding incident management, while the process remains similar, end-user feedback indicates an overwhelming amount of unnecessary information, leading to confusion.

There is a need to enhance ticket details visibility on the portal, such as displaying SLA information, which currently requires development effort. Additionally, there's a need for line manager approvals, especially for requests like license procurement, which is currently managed via teammates. Developing a feature specifically for approvals could alleviate the need for additional licenses. There are challenges with SLA reporting due to SLAs being configured as tasks. This leads to difficulties in accurately reporting SLA compliance, as one ticket may have multiple SLAs. Addressing this issue would improve reporting accuracy.

I have been working with it for six months now.

The current setup is stable, yet there's a pressing need for continual enhancement in processes and procedures.

We are currently in the testing phase, so it's premature to conclude within just six or five months. While the capabilities are present, it may take more time to ascertain whether the system is fully functional and reliable. We have approximately seven thousand users, and the deployment spans across seventeen countries.

The technical support team consistently provides accurate responses to my inquiries, whereas the developer sometimes attempts to evade the support team's answers. In certain scenarios, I've received resolutions directly from the support team while the partner tries to manipulate the situation. I've maintained direct contact with the support team, who are proactive in providing solutions. Even when they don't have an immediate answer, they make an effort to provide guidance through articles, videos, and other resources. I would rate them nine out of ten.

Positive

I find little distinction between Jira and ServiceNow in terms of management data, as we initially opted for the standard license, which didn't impose limitations compared to Jira's standard license.

During the initial setup, I faced significant challenges with our partner developers as they struggled to grasp our requirements and insisted on their preferred approach rather than following our needs. Despite encountering difficulties during the development phase, we ultimately achieved our desired outcome. However, I believe that collaborating with different partners may have yielded better results.

The deployment, initially scheduled for six months, ended up taking approximately a year. Around three developers were in charge of it, who also handled maintenance tasks. Despite facing delays, we continued working with the same partner due to our familiarity with the environment.

We haven't seen a return on investment so far. However, there's potential for improved ROI as we develop, enhance, or onboard additional departments, which may lead to better outcomes.

The licensing expenses are excessively high. To illustrate, consider Jira, a platform we've utilized for ten years. Under a standard license model, we have been paying five times the cost compared to Jira, despite having an equivalent number of licenses.

The product itself is satisfactory, offering all the necessary features and functionalities. However, the quality of the outcome heavily relies on the competence and dedication of the developers. Without continuous oversight and intervention, the result may vary from excellent to subpar. Therefore, the success largely hinges on the capabilities and commitment of the developers or partners involved. Overall, I would rate it eight out of ten.

We began by providing internal and customer advisory services, focusing on ITSM. We replaced products from IBM, HPE, and BMC, migrating customers to the ServiceNow ITSM platform. In some cases, we also transitioned customers to ITOM after stabilizing the ITSM product. This initiative started around 2015 and continued into 2016 and 2017,

ServiceNow has been implemented to streamline team workflows across different departments in our company. Users, including traveling leaders, were able to approve requests and authorize additional rights through the mobile platform. 

Subsequently, we integrated HR, cybersecurity, and other teams into the workflow for employee onboarding and offboarding. The system proved particularly beneficial for managing employee movements between projects and departments. 

In incident and problem management, we find ServiceNow's ISO compliance features to be highly valuable. The system manages the entire process, ensuring compliance with ITSM standards, and providing a complete audit trail that is useful for auditors and certifying authorities. Another significant benefit is the integration capabilities of ServiceNow's IT workflows.

ServiceNow's ease of use allowed us to establish numerous shared services. Various critical transactions, as well as routine service requests and queries, were migrated to the shared ServiceNow platform. This transition freed up resources in HR, finance, procurement, and IT administration, enabling our staff to focus on more meaningful tasks.

The tool's ITOM products are useful. 

The challenge with ServiceNow lies in its expansive portfolio of services. It can be complex, and users may find it expensive and challenging to understand. There is a need for a configurator within ServiceNow that guides users on how to utilize the tool effectively. This configurator should provide insights into licensing, team requirements, and the best licensing model based on whether companies prefer ownership or consumption-based models.

ServiceNow has been deployed in both on-premises and cloud environments. However, the cost of using ServiceNow, especially for IT Operations Management is high. This expense has led customers to explore alternatives such as Freshdesk or other products in the market.

I have been using the product for ten years. 

I rate the tool's stability an eight out of ten. One challenge with ServiceNow is occasional failures and availability issues, although they are rare. In case of critical operations being impacted, there is no recall available.

I rate the solution's scalability a nine out of ten. 

The tool needs to improve its documentation and the providers need to stay updated with all the offerings. The certification process of service providers should be reviewed as not all of them are up to date with ServiceNow offerings.

Neutral

I rate the product's deployment a six out of ten. Its deployment depends on factors such as the customer's existing backend setup and the organization of their data. For a fresh implementation, it can be fast and straightforward. However, if data migration and the creation of custom workflows and integrations are involved, it can take longer.

I rate the solution's pricing a six out of ten. The pricing for ServiceNow is based on a SaaS platform with annual contracts. However, it may not offer much flexibility for adjusting usage in the short term.

The solution is suitable for enterprises. It is not advisable for small and medium businesses. The tool comes with a developer's toolkit which offers integration possibilities. It goes beyond traditional IT functions, becoming a business solution used across various departments. With its development capabilities, ServiceNow facilitates applications in core functional areas, such as operations.

ServiceNow is good for many types of business needs and is better than older products. However, it faces tough competition from newer platforms. ServiceNow keeps getting better with new features, but its value may change. Automation is easier now, and people who use it are more familiar with technology.

I rate the overall product a seven out of ten. 

The most valuable features of the solution are the ease of use and the sensor for ticketing systems. In terms of the reports generated out of the metrics, specifically operational metrics, along with the dashboard, are very good in ServiceNow.

From an HR standpoint, if users can have a very integrated onboarding or offboarding process between ServiceNow and Workday, then it can give a very good employee experience.

I have been using ServiceNow for four years. I am a customer of ServiceNow.

I have had no issues with the tool breaking down or bugs. Stability-wise, I rate the solution an eight out of ten.

I had no issues using the tool's scalability feature. Scalability-wise, I rate the solution an eight out of ten.

In our company, we have formed an in-house ServiceNow support team to help us.

I have no experience with other solutions before ServiceNow.

The product's initial setup phase is a bit technical in nature.

The solution is deployed on the cloud.

The solution can be deployed in six to twelve months.

My company has a dependency on ServiceNow partners who can be part of the implementation process.

To those who plan to use ServiceNow, I would say that it is always good to use the system for case management. ServiceNow is a platform that allows a company's customers, including the employees and stakeholders, to connect with the services revolving around HR or digital technology.

I rate the overall tool an 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.

We use it for HR, IT, finance, and many other processes. A lot is automated with ServiceNow.

We use automation, SCMBB, incident management, problem management, change management, VM access management, and more.

There is room for improvement in price. 

I have been using it for more than five years now. 

It is highly stable solution. 

The scalability is low. There are around a thousand end users using this solution. I used it daily.  It's core to our operations.

We always get good support.

Positive

We used an internal, self-coded solution. We needed more features and functions, like CDP and other integrated solutions for broader support.

I would rate my experience with the initial setup a six out of ten, with ten being easy. Not super easy, but not super difficult either.

Overall, deployment took us a few days. It's still ongoing as we integrate with internal systems, but the core setup was quick.

It directly connects to our main database for authorization and asset storage. It's also part of our ERP system and connects to various management systems. We have a lot of systems that connect to ServiceNow.

We always use an integrator. Around five engineers from the integrator. 

Two or three engineers manage it.

I would rate the pricing a six out of ten, with ten being expensive. 

It's the best for me. I would rate the solution a ten out of ten. 

The solution has greatly enhanced our organization's ITSM processes. ServiceNow provides quite good insights about what is happening in the organization. I haven't seen any other products with the kind of flexibility and customization you can do with ServiceNow.

Putting some custom scripts into ServiceNow is easier than any other product. ServiceNow has a lot of out-of-the-box connectors. If I want to create a ticket using Microsoft Teams that has an out-of-the-box connector, I can directly integrate ServiceNow with my Microsoft Teams. I can go ahead and create a ticket there, update that ticket, and close it.

The most valuable feature of the solution for our workflows is mostly related to the experience part of it. Not everybody has to log in to ServiceNow to see its status. Most of us often use Microsoft Teams for collaboration. We have chatbots available that we can use to see the status of our ticket, and it gives the response immediately. The support team does the ticket updation in Microsoft Teams itself.

During a crisis or major incident, the team opens up a Teams channel where they can diagnose and resolve the issue and then update the ticket from the Teams' console. Nobody has to log into ServiceNow and keep switching between the multiple windows.

The solution’s pricing is expensive and could be improved.

I have been using ServiceNow for seven years.

I rate the solution a nine out of ten for stability.

More than 1,000 users are using ServiceNow in our organization.

I rate the solution a nine out of ten for scalability.

The solution’s deployment time depends on my customer, but it typically takes around two to three months. A team of four to five people, including architects, developers, project managers, and SMEs, was involved in the solution's deployment process.

ServiceNow is an expensive solution. Users can pay monthly or yearly licensing fees for ServiceNow.

I rate the solution's integration capability a nine out of ten. ServiceNow is deployed on the cloud in our organization.

I would recommend ServiceNow to other users. ServiceNow is the best product for large enterprises looking for a total landscape transformation to get the best out of the system and the best single source of records.

The solution's automation capabilities helped us greatly reduce our team's manual tasks. ServiceNow's reporting analytics tool is quite insightful, and you can do a lot of customization around it. The reports can be sent automatically.

Overall, I rate the solution ten out of ten.