You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
This is the second part of the article. In the first part, we went through the main capabilities Atlassian software gives us to enable self-service and a couple of possible extensions to them. In this part, let's see how we can improve this further after a customer submits a request in Jira Service Desk.
We can also add a self-service touch after a customer raises a request. A couple of workflow transitions that will make the agents' work easier and enable clients to make certain actions within their requests will do just fine. This isn't available in Jira Service Desk natively, but there's an app, Actions for Jira Service Desk, which adds this function. It can be used in a bunch of different ways depending on how we configure it.
After resolving a ticket, it's nice to get detailed feedback about how it all went. The one 5-star question survey available natively in Jira Service Desk isn't enough to gain in-depth insight into how the customer perceives the whole experience or if there were any problems along the way. It helps measure customer satisfaction, but it misses out on important information that you could use afterwards to improve the support process. There's a way out of this by creating custom fields with questions you want to ask and which you can use later on when creating a survey.
Enabling users to interact with their requests in more ways than just commenting makes it easier for them to change important details or even escalate it as they see fit. Also, it shortens the process in a way, because agents don't need to get involved and make all the changes or transitions for the customers. For example, you can decide which fields the users can edit. Whenever a client wants to change something in their request, they can edit it and make changes only on the specific fields. Other than that, a customer can transition the request when there's a need for their input. For instance, when the requester isn't happy with the solution, they can reopen the request, or the other way around - when they're satisfied with the answer to their question, they can close it. Each action they can take is visible on the sidebar of the Request Detail View in the Actions section.
To do so, you need to:
Admins and agents can make good use of Actions for Jira Service Desk as well, because it extends the automation rules available in the tool. A common use of this is assigning agents to the requests based on the reporter's language, which comes in handy when you have international customers. For example, when a customer raises requests in Spanish, it will go to the person who knows the language and can easily answer all the questions and pass the problem on to the development team. Other than that, there are additional conditions such as Reporter Email Contains and the option to add Organizations, request participants, labels, as well as set priorities to the issues upon these conditions.
To set an automation rule that will assign an agent and set a priority to a specific request based on language, you should:
Nowadays, providing customers with self-service capabilities is clearly a must-have. Each of the functionalities enabling both external and internal users to do more on their own ensures a seamless flow of the process, possibility for an agent to focus on the task at hand, and make the job easier for everyone by delegating requests to the people who will know how to handle them. After all, self-service aims to engage customers on all stages of the customer support process, and not only at the beginning and the end of it. We only should be careful in planning these investments, as according to Gartner Research VP David Coyle, they may induce additional costs for knowledge management and staff training, which in turn may lead to increase overall support costs. Self-service isn't meant to cut on the budget, but it is to create an experience our customers would love us for.
If you’d like to learn more about improving Jira Service Desk, read other articles on the subject available on the Community: