The short answer
To set up CSAT surveys in Zendesk, enable the Customer Satisfaction setting in Admin Center, configure the survey email content and follow-up question, create a trigger that sends the survey on ticket solve, test it on a sandbox ticket, and launch. Zendesk's native CSAT reporting covers score distribution and tag-level breakdowns. For deeper analysis — theme clustering, sentiment of follow-up comments, cross-channel correlation — connect Zendesk to Indellia via the Zendesk integration.
Why Zendesk's native CSAT is the right starting point
Zendesk's built-in CSAT is free, sits directly on the ticket workflow, and requires no new tool procurement. For teams measuring post-ticket satisfaction for the first time, the native feature is the right starting point — nine times out of ten.
What it does well: captures a score on every solved ticket, associates the score with the agent and ticket metadata, supports a follow-up free-text question. What it doesn't do well: analyze the free-text responses at theme level, compare satisfaction to sentiment from non-ticket channels, detect anomalies across tickets-plus-reviews.
The right pattern for most consumer brands: run Zendesk CSAT natively for the score collection, pipe the responses into Indellia for cross-channel analysis.
The literal steps
Enable CSAT in Zendesk
Sign in to Zendesk as an administrator. Open the Admin Center from the top-right product-switcher. Navigate to Channels → Messaging and email → Customer satisfaction. Toggle Customer Satisfaction on. This makes the CSAT fields available on tickets and enables the satisfaction endpoint.
If you don't see the Customer Satisfaction option, your Zendesk plan tier may not include it. CSAT is available on Suite Growth and higher, and on Support Professional and higher.
Configure the survey email
In the Customer Satisfaction settings page, edit the email content. Three fields matter: subject line, body text, and thanks-page copy. Keep the subject short ("How was your experience with [Brand] today?"). Keep the body body two or three sentences, asking the customer to click either "Good, I'm satisfied" or "Bad, I'm not satisfied." Zendesk uses a binary scale natively — if you want a five-point scale, that's a customization below.
Set the trigger
Go to Admin Center → Objects and rules → Business rules → Triggers. Create a new trigger named "Send CSAT on ticket solve." Conditions: Ticket → Status changed to Solved. Meet ALL of: Ticket is → Solved. Ticket is NOT → Spam.
Actions: Email user → Requester. In the email body, use the placeholder {{satisfaction.rating_url}} — this renders as the two rating buttons. Schedule the email for 24 hours after solve for most categories; CX teams report higher response rates than immediate-solve sends, which feel too early.
Add the follow-up question
After the customer selects Good or Bad, Zendesk displays a thanks page with a free-text question. The default is "What could we have done better?" — acceptable but generic. Better: ask specifically about the product or the experience ("What happened with your product?" or "What could we have done differently?").
The free-text responses are the analytical gold of CSAT. Score alone tells you satisfaction rate; the free-text tells you why. Most teams ignore the free-text because Zendesk's native reporting doesn't surface it at theme level.
The free-text responses are the analytical gold of CSAT. Score tells you satisfaction rate; free-text tells you why. Indellia — CSAT
Test and launch
Create a test ticket using a personal email. Solve it. Wait 24 hours. Verify the CSAT email arrives, the rating buttons work, the thanks page shows the follow-up question, and the response records back on the ticket in Zendesk.
If anything breaks, check the trigger conditions (common issue: requester has CSAT emails disabled in notifications), the email content (common issue: the placeholder wasn't pasted correctly), or the plan tier.
Analyze in Zendesk
Zendesk's Explore (or Insights for older accounts) produces out-of-the-box CSAT reports — score distribution, score by agent, score by group, score over time. Useful for operational management. Less useful for understanding why.
Export the free-text responses for deeper analysis. In Explore, the Satisfaction dataset exposes the rating and the free-text comment; export to CSV weekly.
Connect to Indellia for theme-level analysis
In the Indellia web app, navigate to Settings → Integrations → Zendesk. Provide your Zendesk subdomain and OAuth credentials. Indellia will pull tickets, CSAT scores, and CSAT free-text responses on a continuous basis.
Once connected, CSAT data flows into the same corpus as your reviews, returns, and other feedback. The Theme Agent clusters CSAT free-text responses by theme. The Anomaly Agent watches for rising themes in CSAT responses. The SKU Agent links CSAT tickets to the product the customer was asking about. Cross-channel views now compare CSAT responses to reviews for the same SKU family.
Analyze Zendesk CSAT responses at theme level. Connect Zendesk in under five minutes. CSAT free-text flows into the same corpus as your reviews and returns.
Common issues
- Low response rate. Most teams see 8–15% CSAT response rate on email surveys. Below 5% usually means subject-line fatigue (customers receiving too many brand emails) or timing issues (sending the survey too soon after solve).
- Binary vs 5-point scale debate. Zendesk native is binary. 5-point scales produce more granular data but require customization or third-party apps. For most operational purposes, binary is sufficient; the gradient matters less than the trend.
- Agent bias. Individual-agent CSAT becomes a performance metric, which creates incentives to request good ratings from customers explicitly ("if you're satisfied, please rate us Good"). This gaming is detectable in the free-text and should be monitored.
- Sampling bias. Customers who respond to surveys are not representative of customers who don't. Treat CSAT as one signal among several, not a ground truth.