What is your primary use case for ServiceNow?

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

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.

We are using ServiceNow as a helpdesk.

We use the product as an incident management tool and receive alerts via email.

ServiceNow is a powerful tool, but to utilize its features most efficiently, it requires proper fine-tuning and design. When developed according to specific requirements, it becomes an excellent solution for ticketing and reporting management, offering enhanced capabilities for streamlined operations.

The solution is being used for our ticketing system.

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

The main use case of the product involves providing solutions for customers aiming at enhancing their overall business efficiency and effectiveness in managing IT services and operations.

I have been exploring the wireless designer service on ServiceNow.

We utilize it as a ticketing tool for the customer support team. It helps us manage digital workflow and possible incident alerts.

We use ServiceNow for configuration management. We're currently setting up the CMDB as well as the help desk.

I work in the compliance department at my company, and we use ServiceNow to manage our team members' tasks.

We use the solution to manage a suite of applications.

Waiting for the next generation ITSM Solutions, ServiceNow is just another flavour of the old school Service Management tools, with an over-reliance on Java scripts, poor wizards, and a disjointed Process Designer. It's just going down the same path as BMC, while carrying legacy baggage from HP/Peregrine and Remedy design concepts. In this modern era with AI, Machine Learning should be little need for Java scripting (Not the norm but an exception). The AI capability is a "Bolt On" and not integrated into the base product *mistake of all old school products" and requires a separate license for those reasons.

CMDB first always (the quality of everyone else depends on it).

Many organizations use this solution for event management. They integrate their monitoring systems with ServiceNow for events and incidents. ServiceNow is also used for the automation of tasks such as the launching of AWS or Azure.

I'm a service manager, so I'm mainly focusing on customers' CMDB, incidents, changes, and problem management tasks. We have many global customers with network solutions.

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

I mostly use it for change management.

I'm in the public service sector, and it is used for public services. In terms of deployment, you normally buy ServiceNow on the cloud. You can also have it on-prem, but they're not very keen on giving you that option. So, more often, it is on the cloud, which is very difficult for my type of clients who are not based in America because ServiceNow Cloud is all on American hyperscalers.

We are a system implementor and ServiceNow is one of the products that we provide to our clients. I have customers in the banking and retail industries that I manage using ServiceNow. I primarily use the ITOM module and don't use the ITSM features.

I'm a ServiceNow consultant and my company is a service provider where we are deploying ServiceNow ourselves on-premises. Here it is primarily used as a service catalog and in BIZBOK-developed services and knowledge management. As a ServiceNow partner, we also offer it in a ServiceNow-like cloud to end customers and we do consulting and projects with it as a third party. Our current customer sees especially heavy usage of ServiceNow, with between 100-150K accesses per month, and up to a million users who access it in total. We are one of many third parties who are involved in this project.

We used ServiceNow for various functions like incident management, ITSM (information technology service management), and we also used it for CMDB (configuration management database). I worked for a manufacturing company and we were using ServiceNow for managing the company's IT functions, particularly for ITSM. In my current company, we use it for CMDB.

The product is primarily used for HR service delivery, traditional IT service management, and, increasingly, integrated risk management, or IRM. The biggest area of growth is what we call creator workflows. This is building new applications on ServiceNow, using ServiceNow as a development platform. That's the biggest area of growth for us.

We primarily use the solution to support Airbus Helicopters. It's great for handling support tickets and onboarding employees.

We have several applications of the product, however, the main use case is to generate all the backlogs of the different squads where we assign histories and we can link this to concrete people. The histories and the tasks that we draft within the histories are used for creating all the burn charts in agile and to show the velocity of how well it was the last sprint in terms of shipments. This is the key purpose. We also use ServiceNow to log IT tickets and to trace them. Those tickets can be created directly as a ServiceNow history on the IT squads. This will go directly to their backlog. It is a quite nice interaction. It's used to manage the sprint in agile to create all the backlogs and to activate the current sprints, to create the burnout charts of the velocity of the sprints, and also to register any IT-related support ticket requests.

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

I worked on the CMDB configuration management setup, and then previously I worked on software asset management also and hardware asset management also. I did a little bit on the ITSM side also.

I am a customer of ServiceNow. We use the solution for operations and ITSM.

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

My primary use case of this solution is for tickets.

We primarily use the solution for IT Operational Management.

We use ServiceNow for asset management. I manage the IT contracts that are in ServiceNow with the metadata that we have. I'm the associate director for IT contract assets.

ServiceNow can be used for service requests and change management.

I previously used the on-premise version of ServiceNow. It was a better fit for companies and banks because of their tech security protocols. But for my work with my current company, I am considering the cloud solution because we already have all the other software components in AWS.

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

Most of our tickets go through ServiceNow. Any tickets that we need to open in order to interact with other teams and make things happen go through ServiceNow. When I need to create an AWS account, I use ServiceNow. I need to use ServiceNow to request a new machine. We use ServiceNow for everything that requires us to interact with other teams. They use it for internal communication across all departments.

We use it as a tool to develop and monitor attestations and assessments where we develop questions based on our policies and ask application owners to explain and show compliance with our policies through a series of attestation questions. I refer to it often when I'm looking up applications in the CMDB. The CMDB gives me a lot of information on the application in terms of what certain parameters are, who owns the application, and what's the structure of the organization owning the application. It gives me a fair amount of information. We are using the latest version. We stay up to date with all the patches.

We use ServiceNow as a ticketing tool that processes and catalogs customer service requests in our organization.

I implement ServiceNow for our customers. I'm a reseller and we are partners of ServiceNow. I'm the company business developer.

Multi Tenant, Scalable, Flexible and Stable

We use the solution primarily for IT Operations Management, SLA and ordinary day-to-day operations. We also use it for business dashboards and different groups within the company.

We use ServiceNow for ITSM onboarding. We are customers and I'm a system analyst.

I have used this solution to create forms for employees to fill out. The main use is for incident management. They are configuring the asset management in CMDB, and they are installing at this time.

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.

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).

We primarily use the solution for service desk requests, in order to track service desk requests and to know who's asking what and track these requests.

We use it for interim problem change configuration, regress management, and knowledge management.

We are premium partners with ServiceNow and I'm a solutions architect.

We are using Quebec, which is the latest version of ServiceNow. We use ServiceNow as an IT asset and business management solution.

We use this solution for managing IT assets and business operations. We are also using it to help make better business decisions.

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.

We use this solution for many things, such as ITFM, incident problem change, configuration, and vulnerability response.

We primarily use the solution just for our ticketing purposes to keep track of our incidents, projects, and tasks. We use it for internal projects, circuit routers, upgrades, keeping track of vendor contracts, et cetera. Basically, it's just a repository of everything that we do and to support our internal clients that deal with maintaining bookkeeping as well as providing the tickets, keeping track of projects, and stuff like that.

I use the solution primarily for IT Financial Management and IT Business Management.

The solution is used primarily to report incidents and then to follow up. It's mainly used for ticketing and incident resolution and tasks of that nature. I look at incidents and see the resolutions and report on that.

We use this solution for incident management, change request management, and service request catalog. These are our three primary use cases. Within our organization, there are roughly 15,000 to 20,000 employees using this solution. We have two staff members that handle all maintenance-related issues. As our mission over the next couple of years is acquisition, we definitely plan to increase our usage of this solution.

I don't actually use this solution directly. We're a partner so we typically find a customer and do the necessary RSC, etc. I am responsible for managing a team of 19 professionals that use this solution and others. I've used ServiceNow in the past, but I am not currently using it.

Everything that I've done over the last six years with ServiceNow has been for hospital systems. It was used at different levels for different clients. Many times, it was being used by the whole organization, but my involvement has always been for the department projects. There was significant effort into reporting and dashboards and some automation for approvals. I am currently using its latest version.

Primarily, we use it for our service desk and IT help desk ticketing. We also have the PPM module. ServiceNow is our main PPM platform at the moment. We use the Idea Portal for project requests, and we are also in the process of installing the financial module. We're using the latest version of ServiceNow.

We primarily use the solution for IT service management and then we're using it for custom applications. That includes digitizing workflows and helping our company with that.

We primarily use the solution for tickets and we use it for order processing. We use the product for incident management, asset management, and service management. Those are the three big use cases. It's mostly asset management.

We mainly use it for requests and tracking incidents. We are onboarding our HR team, and they are going to start using the HR module in it as well. We also use it for asset management and configuration management. We are using the Paris release.

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.

We use this solution for handling help desk tickets and tasks.

We use this solution for Service Management, iCast Management, and Software Management. There are several use cases, you can use them in Education and in Health. We are using the latest version, which is called Paris.

Right now, the primary use case for this solution within my organization is billing. The proposal is to expand our use of the platform to validate privileged requests.

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

We use the solution for workflow automation and business processing.

ServiceNow is helpdesk software that I have some experience with. This is not a solution that I deploy. Rather, I interact with it using hooks between it and NetBrain. It is used for the creation and tracking of tickets and incidents, tasks, projects, and self-ordering. Our parent company uses ServiceNow for ordering and it has been utilized with a lot of different workflows. This is something that we never did but now that we've merged together, and we've merged our instances of ServiceNow, it means more of those self-service tech catalogs now in place and utilized.

We use it for incident management.

ServiceNow can be used for many different use cases such as: * IT service management * Managing Assets * Development and operations * Job processes * Project portfolio management * Managing of infrastructures There are many more modules and HR that I have not yet explored that are available.

We use ServiceNow for all service delivering processes within service management. For service and incident problems, change and configuration management, relief management, and event management. Within our organization, there are roughly 30,000 users, using ServiceNow.

We primarily use the solution for ITSM record catalog incident problems and Service Level Management.

We use it for ITSM and custom applications for the physical workforce.

Our use case is around the core idle processes in general. We use it as a service management capability for managing intercom and so forth.

We use it for our service desk as well as for some asset management.

IT Service Management

We are using ServiceNow for help desk operations. In our operation center, we are using ServiceNow for request management, incident management, inventory CMDB, and client information.

We use the solution as it's a requirement for our standards of use in the future. I primarily use the product to look for tickets. I also check for future projects and so on.

We use it for a combination of things. I would say that the two big use cases that I'm aware of are for logging general acute IT issues. Then they also use it for actual security-specific issues. These are the two main use cases that I'm aware of.

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

I have two primary uses of ServiceNow: 1. As our ITSM Platform for providing Application Managed Services (AMS) to Enterprise clients who have solutions on Oracle, Workday, Coupa, and ServiceNow. NOTE: Other groups within my firm also use ServiceNow to provide IT Service Management to clients on Microsoft, SalesForce, and other major vendors. We have multiple production instances for delivering Service Desk support to various client install bases, including this one for my above mentioned AMS business. 2. As the ITSM platform for our internal, global support framework. This is a separate instance of the one I use for my UK clients and is 'owned' by our US member firm. Said US firm uses this instance to support not only our internal global Management Consulting business but also to provide AMS to US-based external clients.

I use ServiceNow for incident management, problem management, change management, and request management.

Our primary use cases are for service management, incident, change, problem, asset, and lifecycle. The system was build and integrated to SAP as a backend ERP?CRM system. This made integrations and choices in functionality complicated. However, by replacing Symphony as a rather internal orientated system, ServiceNow gave us the benefit of tight customer integrations by means of the web-based portal, which is a user-friendly interface to use and actually helps speeding up incident handling by improved communication and information sharing.

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.

Our primary use case of this product is for incident and change management. We are customers of ServiceNow and I work as a senior software development engineer.

We run thousands of automations.

We use this solution for Service Management in banking branches.

This solution is our help desk system.

We are an integrator. We help our clients to implement ServiceNow for their companies.

We use it for ITSM and ITBM.

We are trying to bring some ServiceNow projects to our team. We are trying to upgrade our ServiceNow knowledge by learning the modules and building our own application. We are presenting the application that we develop to our management. We can then market ourselves, showing that we have some ServiceNow capabilities so that we get some ServiceNow projects. We have used almost all the features of ServiceNow within this application. Almost all the reports, data evaluation, dashboards, widgets, all the workflow-related stuff, integrations, etc. We have used each ServiceNow topic in this application.

I'm a consultant, so I primarily work on projects implementing Service Now inside of different organizations.

We are consultants. We use ServiceNow to develop ideas and solutions for our customers.

We use it for ticketing.

As a developer, I work on ServiceNow for HR solutions and a few other Service Portal functions.

We use it for ITIL/ITOM catalog of services. ServiceNow is the CMDB for our organization, and we use the Discovery, Incident Management, Change and Project Management tools within ServiceNow to keep a centralized view of our enterprise. We have recently begun implementing the Governance and Risk (GRC) features as well.

As a developer, I have mostly work on agent management and service catalog items, to create business tools. I write scripts to satisfy customer requirements.

It's used for a helpdesk.

We use it as a service desk solution, for ticketing.

We use ServiceNow mostly for our IT ticketing business. Recently we set up the Request portion of ServiceNow and we're using it as well.

* Work intake * Project management * Project for a 30 person marketing and communications team at a Big 4 professional services firm.

We build out video knowledge bases, how-to knowledge bases for self-service support and agent use. We integrate into a number of different ticketing systems, service management platforms, helpdesk platforms, and call center systems. We are a ServiceNow partner and we have a ServiceNow instance. We use it for ticketing support, ticketing systems. It has worked really well for what we do.

The primary use case is IT service management. It encompasses quite a few things, such as incident records, change records, etc.

We use it for incidents, incident management, sales management, and problem management. We are very happy with the product. We are about to upgrade to IT Service Management edition on September.