Zendesk CSAT by Tag Report

Overall CSAT can look healthy while one support topic quietly frustrates customers every week.

That happens because satisfaction is usually reviewed as one blended quality number. It tells you whether customers are broadly happy, but it does not tell you which kinds of work produce the worst experience. When satisfaction drops only inside a few issue categories, the top-line score often stays steady long enough for the problem to normalize.

This guide shows how to build a Zendesk CSAT by tag report, how to interpret the pattern, and how to combine tag-level satisfaction with the operational metrics that explain why customers are frustrated.

What this report should answer

A useful CSAT-by-tag report should answer:

Which issue types consistently get lower satisfaction?
Are low-CSAT tags also slower or more likely to reopen?
Is the satisfaction problem concentrated in one workflow, one product area, or one customer segment?
Are we reacting to a true quality issue or a sample-size illusion?

For the metric definition, see CSAT. For the tag structure underneath the chart, use issue taxonomy and tag co-occurrence.

Why tag-level CSAT matters

A single CSAT number can tell you the queue is fine when customers experiencing one specific problem would strongly disagree.

That matters because:

certain issue types are emotionally sharper than others
some topics require more back-and-forth before customers feel resolved
one broken product workflow can damage satisfaction across many otherwise healthy tickets
leadership often acts too late when it cannot see which topic is causing the score drift

CSAT by tag turns customer feedback into a root-cause view. It answers not just “Are customers happy?” but “What kind of work creates dissatisfaction?”

How to build the report in Zendesk

Use the Support: Tickets dataset in Zendesk Explore and start with the satisfaction metric you already use in reporting.

1. Confirm the CSAT definition

Make the reporting rule explicit:

percent positive ratings, average score, or another chosen method
which tickets were offered a survey
minimum sample size before a tag is considered reviewable

If survey coverage is thin, tag-level CSAT becomes noisy very quickly. For the base setup, start with How to report CSAT in Zendesk.

2. Break CSAT out by tag

Use tags that represent real issue categories or product areas, not just workflow labels. If your taxonomy is messy, start with a smaller set of tags you already trust.

3. Add rating count beside the score

Never review tag-level satisfaction without the number of ratings. A tag with two bad surveys is not the same as a tag with two hundred.

The two core columns are:

CSAT by tag
ratings count by tag

4. Trend the tags that matter most

Use weekly or monthly views to track whether the same tags repeatedly underperform. Trends matter more than a single bad period.

5. Compare satisfaction with operational metrics

The most useful pairings are:

If a tag has weak CSAT but healthy speed, the issue may be solution quality or policy friction. If CSAT, reopen rate, and resolution time all move together, the problem is likely bigger than message tone alone.

The most useful report layouts

CSAT by top tags

This is the main leaderboard. It tells you which topics consistently create the worst customer experience.

CSAT by tag over time

This shows whether a problematic topic is improving, stable, or quietly getting worse.

CSAT by tag and group

This helps you tell whether the dissatisfaction belongs to the issue type itself or to one team’s way of handling it.

CSAT by tag with reopen and resolution context

Use this when you want one clear answer to “Why do customers dislike this category?” The quality story is usually stronger when satisfaction is reviewed beside Zendesk Reopen Rate by Tag Report and Zendesk Tag-to-Resolution Time Report.

How to interpret the patterns

One tag has low CSAT but normal speed

The team may be responding quickly but not solving the issue in a way customers consider complete or fair. Look at the actual ticket transcripts and survey comments.

One tag has low CSAT and high reopen rate

That is usually a durable quality problem. Customers are unsatisfied and the issue keeps coming back after support thinks it is solved.

One tag has low CSAT and low survey count

Treat it as a watchlist item, not a conclusion. Sample size matters too much to treat tiny categories as established truth.

That often points to a shared workflow or product area problem. Review whether the taxonomy is splitting one broader issue across several labels.

Common mistakes

Ignoring sample size. Tag-level CSAT without rating count is easy to overread.
Using tags customers never see. Routing or internal workflow tags are usually less useful than issue-type tags.
Separating satisfaction from operations. CSAT alone rarely tells you why a topic feels bad.
Treating all low-CSAT tags as coaching issues. Many are process, product, or policy issues first.
Skipping survey comments. The score tells you where to look; the verbatim feedback tells you what actually frustrated the customer.

What to do when one tag stands out

If one tag consistently gets weaker satisfaction:

Review sample tickets and survey comments for the tag.
Check whether the same tag also has high reopen rate or long resolution time.
Decide whether the problem is expectation-setting, solution quality, or product friction.
Make one clear owner responsible for the fix.
Re-check the tag after the change instead of only watching overall CSAT.

The point of the report is not to create another ranking table. It is to focus improvement on the work customers actually find most frustrating.

Where this report fits in your dashboard

This report works best beside:

Together, those views show which topics frustrate customers, which topics are slow, and which topics support fails to resolve durably.

FAQ

What is a good sample size for CSAT by tag?
There is no single rule, but avoid drawing strong conclusions from very small counts. The exact threshold depends on your ticket volume and survey coverage.

Should I use positive-rate CSAT or average score?
Use the method your team already reports consistently. The important part is comparability across tags and time periods.

What if we do not collect enough CSAT?
Use reopen rate and customer reopen rate as stronger quality signals until survey coverage improves.

See which Zendesk issue tags quietly create the worst customer experience - start free