Zendesk CSAT by Ticket Form Report

Overall CSAT tells you how satisfied customers are in aggregate. CSAT by ticket form tells you which intake paths customers actually dislike most.

That matters because satisfaction rarely drops evenly across all support work. It usually clusters in a few request types, workflows, or service paths. One form can create a much worse experience than the rest of the queue while the global score still looks stable enough to ignore.

This guide shows how to build a Zendesk CSAT by ticket form report, how to interpret the patterns, and how to use it to fix the forms quietly creating the most friction.

What this report should answer

A strong CSAT-by-ticket-form report should answer:

Which ticket forms receive the weakest satisfaction scores?
Is customer friction concentrated in a few intake paths even while the overall score looks acceptable?
Are the lowest-scoring forms also showing slow first reply, slow resolution, or high reopen rate?
Is the problem caused by the work itself, the workflow around it, or the expectation customers bring into that form?

For the metric definition, see CSAT. For related quality context, keep reopen rate and requester wait time nearby.

Why ticket-form-level CSAT matters

Customers do not rate your average workflow. They rate the specific path they just experienced.

One ticket form can drag satisfaction down because:

the request type is confusing or emotionally loaded
the form routes into a slower or more complex workflow
the form creates poor expectations about what support can do
the work often requires handoffs, approvals, or repeat explanation

When you only review global CSAT, stronger forms can mask the ones that are actually causing frustration. CSAT by ticket form reveals where the pain really lives.

How to build the report in Zendesk

Use the Support: Tickets dataset in Zendesk Explore and focus on forms with enough survey volume to be meaningful.

1. Group by ticket form

Make ticket form the main row dimension. This lets you compare customer sentiment across different intake paths and workflows.

2. Add response volume

Never review CSAT without sample size. Always pair:

CSAT score
number of ratings
ticket form

That keeps you from overreacting to one low score on a tiny form.

3. Add speed and quality context

The most useful companion metrics are:

first reply time
resolution time
reopen rate
backlog or ticket age

These help you tell whether the satisfaction issue is about slowness, poor resolution quality, or the nature of the work itself.

4. Segment when needed

If one form supports multiple audiences, add cuts like:

priority
channel
assigned group
customer segment

That often reveals whether the low score belongs to one part of the workflow rather than the whole form.

5. Trend it over time

A one-month dip can be noise. Repeated weakness in the same form usually points to a real and fixable customer-experience problem.

The most useful report layouts

CSAT by ticket form

This is the core quality view. It shows which intake paths customers rate worst.

CSAT by ticket form with response count

This is the safest operating version because it keeps sample size attached to every score.

CSAT by ticket form with first reply and resolution time

This is one of the most revealing pairings because it shows whether low satisfaction is mostly explained by speed or by something deeper in the experience.

CSAT by ticket form and reopen rate

Use this when you want to see whether low satisfaction matches explicit evidence that issues are not actually getting resolved well.

How to interpret the patterns

One form has low CSAT and slow resolution time

That often means the workflow is both frustrating and slow. The customer experience problem is likely real, not random.

One form has low CSAT but healthy first reply time

That usually means the issue is deeper than quick acknowledgment. Resolution quality, handoffs, or expectation mismatch may be the bigger problem.

One form has weak CSAT and high reopen rate

This is a strong quality signal. Customers are not just unhappy; the work is coming back after it was supposedly solved.

One form drags CSAT down while the global score stays stable

This is the hidden-concentration pattern. The rest of the queue looks fine enough to hide one intake path where customers are consistently having a worse experience.

Common mistakes

Using CSAT without sample size. Tiny forms can look artificially extreme.
Treating low CSAT as only a people issue. Workflow design often causes the pain.
Ignoring speed context. Slow first reply and slow resolution still matter.
Looking only at the global score. That hides localized friction.
Assuming every low-scoring form should have the same target. Some request types are inherently harder and need different expectations.

What to do when a ticket form stands out

If one form repeatedly shows weak CSAT:

Read real ticket transcripts and survey comments from that form.
Check whether the pattern pairs with slow first reply, slow resolution, or high reopen rate.
Compare it with Zendesk First Reply Time by Ticket Form Report and Zendesk Resolution Time by Ticket Form Report.
Review whether the form sets the wrong expectation or routes work into a frustrating workflow.
Make one concrete process change and watch the form-level trend, not just the global score.

The goal is not to force every request type into the same satisfaction score. It is to find the intake paths where customer frustration is structurally higher than it should be.

Where this report fits in your dashboard

This report works best beside:

Together, those views show where customer friction clusters, whether it is tied to speed or quality, and which forms support ops should investigate first.

FAQ

What sample size is enough for CSAT by ticket form?
There is no universal threshold, but you should be cautious with very low response counts. The smaller the sample, the more important it is to review comments and adjacent metrics before acting.

What if one form is always lower because the request type is inherently difficult?
That can be true. The question is whether the score is stable and explainable or whether it is falling because the workflow is creating avoidable frustration.

How often should I review this report?
Monthly is often enough for stable teams. Weekly review is useful when survey volume is high or when one form is already showing repeated friction.

See which Zendesk intake paths create the most customer friction - start free