How to send Slack alerts for low Zendesk CSAT scores

Why alert on low CSAT scores?

A customer who submits a "Bad" satisfaction rating is telling you something went wrong — but Zendesk buries that signal in a reporting dashboard that most managers check weekly at best. That creates a 3-7 day gap where unhappy customers go unnoticed, and by the time you see the trend, the opportunity to recover the relationship has passed. Research shows that following up within 24 hours of a negative experience recovers 50-70% of at-risk customers. Wait a week and the save rate drops below 10%.

Routing low CSAT scores to Slack closes that gap. The moment a customer rates "Bad," the assigned agent or a recovery specialist sees it with full context — the ticket subject, the customer's comment explaining what went wrong, and a direct link to the ticket. Quick follow-up while the experience is fresh frequently turns a detractor into a loyal advocate. Over time, the alert feed also surfaces systemic issues — if the same agent, ticket type, or time window consistently generates bad ratings, you can fix the root cause rather than reacting to individual complaints.

How it works

Regardless of which tool you use, every approach follows the same pattern:

1. Detect the rating — Zendesk triggers can fire on the Satisfaction condition (e.g., "Changed to Bad") for immediate native alerts. Alternatively, the n8n and Claude Code approaches poll the satisfaction ratings API (/api/v2/satisfaction_ratings?score=bad) for richer data.
2. Enrich with context — for each bad rating, include ticket details (subject, requester, assignee) so the follow-up agent has everything they need without opening the ticket first. Native triggers include basic placeholders; n8n/Claude Code can add external context.
3. Alert the team — post a message to Slack with the ticket number, customer name, their comment, and a direct link. Native Slack integration sends plain-text; n8n sends Block Kit formatted messages.

The approaches below differ in richness and flexibility — native is simplest, n8n/Claude Code offer more formatting and external integrations.

What you'll need

Which approach should I use?

• Zendesk Native — uses built-in trigger conditions (Satisfaction: Changed to Bad) to fire Slack notifications instantly. Simplest setup, no code, no external tools. Trade-off: plain-text Slack messages with limited formatting.
• n8n (Recommended) — polls the Zendesk CSAT API every 5 minutes, filters new bad ratings, and posts Block Kit alerts to Slack. Best for teams who want rich formatting, external enrichment, or integration with other systems. Free when self-hosted; $24/mo on n8n Cloud.
• Claude Code — a guided Claude Code skill with workflow guidelines and API references. Ask Claude to check CSAT scores, filter by agent or time window, or summarize trends — it generates and runs the right code. Best for teams already using Claude Code who want conversational flexibility alongside scheduled checks.

Choose your approach

Select an approach below to see the full step-by-step guide.