Configure Zendesk CSAT surveys — and their limitations
Prerequisites
- Zendesk account on Professional plan or above (CSAT is not available on Team plan)
- Admin access to Zendesk Admin Center
Overview
Zendesk can send CSAT surveys automatically when tickets are solved. However, it cannot trigger automations or notifications when a customer responds to the survey. There is no "satisfaction rating changed" condition in Zendesk triggers or automations.
This approach covers configuring the CSAT survey itself — enabling it, customizing timing, and restricting which tickets receive surveys. For acting on responses (like sending Slack alerts when a customer rates "Bad"), use the n8n or Agent Skill approaches.
Step 1: Enable CSAT surveys
Navigate to Admin Center → People → Satisfaction and toggle satisfaction surveys to Enabled.
Configure which channels receive surveys:
- Email — survey is embedded in the solved notification email
- Messaging — survey appears in the messaging widget after the conversation ends
Zendesk uses a two-option scale: customers rate their experience as either "Good" or "Bad". This is not a 1-5 star scale. Any "Bad" rating is a dissatisfied customer who warrants follow-up.
Step 2: Customize survey timing
By default, Zendesk sends the satisfaction survey 24 hours after a ticket is set to Solved. This is controlled by a built-in automation.
Navigate to Admin Center → Objects and rules → Business rules → Automations and find the automation named Request customer satisfaction rating.
The default conditions are:
- Hours since solved: is 24
- Ticket is not closed
- Satisfaction: is not offered
You can adjust the timing by changing the "Hours since solved" value. Shorter delays (4-8 hours) capture feedback while the interaction is fresh. Longer delays (24-48 hours) give customers time to verify a solution actually worked.
Survey responses drop off sharply after 24 hours. If your response rate is below 10%, try reducing the delay to 4-8 hours. Customers are more likely to respond while the support experience is still top of mind.
Step 3: Customize survey content
Navigate to Admin Center → People → Satisfaction to edit:
- Question text — the prompt shown to customers (default: "How would you rate the support you received?")
- Rating labels — the text on the Good/Bad buttons
- Reasons — optional follow-up reasons customers can select after rating Bad (e.g., "Issue not resolved", "Took too long", "Agent was unhelpful")
Enabling Bad rating reasons gives you structured data about why customers are unhappy, which helps identify patterns beyond individual tickets.
Step 4: Restrict which tickets get surveyed
Edit the Request customer satisfaction rating automation to add conditions that exclude certain tickets:
- Exclude specific groups: Add condition "Group is not [group name]" to skip tickets from groups where surveys don't make sense (e.g., internal IT)
- Exclude by tag: Add condition "Tags do not contain [tag]" to skip auto-closed tickets or spam
- Only survey specific forms: Add condition "Ticket form is [form name]" to limit surveys to customer-facing ticket types
There is no trigger condition like "satisfaction rating is Bad" available in Zendesk triggers or automations. The CSAT survey is a one-way feedback collection mechanism in native Zendesk. To act on responses — like sending Slack alerts, reopening tickets, or routing bad ratings — you must poll the satisfaction ratings API externally. This is the fundamental limitation that makes the n8n and code-based approaches necessary.
Step 5: Monitor CSAT in Zendesk reporting
Zendesk includes built-in CSAT reporting in Explore:
- Navigate to Explore → Dashboard → Zendesk Support → Satisfaction
- Review overall satisfaction score, response rate, and trends over time
- Filter by group, agent, or ticket form to find patterns
The Satisfaction dashboard shows aggregate metrics but does not provide real-time alerting. You'll see trends over days and weeks, but individual bad ratings won't surface until you look at the dashboard.
They poll the Zendesk satisfaction ratings API endpoint (/api/v2/satisfaction_ratings?score=bad) to detect new bad ratings and send formatted Slack messages in near-real-time. This is the only way to get proactive notification of bad CSAT scores from Zendesk.
Cost
Satisfaction surveys are included with Zendesk Suite Professional plan and above at no additional cost. They are not available on the Team plan.
Need help implementing this?
We build and optimize automation systems for mid-market businesses. Let's discuss the right approach for your team.