Your customers can provide feedback about their experience in Zendesk Support by rating their solved tickets. When you enable CSAT (customer satisfaction) ratings in Zendesk Support, end users receive a notification 24 hours after the ticket has been set to solved that asks them to briefly evaluate their experience, as shown here:
The survey is designed to maximize the response rate by being quick and simple while also gathering the essential data: a positive or negative rating. Customers can also provide a comment if they want.
Enabling CSAT in Zendesk Support also enables it for messaging. See About CSAT ratings in messaging.
This article contains the following sections:
Related articles:
Understanding the CSAT end user experience
End users don't have to be logged in to rate their tickets. When an end user receives a CSAT survey request via email, they can rate the support interaction directly from the email message; they do not need to be logged in. Clicking a response link in the survey email saves the end user's rating and opens the ticket with a prompt to add a comment about the rating if they'd like.
The end user’s initial rating submitted via the email link is saved for up to one hour as their “intention.” This delay gives users the chance to review their ticket and write a comment about their rating.
If users:
-
Do not submit further information within one hour, their intention is recorded as their rating after the one hour period has lapsed. In this scenario, there is up to a one-hour delay between the time the user clicks the rating in the email and the time in which the rating is recorded.
-
Add further information about their rating to the ticket, their rating and comment are recorded as soon as they submit the ticket.
In this example, the end user clicked the 'Good, I'm satisfied' link so the Good button is shaded blue to indicate that it is the selected rating. A comment can be added and the rating can be changed.
If you have satisfaction reasons enabled, end users who select 'Bad, I'm unsatisfied' are presented with a drop-down menu of possible reasons for their negative response.
Selecting a response is optional, and can be skipped. For information, see Working with satisfaction reasons.
If an end user does login to your help center, they can rate their tickets there as well. In help center, the rating prompt is only available on tickets for which the Ticket Satisfaction is set to Offered by an automation or trigger (see Understanding how the CSAT survey request is sent). Ratings submitted via the help center are recorded immediately.
End users can change their rating by clicking the emailed link again or by accessing the ticket through the My activities page in help center, then resubmitting their response. Ratings can be changed until the ticket is closed. See Tracking your support requests for information on viewing your tickets in help center.
- End users can't opt out of receiving survey requests.
- Satisfaction rating is per ticket, not per customer. End users receive a survey request for each of their tickets that are solved.
- Once a ticket is set to "Closed" status, the temporary URL will no longer work. It will re-direct the user to a generic page.
When and how end users are asked for a satisfaction rating through email is customizable. You can set a time other than the default 24 hours later to send the email. You can also add the survey request in the email that customers receive when an agent marks a ticket as solved instead. You can also use business rules to be more selective about (include or exclude) which tickets generate the survey request. If you send a satisfaction survey before the ticket is solved, end users need to sign in to access it.
Understanding how the CSAT survey request is sent
When you enable customer satisfaction rating (see Enabling CSAT), a system-generated automation called Request customer satisfaction rating is added to Zendesk Support. This automation sends the survey email to the ticket requester 24 hours after the ticket is solved. You can of course customize this.
Hello {{ticket.requester.name}}, We'd love to hear what you think of our customer service. Please take a moment to answer one simple question below: {{satisfaction.rating_section}} Here's a reminder of what your ticket was about: {{ticket.comments_formatted}}
When customers receive the email, they simply click either the Good or Bad links and follow the steps described above.
For more information about this automation, see About the Request Customer Satisfaction Rating automation.
Understanding how agents receive the customer satisfaction rating feedback
The results of customer satisfaction surveys for agents are shown in the agent's dashboard and in a view called Rated tickets from the last 7 days.
Agents see, in their dashboard (when they click the Home icon () in the sidebar), the number of good and bad tickets for this week. They also see the overall satisfaction rating for the agent and all agents in Zendesk Support over the last 60 days (including the current day).
The calculation of the overall satisfaction rating uses the following simple formula:
This means that the score is an average of the total positive ratings from the past 60 days. An agent with a score of 90% means that over the past 60 days, 90% of the ratings they received were positive.
Agents, groups, and the account all have scores. The overall account score (in the example above, 95%) is the average for all agents in Zendesk Support. The two ratings provide feedback about individual performance and the average performance of all agents.
The view (Rated tickets from the last 7 days) gives you a quick overview of the rating activity, with a Satisfaction column containing both Good and Bad ratings. You can clone and modify this view or create your own. This view is inactivate by default.
- Agents cannot rate tickets.
- All agents see their ratings in their dashboard. This feature is enabled at the account level and applies to all agents in your Zendesk account. You can't exclude individual agents from receiving ratings on the tickets they are assigned to.
Additionally, ratings cannot be moderated. All ratings are shown.
84 Comments
@... Yes, that's exactly what I'm thinking. Zendesk should strongly consider this feedback.
Hi @... - Maybe it's time that Zendesk will change the terminology of Good/Bad. I'm Satisfied/unsatisfied is enough. No one gives bad support, but sometimes the answer is not enough. For example, you gave a good answer, but it is not enough, as you could add it to your wish list or forward it up to your managers.
@..., what do you think? (Don't count on it, it is almost impossible to convince Zendesk to change something for their clients...)
You can customize the good/bad text on the SAT that is sent to the clients with happy/sad icons so at least your clients won't feel bad to give 'bad' feedback.
Is it possible to set up CSAT ratings in a 5 point Likert Scale?
I'm pretty sure this is false:
The trick is to add an action to set "satisfaction" to "offered" in the same trigger/automation when you request the survey. Then, they're allowed to respond to the survey without signing in.
Generally, CSAT surveys are sent via Automation, a number of hours after the ticket's status has been set to Solved. The conditions for when the surveys are sent are configurable by you, but by default it's set to roughly 24 hours after the ticket has been solved. From that point until the ticket's status is set to Closed, the requester can respond to the survey, or if allowed by your account configuration, log in to your help center, and set the CSAT rating in their ticket directly (in the My Activities section of the help center). By default, Solved tickets are set to Closed status 4 days after the ticket was solved, but that is also configurable -- see Why do solved tickets change to a closed status?
Hi @... and @...,
After reporting it to ZD, I got an answer from @...:
The rating is only applied after around 15-45 minutes after the link has been clicked. This is by design and is intended to allow users time to enter a comment and save the page if they want to. The reasoning behind this is because if the rating were applied immediately, when the user submitted first clicked the link, and then proceeded to enter a comment and click "update", then there would actually be 2 rating events which could cause issues with things like reporting.
I can confirm that after waiting about an hour, the ticket was updated with the 1st click from the email.
Hi @... and @... - I think that the reason why your client does not send CSAT - is because of a bug in Zendesk CSAT. Or actually, they do send CSAT, but Zendesk does not save it to the ticket.
After spending a few hours on that, and trying several different trigger combinations that actually saying the same, I made a test to discovers a bug on ZD side: The client receives the CSAT mail with the two links. When he clicks on good/bad a page is opened that says that his rating was saved with a button Update, which gives the impression that he already selected, and now he can update his selection. But in-fact, only after he click Update, his selection is saved (and not by clicking on the email link!)
This is very confusing as the button say Update and not OK (and then changed to Update):
This trigger proves it:
This trigger was triggered 39 times. Then, a CSAT was sent to the client:
When he clicks on the Good link, he gets the page bellow, but the trigger was not fired (still 39 times) and the ticket was not changed with the new rating:
on ZD side, the ticket has no rating:
Only after the user click Update (without changing his rating) – the trigger is fired (changed to 40 times), and the ticket is updated with the rating:
If the user clicks Update again without changing anything, the trigger is not fired again.
This proves that the client thinks that the rating was saved for the 1st time, but actually, it was not saved.
Dave, what do you think? This looks like a critical bug.
Hi,
Often times our users submit multiple tickets and we just close the duplicates. I don't want to send CSAT requests/conversations to the closed duplicates - I only want them to get one CSAT request. Is there a way to change the Send CSAT survey in relation to ONLY tickets one of my agents has responded to? Would it be to set it to only send it to "Assignee: one of our agents," and never a requester?
Thanks!
Hannah
Yaniv Dayan -- Thank you for your comments above surfacing and then explaining the delay between when End user rates the ticket and when the rating appears on the ticket from the Agent UI.
While I understand the rationale for why it works like this (as described above) I don't think this should have to be the way it works. Why would two rating events on the same ticket cause a problem with reporting? It is in fact two separate events: The user submits their rating and then the user submits a comment.
Seems like it should have always been recorded as two separate events but since it wasn't now it can't be changed.
I don't think it's a good practice to have the user submit something on a ticket and not have that reflected as an event immediately. There are use cases for triggering an event immediately upon the survey being responded to (which are admittedly edge cases) but still this I think is a dangerous idea as Zendesk system and admin should know a change was submitted as soon as it was submitted to inform triggers that might need to be executed in real time and not 15-45 minutes after the user completes some action. Just my two cents!
Hi RichL
With reference to the first question that Anuj Singh asked you on CSAT reminders, how do we configure the CSAT settings such at only those who have not rated gets the reminder survey? This is to avoid duplicates as customers who have rated us the first time may rate us again the second time when they get the reminder.
Regards,
Zil
@... Hmm this might be complicated, but what if you had some trigger sequence like:
Some of my customers are reporting that when trying to leave a satisfaction rating from a mobile phone email reply they are receiving error messages. Are you aware of any limitations using the standard placeholders, {{satisfaction.rating_section}}, with mobile platforms?
Rebecca Che - yes that is possible and easy to do with a Trigger.
We have implemented that and it is quite useful.
Although the Bad CSAT's we have received are normally due to the Feedback email being quite sensitive (so if a user is checking it on the mobile phone) they may accidently select Bad and not even realize it.
Go to your Trigger View in Admin Console.
Define Meets Any of these Conditions
Satisfaction "is" Bad
Satisfaction "is" Bad with Comments.
Then just add the action to e-mail the Team Lead and there you can define the email subject and body.
Hi Wheel Pros, LLC,
Thanks for looking into that, I have tried this option and it seems to be the best option available.
Lee
This may be of some help: Are CSAT surveys multi-lingual?
Hey Anuj Singh!
There are many ways to set this up and ultimately how you do it would depend on how/when you want to send the initial CSAT survey and reminder.
An example of how you could do this:
1. Create an automation to send the initial CSAT survey 2 days after ticket is solved
2. Create a second automation to send the CSAT survey reminder 4 days after ticket is solved if a CSAT rating has not been provided by end-user for that ticket
Example automations:
Request CSAT from Customer automation
Conditions -- All
Actions --
CSAT Reminder automation
Conditions -- All
Actions --
The above setup should do the trick. You can of course add additional conditions to not send CSAT survey for certain tickets based on whatever makes sense for your situation.
The initial and reminder CSAT automations would both only run once with the above configuration. Once the Satisfaction is offered in the first automation it would never get set back to unoffered so that would only be able to activate once. And the second automation adds a tag which would prevent the CSAT reminder email from being sent a second time if the ticket were to be re-opened and then solved a second time after the CSAT reminder email was sent.
You could configure these automations differently if you want to re-send the initial CSAT email and/or reminder email. To re-send the reminder email upon re-solve you would just need to eliminate the tag condition and action from the reminder automation above. To re-send the initial CSAT survey upon re-solve you would need to also add a trigger which sets the Ticket: Satisfaction back to blank/null when Ticket: Status Changed from Solved and Ticket: Status Is Open and Current User Is (end-user)
That's a pretty detailed explanation but I may have missed something so I would suggest, like with any similar change, test and monitor the functionality once implemented. Other triggers or automations your Zendesk may have could introduce wrinkles that I can't account for or I may have just missed somethings as I think through this here. Good luck!
Lee Ryall
No problem at all. I did a lot of digging on NPS and stumbled upon the missing functionality that you're looking for as well. Glad I could help. Not sponsored by SimpleSAT or anything, just sharing my experiences when shopping around from something that would integrate well with ZD with an easy to swallow price tag.
Hi Everyone,
Is it possible to create the Rating via the api's using the agent's basic authentication for user tickets?
I'm getting "Forbidden" error when calling the below api
Exception:
Thanks
I have tried the api via postman only and also on curl. will there be any issue with the enduser authentication? do we have any setting to enable for api access for the enduser in admin panel? Let me know if you req. the curl req. that i was trying. will share it via private mail. please feel free to drop a mail to "gowtham.s1@betterplace.co.in"
Thanks
How do I publish the csat general score across the company or embed it on a web page? I believe I saw an option that requires at least 100 responses in order to do it but I cannot find it anymore.
Thanks
Hello ZD
Can you see if there is a way to offer a 'value' to customer to click of what made them happy/select Good for CSAT?
Trying to see if we can measure that as well on a ticket. Hopeful to do something quick and simple like what we do with bad satisfaction ticket reasons.
Hi Natalia Numa welcome to our Community! :)
You can definitely send your survey in Spanish by setting up translations in your account and use the dynamic content placeholder in your CSAT automation.
You may find more info and instructions to set it up here:
Creating dynamic content items
Multi lingual CSAT survey
I hope this helps! :)
Appreciate it Wheel Pros, LLC
If a ticket is merged with another open ticket, does that merged ticket send a satisfaction email? If so, is there a way to prevent that from happening?
I so nor see this option under my reports. Has it moved?
Hi,
Is there a way to see the "comments" beyond seven days? We would like to chart the comments to help our CS dept. Currently, we see "with comment" for seven days and cannot go back a few months or month by month. Is there a way to set this up? We have the Suite Growth Plan, thanks!
Hi Rachel,
In regards to your concern, there are some workarounds that you can perform to try re-evaluating the CSAT score of the customer.
Here are some article links that you can refer to: https://support.zendesk.com/hc/en-us/community/posts/203457806.
Also, there's a community article that you can check: https://support.zendesk.com/hc/en-us/community/posts/205873008-Reset-satisfaction-rating-to-allow-a-resend-after-improvement-of-situation
I hope this information helps.
John Espina | Customer Advocate
How do I fix survey links that aren't working?
Clicking on the survey links in the email renders a denial error HTTP 403 access denied.
The email links appear in the body of the email from this code in the automation: {{satisfaction.rating_section}}
Code appears correct, but the links aren't working.
Hi Guys,
Since we normally not working in front of the end-user but with one level above, 90% of the support questions come from a relatively small group of users. We don't want to overload this group with CSAT, and also do not wish to send CSAT to casual clients.
What we are looking for is a trigger/automation that sends CSAT every 10 solved tickets, but starts counting after the 2nd ticket (so eventually a client will get CSAT on his 2nd ticket, 12th ticket, 22nd, and so on)
Any idea how we can implement it?
Bryan
Zendesk do not provide a 5 point CSAT rating. You would need a third part app for that. Sorry.
Please sign in to leave a comment.