Loading...
Please wait while we load your content
← All Templates
Customer Support·Intermediate· Saves 2-3 hours/week
Low CSAT Score → Manager Alert → Follow-Up
Instantly alert managers when customers give low satisfaction scores and trigger recovery workflows.
5
Steps
20-30 minutes
Setup Time
2-3 hours/week
Saved / Week
Before You Start
- CSAT survey tool integrated with your support platform (Zendesk Satisfaction Ratings, Typeform, or Nicereply)
- Slack workspace with support management team channels
- Zendesk account for escalation ticket creation (Professional plan or higher)
- ActiveCampaign account for recovery emails and Google Sheets for incident tracking
Step-by-Step Workflow
Trigger
CSAT survey response below threshold
How to configureSet the trigger to fire when a CSAT survey response is received with a score below your threshold (typically 3 or below on a 1-5 scale, or "Bad" in Zendesk's binary satisfied/unsatisfied system). Filter out test responses and internal submissions.
Field Mapping
csat_score
csat_comment
customer_email
customer_name
ticket_id
ticket_subject
agent_name
survey_date
organization
1
Step 1
Alert support manager via Slack DM
How to configureSend an immediate Slack DM to the support manager with full context: CSAT score, customer comment, original ticket details, which agent handled the ticket, and the customer's account history summary. Include a link to both the survey response and the original ticket.
Field Mapping
Slack User→support_manager
Message→" → warning → Low CSAT Alert — Score → {{trigger.csat_score}}/5
Customer→{{trigger.customer_name}} ({{trigger.organization}})
Ticket→#{{trigger.ticket_id}} — {{trigger.ticket_subject}}
Agent→{{trigger.agent_name}}
Comment→\"{{trigger.csat_comment}}\"
View ticket→{{trigger.ticket_url}}"
Send to the support manager, not the agent who handled the ticket — the manager should review and decide on the recovery approach before involving the original agent
2
Step 2
Create escalation ticket in Zendesk
How to configureCreate a follow-up ticket in Zendesk linked to the original ticket. Set it as "Urgent" priority with a "CSAT Recovery" tag. Assign it to a senior agent or the support manager. Include the customer's feedback and the original ticket context in the description.
Field Mapping
Subject→"CSAT Recovery → {{trigger.ticket_subject}}"
Linked Ticket→{{trigger.ticket_id}}
Priority→"Urgent"
Tag→"csat-recovery"
Assignee→support_manager or senior_agent
Description→"Original CSAT → {{trigger.csat_score}}/5
Comment→{{trigger.csat_comment}}
Original ticket→{{trigger.ticket_url}}"
Use Zendesk's "Linked Problem" feature to connect the recovery ticket to the original — this helps identify patterns where specific types of tickets consistently produce low CSAT
3
Step 3
Send apology/recovery email to customer
How to configureSend a personalized recovery email from the support manager (not a generic address). Acknowledge the poor experience, apologize specifically for what went wrong based on their comment, and offer to make it right. Avoid form-letter language.
Field Mapping
To→{{trigger.customer_email}}
From→support_manager@company.com
Subject→"{{trigger.customer_name}}
we want to make this right"
Body→personalized apology
specific reference to {{trigger.csat_comment}}
offer to resolve
direct contact info
Send the recovery email within 2 hours of the low CSAT score — response speed is the #1 factor in turning a dissatisfied customer into a retained one
4
Step 4
Log incident in tracking spreadsheet
How to configureLog the incident in a Google Sheets "CSAT Recovery" tracker. Include the date, customer, original CSAT score, agent who handled it, category of the complaint, and a "Resolution" column to fill in later. This data drives monthly support quality reviews.
Field Mapping
Date→{{trigger.survey_date}}
Customer→{{trigger.customer_name}}
Organization→{{trigger.organization}}
CSAT Score→{{trigger.csat_score}}
Comment→{{trigger.csat_comment}}
Original Agent→{{trigger.agent_name}}
Ticket ID→{{trigger.ticket_id}}
Resolution→(to be filled)
Add a "Days to Resolve" formula column that calculates how long each recovery took — track this metric monthly to ensure your team is getting faster at service recovery
Workflow Complete
Test with sample data before turning on for production.
Estimated Monthly Cost
ZapierFree plan available
Many tools offer free plans that cover basic automation needs. Costs scale with usage volume.
Build This Workflow
Zapier
Free plan available
Make
Free plan available
Import to n8n (One Click)
Ready-to-import n8n workflow
Download this workflow as a JSON file and import it directly into n8n. Open n8n → Workflows → Import from File → select the downloaded JSON. You will need to connect your credentials for each node.
Works with n8n Cloud and self-hosted. After importing, configure your API credentials for each node.Read our n8n review →
Customization Ideas
- Add a customer lifetime value lookup — high-LTV customers with low CSAT get escalated to the VP of Customer Success
- Include a root cause analysis template that auto-populates with the ticket history
- Branch by CSAT score — 1-2 stars trigger immediate escalation, 3 stars trigger a softer check-in
- Add a Calendly step to offer the dissatisfied customer a direct call with a senior support manager
How to Set Up This Automation
- 1Choose your automation platformSign up for Zapier. Free plans are available to get started.
- 2Connect your accountsAuthenticate each tool used in the workflow. You will need active accounts for .
- 3Set up the triggerSet the trigger to fire when a CSAT survey response is received with a score below your threshold (typically 3 or below on a 1-5 scale, or "Bad" in Zendesk's binary satisfied/unsatisfied system). Filter out test responses and internal submissions.
- 4Add action steps and map fieldsAdd each step in order. The key is mapping data correctly between steps — make sure fields like email, name, and IDs pass through from the trigger to each action.
- 5Test with sample dataRun the workflow with a test record before turning it on for production. Verify each step executes and data appears correctly in each tool.
- 6Turn it on and monitorActivate the workflow and check the first 5-10 runs. Set up error notifications so you know immediately if something breaks.
Common Pitfalls to Avoid
- •Missing field mappings — Double-check that every required field in each action step has data mapped from the trigger or a previous step.
- •Rate limits — If you process high volume, check each tool's API rate limits. Add delays between steps if needed.
- •Error handling — Add error notification steps so failed runs don't go unnoticed. Most platforms support email or Slack alerts on failure.
- •Duplicate handling — Add a "search before create" step to avoid creating duplicate records in your CRM or database.
Frequently Asked Questions
How do I set up this customer support automation?
This workflow has 5 steps. Start by connecting your trigger (CSAT survey response below threshold) to an automation platform like Zapier, then add each action step. Most users complete the setup in 15-30 minutes.
Which automation platform should I use for this workflow?
We recommend Zapier, Make for this workflow. Zapier is easiest for beginners, while n8n is best for developers who want full control.
How much time will this automation save?
This automation typically saves 2-3 hours/week. The exact savings depend on your current volume and how much manual work each step currently requires.
Related Templates
Common Question → Auto-Reply → Knowledge Base Update
Detect common support questions and send instant auto-replies while flagging gaps in your knowledge base.
5-8 hours/weekadvanced
Ticket Created → Priority Routing → SLA Timer
Route new support tickets by priority and start SLA timers automatically for faster resolution.
4-6 hours/weekintermediate
Ticket Escalation → Manager Notification → SLA Update
Handle ticket escalations smoothly with automatic manager notifications and SLA adjustments.
2-3 hours/weekintermediate
Ticket Resolved → Feedback Survey → Metrics Update
Automatically send satisfaction surveys when tickets are resolved and track support team metrics.
1-2 hours/weekbeginner
Not sure which automation platform to use?
Find Your Software