We've been running Zendesk for about two years now, and our internal dashboard proudly shows a consistent 92% CSAT. Management loves it. I hate it.
The problem isn't the average; it's the distribution. When I segment the ratings by ticket category, one group—let's call them "Legacy Plan Power Users"—consistently scores us at 30-40%. Their volume is only about 5% of total tickets, but their ratings are so catastrophically low they single-handedly drag the overall average down from what would be a 97% for everyone else. The 92% is a completely misleading vanity metric.
I suspect the issue is a mix of product limitations they're hitting and agent inexperience with those specific, complex workflows. But the CSAT survey just asks "How did we do?" after the ticket closes, conflating our support performance with their frustration at the product itself.
Has anyone else deconstructed their Zendesk satisfaction data to the point of despair? I'm looking for strategies to either:
* Statistically present the data in a way that isolates this segment's influence for internal reporting.
* Configure Zendesk routing or surveys to tag these tickets so we can analyze them separately *and* potentially exclude them from the main CSAT calculation if they're truly measuring product, not support.
* Better yet, any way to trigger a different survey or process for known problematic segments?
Most advice I find is about "improving the score," but I want to understand and report it correctly first. I don't trust a metric that can be skewed so heavily by a small, perpetually dissatisfied cohort.
Data skeptic, not a data cynic.
You've perfectly described why aggregated CSAT can be a dangerous comfort blanket. That 92% is hiding a critical, systemic issue with a key user segment.
On your first point about statistical presentation, we had to do something similar. We built a separate dashboard view in our BI tool that excluded a specific tagged segment, but we always showed it side-by-side with the overall number. The crucial part was labeling them clearly: "Overall CSAT" and "CSAT Excluding Legacy Workflow Tickets." Management could see both the pretty number and the ugly truth, which made the case for investing in a fix.
For tagging, can you use Zendesk's conditional logic in the satisfaction survey? We set ours to add a specific tag if the ticket was tagged with certain product-area keywords *and* the user was on a particular plan. This automatically grouped them for reporting without relying on agents to remember. The real work, of course, starts after you've isolated them. Have you considered setting up a dedicated, specialized queue for these tickets?
buyer beware, but buy smart