Why and how to conduct customer surveys in Jira Service Desk Server

[#1]

"Your most unhappy customers are your greatest source of learning," Bill Gates once said. However, to learn our lesson, we need to know what went wrong during a customer's experience with our product, support, or brand in general. We should remember that 64% of consumers pay more attention to customer experience than to price. By collecting feedback after their every interaction with our business, we gain insight about how our brand is perceived and what we should improve when it comes to support process, product or even documentation. What's more, our brand image benefits from it as well, because we show that we care for the clients and want to hear what they have to say to make their experience with our business as smooth as possible. 

Measuring customer satisfaction

After going through the support process, it's good to know how our customer assesses it. Good news, we don't have to ask too many questions to get the necessary feedback. Customer Sure analyzed tons of survey requests and noticed that the surveys with six to nine questions have the lowest abandon rate. However, we need to remember that these questions can't be difficult to answer - they should be five-scored questions, where the client doesn't have to think too much and write too much. It'll be easier not only for the customers but also for us when going through the answers.

Source: Customer Sure

Jira Service Desk and customer satisfaction survey

Seeing as Jira Service Desk is the main support channel for most of the companies which use this software, we should consider setting a customer satisfaction survey there as well. We can do it natively, by going to Satisfaction settings in Project settings and enabling Collect customer satisfaction feedback option. Then, we can define a question which will be attached to the email our client receives after we resolve their request. Also, there will be a notification on the request detail view with the editable score from the survey and additional space for a comment.

Native customer satisfaction survey in Jira Service Desk. Source: Atlassian documentation

Why native customer satisfaction survey isn't enough?

Although Jira Service Desk enables us to measure customer satisfaction with a quick one-question survey, it gives us only an inkling of how their experience was. Of course, it doesn't take too much of the client's time, however, neither does it provide us with a valuable feedback. Let's face it - one general five-scored question isn't enough, especially when it's sent via email where it can go to spam or the client will ignore it in favor of more important messages. It's great that there's a confirmation section displayed on the Customer Portal, where the user can change their rating or add a comment. But why divide it into two parts when it could be easily combined? Moreover, we want to provide a seamless experience which means that the survey should pop up directly on the Request Detail View, for example when the customer makes a transition to close their request. We can do it with apps found on Atlassian Marketplace.

5 easy steps to conduct customer surveys with Atlassian Marketplace apps

There's a number of apps on Atlassian Marketplace dedicated to collecting customer feedback on Server instances in Jira Service Desk. One of these apps is Actions for Jira Service Desk. We already described how this app helps improve the customer journey through Jira Service Desk by adding customer transitions to the Request Detail View. By enabling this feature on the Service Desk, we can now extend the clients actions and make the support process even more integrated with customer satisfaction survey. Before designing such a survey, we need to create custom fields with adequate questions. After that, we need to follow this 5 easy steps: 

1. Create Feedback transition in the workflow and add custom fields to the screen, including native field Satisfaction.
2. Go to Add-ons in Jira Administration menu and choose Workflow actions.
3. Select transition and set its name visible to the users.
4. Add description that will tell the user what you need from him, for example "We always want to improve. Could you help us out and spent a few minutes to let us know about your support experience?"
5. Choose custom fields you created earlier to display on the survey. 

Customer satisfaction survey displayed after clicking on the transition button on the Request Detail View 

Depending on our needs, we can set such a survey for various customer transitions. For example, when we want to get feedback from the client when the request is resolved, we can add an advanced transition for them to approve the solution and close the request themselves. This way, when a user clicks on the Close request button, the survey will pop up and they will be able to evaluate our support process. Also, we can enable the clients to provide feedback when they want to reopen the request and gain some more information about what was wrong with the previous solution. Moreover, we're able to display the custom fields in the Issue Navigator, export them to .csv file, prepare reports, edit them in Excel when for example we add our rating, etc. 

Once we give our customers the possibility to fill in the survey immediately after they close the request, we can gather feedback in real time. Surely, it'll be easier for the users to assess the support they got directly after it's finished. However, it gives us a lot more because we not only gain information if we deliver wow customer experience but also provide our support agents with instant feedback about their work. 

If you’d like to learn more about Actions for Jira Service Desk, read more about the app on Community:

• Automating Jira Service Desk
• How to enable self-service in Jira Service Desk, pt. 1
• 3 simple actions to extend the Jira Service Desk workflow

[Jiri Kanicky]

The problem is that customer/user never closes a ticket in Support environment. It is always the Support engineer. Hence the customer is not logged and will not see any pop up.