Zendesk CSAT, Measured Honestly
Zendesk CSAT is one question after a ticket closes, and a number that either tells you something or flatters you, depending entirely on how you set it up.
How the Zendesk CSAT survey works
Zendesk sends a satisfaction survey once a ticket is solved. It asks whether the experience was good or bad, with an optional comment. The rating lands back on the ticket itself, so you can report by agent, group, channel, tag and time.
An automation fires the survey, so you control the timing. It's a small setting. It also affects your score more than anything your agents do.
Timing, and why it decides your score
Send too fast and you catch people who haven't tried the fix yet. Send too slowly and you catch people who have forgotten the interaction entirely and are rating their mood instead.
A few hours after solve is the usual sweet spot for straightforward tickets. Anything the customer has to verify does better the next morning.
Whatever you pick, keep it. A score that moves because you changed the delay isn't measuring your support, it's measuring your automation.
Reading the number
Most teams land between 75% and 90%. Comparing across companies is close to meaningless, because survey design moves the number more than performance does.
The comment field is what matters. Ten bad ratings with comments teach you more than a thousand good ones without one. Read them weekly, tag the themes, then take the top theme to whoever owns the underlying problem.
Segment before you conclude anything. By channel, by group, by first response time band. An aggregate CSAT hides the one queue that's quietly failing.
The pattern that drags CSAT down invisibly
A customer writes in twice about one problem. Two tickets, two agents, two answers, sometimes contradictory ones. Both get solved. Both send a survey.
One confused customer, two survey invitations, and any dissatisfaction counted twice. Worse, the interaction behind it was avoidable. That second ticket should never have reached an agent at all.
If your CSAT has an unexplained soft patch, check your duplicate rate before you coach anybody. Two answers to one question is a quality failure, and it isn't one that agent training prevents.
Frequently asked questions
When should Zendesk send the CSAT survey?
A few hours after solve for simple tickets, the next morning for anything the customer has to verify. The exact delay matters less than sticking to it.
What's a good Zendesk CSAT score?
Most teams sit between 75% and 90%. Track your own trend, because you're not comparing like with like against a number from a different survey design.
Should merged tickets send a survey?
No. Exclude tickets tagged closed_by_merge from your survey automation, or you're surveying people about a ticket that was administratively closed.
Remove the interactions that earn bad scores
Two agents answering one customer differently is a CSAT problem you can delete rather than coach.
Start free trial14-day free trial. No credit card required.