What is our primary use case?
I use ServiceNow Customer Service Management for managing ticket flows, raising change requests, and managing support activities. Whenever a customer faces any issues, they raise a ticket on ServiceNow Customer Service Management; once they raise the ticket, it comes to the service desk queue, and we route it to the respective teams so that the correct team receives the ticket and assists the user with their issue.
What is most valuable?
ServiceNow Customer Service Management is a great tool that is very interactive. All details are managed effectively, and even if a large number of customers raise multiple tickets in a very short time, everything is handled within the system. We can generate reports and track everything, and the SLA calculation is very reliable using this tool.
ServiceNow Customer Service Management has impacted our organization positively; we have formed a very good process with this tool that has helped increase the productivity of the team.
When it comes to ticket resolution, the time taken decreases significantly. Considering the high volume of tickets, there is often the same pattern with the same kind of issue. Whenever the ticket team receives a ticket, by checking the pattern, they can find if this kind of issue has occurred in the past, and with the resolution notes stored in those tickets, they can provide faster resolution while making everyone aware of the issue and what steps need to be taken.
What needs improvement?
ServiceNow Customer Service Management is offering very good things, but I felt improvements to our process would allow us to depend on this tool in many other ways.
Regarding the interface, currently the user who creates the ticket has a very limited interface with only the options for creating a ticket and providing details, while the support team has a much larger interface with many options, including SLA details and report generation. While this classification is great, I felt that some modifications could be brought to the interface.
I felt that further modifications can be made so that it could be a perfect tool.
For how long have I used the solution?
I have been working in my current field for seven years, and for the last four years, I have been using ServiceNow Customer Service Management.
What do I think about the stability of the solution?
ServiceNow Customer Service Management is very stable.
What do I think about the scalability of the solution?
ServiceNow Customer Service Management is very scalable; according to our process, we can use it in any way we want.
How are customer service and support?
Customer support provides a lot of help and responds immediately, offering very good service.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Previously, we were using ITSM; we switched from that to ServiceNow Customer Service Management because there were many flaws with ITSM in both the tool and the process. Once we switched, I found that ServiceNow Customer Service Management is much better.
What was our ROI?
When it comes to time and money, I felt a lot of savings have occurred because this process has helped significantly. In our organization, downtime and criticality have been addressed in a very short time, and the revenue and outcomes from this have increased. Time and money savings have helped tremendously in these specific areas.
Which other solutions did I evaluate?
When we started evaluating other options, we immediately received feedback about ServiceNow Customer Service Management. Everyone was telling us about the positives, so there was no other option we considered, as we did not experience much difficulty or put much effort into searching for alternatives.
What other advice do I have?
Based on each ticket, we assign a criticality level; for higher criticality tickets, we have allotted a certain amount of time for the support team to work on it, meaning they must find a resolution and clear the issue within that timeframe. This is how we have prepared a process based on criticality.
Apart from that, I think the major aspect is the SLA process; if the SLA is not met, managers are immediately alerted that a ticket has come to the team's queue and they have failed to meet this SLA, and they take necessary action so that such scenarios will not happen in the future.
If you are looking to establish a good process in your environment, ServiceNow Customer Service Management provides a very good interface tool for this purpose. Ticketing and change management can be managed using this tool, and it is very helpful. I would rate this solution a 9 out of 10.
Which deployment model are you using for this solution?
On-premises