Zendesk CSAT by Assignee Report
Top-line CSAT is useful for spotting whether customers are broadly happy with support. It is not very good at telling you where dissatisfaction actually starts.
That matters because one owner queue can create most of the low ratings while the team average still looks stable. If you only review the blended score, you see the lagging symptom but miss the local pattern that is actually creating the friction.
This guide shows how to build a Zendesk CSAT by assignee report, how to interpret owner-level satisfaction gaps, and what to change when one queue quietly drags the experience down. Keep it connected to the support metrics dashboard, Zendesk CSAT Report, and Zendesk CSAT by Group Report.
What this report should answer
A useful CSAT-by-assignee report should answer:
- Which owners receive consistently lower satisfaction scores than peers?
- Is the difference explained by ticket mix, role, or escalation ownership?
- Does low CSAT cluster around one assignee, or is it broader?
- Is the pattern stable enough to act on, or just sample-size noise?
For the broader quality context, pair this report with Ticket Reopen Rate and Zendesk Resolution Time Report.
Why assignee-level CSAT reporting matters
Customer dissatisfaction is often local before it is global.
One owner queue can produce more low ratings because it carries:
- harder issues
- more escalations
- slower follow-up loops
- weak expectation-setting
- tickets that reopen after premature solves
Without an assignee view, those patterns get averaged away. Support leadership sees a stable score. Customers in one part of the queue feel something very different.
How to build the report in Zendesk
Use the Support: Tickets dataset in Zendesk Explore and be careful with denominator size.
1. Start with rated-ticket volume
Do not read CSAT by assignee without the number of ratings beside it. A very small sample can make any owner look unusually good or bad.
2. Break CSAT out by assignee
Add assignee as the main row dimension and show:
- CSAT %
- total ratings
- low-rating count, if available
That gives you both satisfaction level and sample context.
3. Add one explanatory cut
After you identify an outlier, add one secondary cut such as:
- assignee plus channel
- assignee plus priority
- assignee plus tag
- assignee plus group
This helps you see whether the issue belongs to the owner or the work they own.
4. Trend it monthly or on a rolling window
CSAT is often too noisy day to day. A rolling 30-day or monthly view is usually more useful for owner-level interpretation.
5. Compare with quality and speed metrics
Low CSAT is much easier to interpret when you review it beside reopen rate, resolution time, and first response time.
The most useful report layouts
CSAT by assignee with rating count
This is the core view. It shows whether one owner consistently receives worse customer feedback than the rest.
Low-rating count by assignee
This is often the best follow-up view because it shows where customer friction is accumulating in absolute terms.
CSAT by assignee and priority
Use this when urgent work seems to generate more negative feedback in one queue. Pair it with Zendesk Resolution Time by Priority Report.
CSAT by assignee and tag
This helps when one issue type or workflow seems to drive most dissatisfaction.
How to interpret the patterns
One assignee has lower CSAT with healthy sample size
That is worth investigating. The cause may be communication habits, ticket mix, or a queue that creates harder customer conversations.
One assignee has low CSAT but very few ratings
Be careful. That may be noise rather than a stable pattern.
One assignee has low CSAT and high reopen rate
That usually points to incomplete resolution, weak expectation-setting, or tickets being solved too early.
Team CSAT looks fine, but one owner repeatedly gets poor scores
This is the local-quality pattern the blended team score hides. It is usually where improvement work should begin.
Common mistakes
- Ignoring sample size.
- Treating CSAT as a pure individual performance score.
- Comparing owners with very different ticket mixes.
- Looking at CSAT without reopens or resolution time.
- Reacting to one bad period instead of a stable pattern.
What to do when one owner queue gets worse satisfaction
If one assignee consistently shows lower CSAT:
- Check rating count first so you know the pattern is real.
- Compare the owner’s reopen rate, resolution time, and ticket mix.
- Review saved replies, expectation-setting, and escalation handoffs.
- Look for one issue type or one channel driving most of the bad feedback.
- Coach the workflow, not just the metric.
The goal is not to use CSAT as a leaderboard. It is to find where customers are having a worse experience than the team average suggests.
Where this report fits in your dashboard
This report works best beside:
Together, those views show whether dissatisfaction comes from slow handling, weak resolution quality, or one queue that creates more difficult customer conversations.
FAQ
Is CSAT by assignee reliable enough to act on?
Yes, if the owner has enough ratings and you compare it with related metrics like reopens and resolution time.
Should I use rolling windows for this report?
Usually yes. A rolling 30-day or monthly view reduces noise and makes the pattern easier to trust.
What should I check first when one owner has low CSAT?
Start with rating count, then review reopen rate, resolution time, and ticket mix before drawing conclusions.