ServiceNow Features

The best thing about Service Now is the way we can handle all data and reports directly on the tool. It is really well designed in getting approvals and assigning tickets. We can also set the ticket assignment groups based on certain rules or configuration items, that really saves us a lot of time. It is user - friendly too. Very easy to navigate and also has some built in buttons that are really useful.

Not a major flaw, but if it can create aging tickets report in the form of a pivot table, then there is nothing to beat this tool. We really don't need to rely on excel if we can integrate some into the reporting feature on service now.

How easy it is to split tasks among other team members when your department may not be the core department.

This is a very difficult piece of software to use, to be fair. Compared to competitors, there seems to be a lot that can be done in this but there's a very real requirement in training involved. When we were set up with this product, we hardly received that. It made the implementation rocky, at best.

A brilliant ITSM tool and available as SaaS. The licensing mechanism is based on the fulfiller and approvers . The cost per licenses is a bit high for a fulfiller and hope service now can bring it down a bit. The best modules are :- Incident management , Change Management , Problem Management and CMDB.

The upgrades , every 6 months are something that always keeps us on our toes. secondly it Whatsapp and telegram can be integrated with service Now...

Loved Service Now! This made managing our help desk easy and our tech were able to work efficiently and effectively. The interface is VERY easy to read and user friendly. The application has so many different functionalities like: Knowledge base, Equipment tracking, RMA, chat, etc. I even enjoyed the Mobile App!

I wish there were different/more theme colors you could customize/choose from. Also the mobile app was complicated setting up.

A single excel sheet upload to add assets into the cmdb table was responsive and fast.

The routine upgrades are a bit of inconvenience. Ex: Migration from Rome to SanDiego to Tokyo and so on which happens once every six months.

ServiceNow allows me to easily log a ticket for any IT matters. The system makes it easy for me to lodge tickets, and "sit back and relax" while an IT personnel is quickly assigned to my task. It's much easier to work through ServiceNow, than to run up and down to my local office's IT department (which can be frustrating if they are already busy or in meetings, and you just have to wait for assistance, wasting time away from your work duties).

There are no specific negative issues that I can note about ServiceNow.

We are using service now for change management task. We can easily integrate with other tool and system . It has nice GUI and power automation tool. we can easily automate business workflow based on requirement. It provides great collaboration that allow team member to share information and work together. It help to maintain SLA.

I haven't found any issue yet. It is working as expected.

Proper managing of incidents to respective teams with 3 tier architecture starting from Help Desk Efficient management of system changes with agile methodology through proper state transition until deployment Categorization of CIs based on CI class and their relationship like Application, Database Instance, Servers

System performance can be far better on node restarting OOB baseline does not support some level of access control for change which it should have Changes created by “Copy Change” can not be tracked separately Can have more option of customizing service portal in configuration based way rather than angular Reporting on Standard Template field values should be more user friendly

easy to use and no training required for end users

should be easy to find and search for older tickets when closed

This tool is very flexible and allows even Business Users to configure processes and worfkflows.

The license is rather difficult to understand and must be re-considered over time.

ServiceNow is such a user friendly product. Their out of the box modules require very little customization to get you up and running using a wide suite of available modules, there's not a lot ServiceNow can't do.

Over-customization can make upgrading time consuming but there are plenty of guides to assist you with this process.

I have been avid ITIL practitioner and have been using various products in various companies of my job experience. ServiceNow supports ITIL processes completely and most efficiently where there are minor drawbacks. The level of compromise required to enable processes efficiently is less as compared to Remedy and HPSM. Service Now has harnessed the power of virtual assistants which is yet being explored by other companies. The ease of set-up and manageability makes configuration of ServiceNow a cake-walk.

If you are new to service management processes, the plethora of services will leave you confused. Configure one process and explore them in and out before moving into another process. Capacity Management is still a missing factor in ServiceNow though demand management can be somehow captured through projects. integration with risk management could have been made simpler to show the mapping of technical risks to business risks.

This software have extensive features which allow us users to work more efficiently. Managing request and concerns of our employees has been easier because they can create raise it through chat or ticket/case in this software anytime. Communication by users and administrators have been easy because they can follow-up through the software or even via email. Dashboard also can be customized depending on the user's needs. It also has a Knowledge Base Management attached to it which allow administrators to clarify or countercheck their responses/resolutions to the tickets/cases.

New users need to be oriented on how to navigate through this tool because it is quite confusing and intimidating to users at first.

The product is fairly easy to use if you are tracking and resolving service tickets or change requests. I like being able to granularly customize my dashboard.

This is a little more complicated for things like configuration management and opening a support request (from a support provider perspective). There are just a lot of steps and a lot of information to fill out. I would recommend having a couple of ServiceNow experts who can help standardize workflows and provide training for these more complicated tasks. Also, the dashboard can get too cluttered if you let it.

I like service now because it's very minimal and direct, and time wasn't wasted on designing a pretty interface. we use it for ticket management, both for sending out tickets to other teams, and then also tracking our workflow. I find it incredibly helpful to be able to track all stages of my work, and don't think I could do my job without it.

It's a little clunky. It's not as intuitive as other options. But I feel as though the functionality, if you have a team dedicated to setting it up for your needs, is incredibly useful and will greatly help in the long run.

Its easy to use, highly customizable on the end user end, and stable. I like that I can make my dashboard look how I want it, and use the format that makes the most sense to me. The admin on the back end has set up some great workflows that allow a single request to be used to do multiple things. Imagine a single ticket to onboard a user, that requests their cubicle from Facilities, thear computer from IT, and their phone from Telecom!

Configuration items. The way our implementation is configured, you need a valid CI to close the ticket. If an item is not in your CMDB, you have to get an admin to add the CI so you can close a ticket. KEEP IN MIND, this is just our implementation and config, and they are working on a solution to allow end users to apply a new CI, this is just OUR temporary growing pain.

Ease of use, User friendly and good User Interface.

Having autorouting feature will greatly help manual assignment

I use ServiceNow for working on the tickets assigned to me. It is very easy to handle for maintaining our current status on the ticket and update the stakeholders/users to keep them on track on the issue or request. It also gives us the option to link any change or problem associated to it. We have the flexibilty of creating incident task and see all related incident created by same user.

As of now I haven't felt any limitations with ServiceNow. Will update if any in future.

Self-sustained, full environment solution, almost without the need for complementation with other gears.

Different user experience takes a while to learn how to navigate it.

all the Modules that we used are ease to use. Documentation is well maintained. Easy to implement. easy to track the changes for Admin Team. Reporting Module is Great for BIz team.

Cost and Product Support. Product road Map dates are not clear.

I have been using ServiceNOW (SNOW going forward) for over 3 years at Nielsen now. The platform holds together a ticketing platform, a custom-built application, self-help, service desk contact information, and knowledge base articles. Our organization also has some integrations with our HR, IT and Finance systems and require a little more maintenance as we are currently committed to another well-established platform. My tickets are always visible, my approvals, etc widgets are very useful too. The portal is light, so it is fast and it also connects seamlessly with Okta.

Employees tend to get confused if the widgets are not correctly set up under the relevant sections of SNOW. The roll out time is quick, but the set up is the larger task. Custom applications running on SNOW can be a little buggy at times. The platform can turn into a administration nightmare if it is not maintained well.

ITIL based Service Portal (Self Service Portal for quick searches spanning instance or specific areas) Knowledge Base (despite that not being checked in the available features) Full Service Management solution for the ENTIRE organization Strong Workflow engine Visible Table structures for clean data flows Extremely customizable (Forms, Fields, Tables, Applications, Portal, Workflow, Knowledge Base, etc...) Best in the business system architecture (fully redundant instances) HI Administration portal and ServiceNow support are top notch Service Now community is extremely active Docs site (formerly wiki) well updated and complete. Great organization and User groups You get a cake upon launch! Extensive Integration capabilities

Cost Some out-of-box examples really don't match up to any organizations needs and leave you wanting more Email rules are more complex than they need to be (some of this can be mitigated by free add-ons like Postmaster) Configuration can sometimes be limited and requires some Javascript to get past basics Mid Servers for integrations can be more work to maintain than desired

Customization options and integration with with other tools (Nagios) as well as separate instances of Snow. As an example: one of our customers is running their own instance of Service Now. Their users interact with their own instance of Snow: log incidents, create service requests, receive and respond to mail communication. Snow objects from customer instance are then bridged (synced) into our instance of Snow, where they are actioned by fulfillers. User communication, ticket status etc. are then bridged (synced) back into customer instance of snow and reach final users.

There is a learning curve for agents coming from other ticketing tools as well as for new joiners - which is expected. A lot of user guide/process information is openly available, however not all the options described (especially reporting) are available in the version currently deployed by the company, which leads to some areas of tribal knowledge.

Easy to log incidents, update status and communicate with the customer about their tickets. Great for storing service documentation -- all of our services are documented in ServiceNow so that as tickets come into our queue, we have a repository of knowledge base articles to refer to in order to resolve the issue. The visual task board facilitates daily team standups to discuss status and priorities.

The only thing I could think of is it would be great if the visual task board had more Trello-like features, especially their power ups (custom fields, burndown chart, etc).