ServiceNow Customer Service Management

Pros

The ability to integrate with other applications and personalize the tool for use in ticketing and routing is maybe the most useful feature of ServiceNow. Our day-to-day customer support operations would not be possible without our user-friendly incident management, configuration management, and service documentation.Fast and simple incident reporting, progress tracking, and customer service interaction. ServiceNow is excellent for archiving service documentation; we've catalogued all of our services there, so that when tickets are sent, we can quickly and easily access the relevant knowledge base articles to address the problem.

Cons

A lengthy upgrade procedure might be the result of too much modification, but luckily there are many resources available to help you out. Non-IT users may find it challenging to use the site without first receiving etxra training.

Alternatives Considered

Pros

The fact that the software is widely versatile and scalable for the needs of an organisation. It can use beyond IT but in every department in our organisation as it offers automation of business tasks as well as good reporting and analysis tools. HR processes, Self Service, Approvals, Confidential reporting, schedule reporting and automating routine work, asset management and discovery.

Cons

The fact that I can not imbed linksBut also think is mostly geared to large organisations. I have not found it to be possible for a small company to take advantage of this service (price plan and configuration is beyond the capabilities for a small company to take, which is a shame).

Pros

-can search to find topics
-can customize search for tickets and service request
-can excel tickets and customize the information
-if you developers access you can create reports
-receive email confirmation and when tickets are updated
-can uploads images and video

Cons

-when creating a service request the user cannot specify the name. First a request is created [sc_request] then automatically a requested Item is created [sc_req_item] with a default title which is extremely confusing
-only the user who created Incidents can reopen Incidents
-only the user who created Incidents can then link to previously closed incidents
-if you don't have developer access you can only see the tickets you created and need other users to add you as a watcher to the ticket
-Incidents cannot be changed into Service requests, and those changes can't be tracked. (example to change a Incident into a service request a Incident must be closed and Service request opened)
-IT Portal view doesn't save views, views are only saved for that session

Pros

Covers all ITIl aspects w.r.t incident, problem and change management.
It has a very cohensive environment right from when an employee joins the organisation, getting access to applications, performing day to day jobs with tickets, requests, incidents, problems and changes.
Given the fact that it also has inbuilt reporting capabilities, this is an absolute must.
It's api and backend can be accessed by multiple softwares and applications enhancing the capability to produce visually appealing reports.
Admins/engineers/customer service execs can create their own dashboards to monitor their queues efficiently.
Inhouse capability to graphically repsent the queue make things easier while distributing work, prioritising work, planning change activities etc...

Cons

None that I know of as yet.
Whatever customisations i needed were easily available within the existing module.

Pros

Integration with other build in like Slack and other communication tools. Easy to operate and quick to learn

Cons

Running reports need to be more customisable.