What it is
The CSAT Survey & Scoring Template is a spreadsheet that turns customer satisfaction from a vague sense into a measured, comparable number. CSAT (Customer Satisfaction) is a transactional metric: right after a ticket closes, it asks the customer how satisfied they were with the support they received, and the share who rate it 4 or 5 (top-2-box) becomes your CSAT score. The workbook gives you a ready-to-fire post-resolution survey, a scoring sheet that computes CSAT percentage and Customer Effort Score from raw responses, benchmark targets with red-amber-green status, and a per-agent breakdown so coaching is based on data rather than anecdote.
The template is a multi-sheet Excel file: an Instructions tab explaining what CSAT measures and how to get honest data, a Survey Design sheet that lays out the questionnaire to fire after resolution (a one-click satisfaction rating plus an effort question and an open comment), a Scoring sheet where you enter the count of responses at each rating and it computes CSAT percentage, CES, and response rate, and an Agent Breakdown sheet that calculates per-agent CSAT against the team target. Question 1 is the CSAT driver (top-2-box = satisfied) and Question 2 captures effort.
It exists because support teams that don't measure satisfaction are flying blind on the one thing that determines whether customers stay — and teams that measure it badly are worse off, acting on skewed data. The template enforces the practices that make CSAT trustworthy: survey immediately after resolution while the experience is fresh, keep it to two taps so people actually respond, and always allow a comment because the verbatim is where the real insight lives. With clean data, CSAT becomes a coaching tool, a quality signal, and a leadership metric all at once.
What it's used for
Teams use a CSAT template to measure, score, and act on customer satisfaction at the ticket level — and to do it with data clean enough to trust. Specifically it's used for:
- ✓ Firing a short post-resolution survey the moment a ticket is marked solved, with a one-click satisfaction rating, an effort question, and an open comment — kept to two taps so response rates stay healthy.
- ✓ Computing CSAT percentage as the top-2-box score — responses of 4 or 5 on a 1-to-5 scale divided by total responses — so the headline number is calculated consistently every period.
- ✓ Capturing Customer Effort Score (CES) alongside CSAT to measure how hard the customer had to work to get helped, a strong predictor of loyalty that satisfaction alone can miss.
- ✓ Tracking response rate so you know how representative the score is — a great CSAT from a 5% response rate is far less trustworthy than a good one from 25%.
- ✓ Comparing actual CSAT, CES, and response rate against editable benchmark targets with red-amber-green status, so leaders can see at a glance where support stands.
- ✓ Breaking CSAT down per agent — entering each agent's satisfied and total responses — so coaching is grounded in data, with a 'low sample' flag to avoid judging agents on too few responses.
- ✓ Mining the open-comment verbatims, which is where the actionable insight lives — a 3-star rating with a comment tells you far more than the number alone about what to fix.
Who uses it
CSAT data flows from the customer who rates a ticket up to the leaders who report on support quality, with managers and agents in between using it to improve. The template serves each level with the view they need.
Context & good to know
CSAT is the most widely used support satisfaction metric precisely because it's transactional and specific — it asks about one interaction while it's fresh, rather than a general feeling. Most help desk platforms, including Zendesk Support, Freshdesk, and Zoho Desk, can fire a CSAT survey automatically when a ticket is solved, which is exactly when the template recommends sending it. The standard calculation is top-2-box: on a 1-to-5 scale, ratings of 4 and 5 count as satisfied, and CSAT percentage is satisfied responses divided by total responses. Keeping that definition stable period over period is what makes the trend meaningful.
The template is opinionated about getting honest data because a biased CSAT score is worse than no score — it drives wrong decisions with false confidence. Three practices protect the data: survey immediately after resolution (memory fades and ratings drift if you wait), keep it to two taps (long surveys crater response rates and over-represent the very angry and the very delighted), and always allow a comment (the verbatim is where the actionable insight is — a 3-star rating with 'it took three replies to get an answer' tells you what to fix in a way the number can't). Response rate is tracked alongside CSAT for the same reason: a 95% CSAT from a 5% response rate is not the win it appears to be.
Pairing CSAT with Customer Effort Score (CES) catches something satisfaction alone misses. A customer can be satisfied with the outcome but exhausted by the process — and high-effort experiences predict churn even when the satisfaction rating is fine. Question 2 captures effort (with a clear scale direction so higher agreement means lower effort), giving the team a second dimension to manage. Reading CSAT and CES together is more diagnostic than either alone: high CSAT with high effort flags a process that's grinding customers down even though the answers are right.
The per-agent breakdown turns CSAT into a coaching tool, but the template guards against misuse. It computes per-agent CSAT against the team target and flags agents with too few responses as 'low sample' so they aren't judged prematurely. The guidance is explicit: coach on patterns, not single scores — one bad rating is noise, a consistent pattern across verbatims is signal. Reference points help calibrate expectations: CSAT of 90%+ is excellent, 80-90% solid, and below 80% needs attention, while support survey response rates of 15-30% are typical. CSAT also feeds the broader metrics dashboard, where it sits alongside SLA attainment and resolution time as one of the headline numbers leadership tracks.