A CSAT survey template is a short customer satisfaction survey you send when a ticket closes. This one asks one required 1-to-5 rating and a few optional follow-ups. You also get the closed-ticket email line and the scoring rule.
It comes from the team behind SherpaDesk: a helpdesk and PSA (professional services automation) a small IT team can run alone. Copy the customer satisfaction survey, build it in the form tool you already use, and put the link in your closed-ticket email.
Key takeaways
A CSAT survey asks people to rate how satisfied they are with a product, a service, or one interaction. In a support queue, the interaction is a ticket. The answer is a rating on a short scale, such as 1 to 5, and the score is the share of satisfied answers.
For IT support there are two kinds of customer satisfaction survey worth running. A transactional survey is "tied to a specific customer interaction with the service desk (i.e. a ticket)." A relationship survey goes out on a schedule to everyone you support. The template below has both: Part A for tickets, Part B for a quarterly MSP client survey.
CSAT is one of three common customer survey measures. Net Promoter Score (NPS) asks how likely people are to recommend you, answered on a zero-to-ten scale. Customer Effort Score (CES) asks how easy it was to get an issue handled, right after the interaction.
| Measure | The question it asks | Scale | Best moment to ask | Where it sits in this template |
|---|---|---|---|---|
| CSAT | How satisfied are you with how we handled this request? | 1 to 5 | When the ticket closes | Q1 (required) and B1 |
| CES | How easy was it to get help? | 5 labeled points | Right after the interaction | Q3 (optional) |
| NPS | How likely are you to recommend us? | 0 to 10 | On a schedule, not per ticket | Not included; add it to Part B if your leadership asks for it |
In a support queue, a customer satisfaction survey carries the weight, because it asks about a ticket you can fix. NPS fits a scheduled survey better. If you add it, ask the recommendation question itself; a satisfaction question scored the NPS way is not NPS.
A closed ticket tells you the work ended. It doesn't tell you whether the person on the other end got what they needed. A short customer satisfaction survey asks, and it puts the answer next to the ticket that caused it.
The bigger risk is what never becomes a ticket. One r/ITManagers poster was asked to start surveying for a reason. Their boss "got an earful in his review about problems we've never heard about and never had a ticket submitted on." A regular satisfaction survey gives that kind of complaint a place to land before the next review.
For an MSP, a falling score from one client is an early warning. Our guide to client transparency and retention covers what to do with it.
Customer satisfaction survey templates often come as a form inside one survey tool. This one is plain text, so it works in any form tool, such as Google Forms, Microsoft Forms, or Tally. Copy the block or download the TXT.
Customer satisfaction survey template · plain textCSAT SURVEY TEMPLATE FOR IT SUPPORT TICKETS
Part A: ticket satisfaction survey, sent at ticket close
Part B: MSP client quarterly survey
Brackets mark what you fill in.
PART A. TICKET SATISFACTION SURVEY
Settings (decide before you build the form)
Form title: How did we do on your request?
Intro line: [Team name] closed your request. One
required question; the rest are optional.
Required: Q1, plus the email field if you make it
required. Q2 to Q6 are optional.
Answers: [named or anonymous]
Named: turn on the form setting that records
each respondent's name or email. Keep Q5 and
Q6. Test the form from an outside client
account.
Named, no such setting: add an email field.
Optional keeps one required question, but
some answers arrive without a name. Required
makes two: say "Two quick answers" in the
intro and email line instead.
Anonymous: no name or email recorded, no email
field. Drop Q5 and Q6, because a ticket number
identifies people.
Surveyed: every closed ticket that gets the
closed-ticket email
Not surveyed: [spam, duplicates, tickets merged
into another ticket]
Frequent requesters: [people who open tickets
most weeks]; keep them in mind when you read
the scores
Results owner: [name, role]
Low score: Q1 rated 1, 2 or 3, or Q2 answered
No or Partly
Low-score review: each one by [the next business
day]; contact the person only if Q6 is Yes
Weekly read: [every Monday], low scores first
Q1. How satisfied are you with how we handled this
request? (required, choose one)
5 Very satisfied
4 Satisfied
3 Neither satisfied nor dissatisfied
2 Dissatisfied
1 Very dissatisfied
Q2. Is the problem fixed? (optional, choose one)
Yes / Partly / No
Q3. How easy was it to get help? (optional, choose one)
Very easy / Easy / Neither easy nor difficult /
Difficult / Very difficult
Q4. What is the main reason for your score?
(optional, short text)
Q5. Ticket number, or a few words about the request
(optional, short text)
Q6. May we contact you about your answer?
(optional, choose one) Yes / No
If Yes: your email or phone [skip if the form
records the email]
Thank-you screen
Thanks. [Name] reads every answer. If the problem
isn't fixed, contact us at [helpdesk email or phone].
Line for the closed-ticket email
Your request is closed. How did we do? One required
question: [survey link]
If the problem isn't fixed, [reply to this email or
call us at phone number].
Scoring
CSAT % = Q1 answers rated 4 or 5 / all Q1 answers x 100
Response rate % = tickets with a matched Q1 answer
/ closed tickets that got the survey email x 100
Matched: Q5 has a ticket number. Unmatched: a
description or blank. Count both in CSAT. Only
matched answers join a ticket and count in the
response rate.
Same ticket number twice: keep the latest answer.
Report both, with the count: "CSAT 85% (34 of 40
answers, 18.9% response rate)".
A small difference between small samples is noise
to watch, not a finding.
PART B. MSP CLIENT QUARTERLY SURVEY
[every quarter, two weeks before the client review]
Send to: [the main contact and two or three regular
users at each client], not only people who opened
a ticket
Window: [two weeks], one reminder
Answers: named, as in Part A
Keep B1 to B4 word for word the same every quarter.
B0. Your company name (required, short text)
B1. Overall, how satisfied are you with IT support
from [company]? (required, 1 to 5 as in Q1)
B2. How satisfied are you with how quickly we respond?
(optional, 1 to 5)
B3. How satisfied are you with how we keep you
informed about open work? (optional, 1 to 5)
B4. How satisfied are you with the reports and reviews
you get from us? (optional, 1 to 5, or "Not
applicable / haven't received these")
B5. What is one thing we should change next quarter?
(optional, short text)
B6. Is a project or change coming up that we should
know about? (optional, short text)
Reporting: show Part B per client, apart from ticket
CSAT. With a few answers per client, read them as
input for the review, not as a trend.
Internal IT: send Part B to all staff [twice a year].
Ask B4 about [the laptop or main app] instead, and
show it only to people who use it.
Decide "Named or anonymous" first, because it shapes the form. A survey link in an email doesn't tell you who clicked it, and a required sign-in doesn't always save a name with the answer.
For a named survey, turn on the form setting that records each respondent's name or email. Then test from an outside client account: the form should open, and the export should name the respondent.
No such setting? Add an email field. Optional keeps the promise of one required question but leaves some answers nameless. Required means two, so the intro and email line say "Two quick answers".
An anonymous form records neither and drops Q5 and Q6, because a ticket number points back to one person. A comment can still give someone away, so promise "no names recorded", not full anonymity. For a ticket satisfaction survey, named usually works better: the person already knows you can see their ticket.
Put one person's name in "Results owner", so the Monday read has an owner.
The survey line rides in the closed-ticket email, so someone who opens a ticket every week sees it every week. List those people under "Frequent requesters": five answers from one person can tilt a small month.
Q1 is the only required question, and it carries the score. It asks about one thing, how the request was handled. Pew Research Center's guidance is to "ask only one question at a time." It warns that double-barreled questions "often lead to responses that are difficult to interpret." "How fast and friendly was the technician?" is two questions. If someone picks 2, you don't know which part failed.
This template uses five labeled points: enough to separate "satisfied" from "very satisfied", few enough to answer at a glance. Pew advises keeping the number of answer choices small, "just four or perhaps five at most," especially in telephone surveys.
| Scale | What it looks like | Good for | Watch for |
|---|---|---|---|
| 5 labeled points | Very satisfied to Very dissatisfied | Ticket surveys; the template default | Keep the same labels every month so the trend holds |
| 3 points or thumbs | Good / OK / Bad, or up and down | Very high-volume queues where one tap matters | Less sensitive to small shifts from one month to the next |
| 0 to 10 | Eleven numbered points | NPS in a twice-yearly survey | More points than one ticket needs, in our view; keep it for NPS |
| Faces or stars | Icons instead of words | Mobile and quick taps | Add a word label to each icon; color alone doesn't carry meaning for everyone |
Whatever you pick, label every point in words. WCAG says color must not be "the only visual means of conveying information." The W3C forms tutorial also asks you to "provide labels to identify all form controls," radio buttons included.
Put Q1 first. Pew notes that "earlier questions can unintentionally provide context for the questions that follow." If Q2 asks "Is the problem fixed?" before the rating, the rating can drift into a fix check.
"Partly" and "No" are the answers that matter. A ticket closed while the problem is still there is a reopen waiting to happen. That's why the template counts either one as a low score, whatever the rating says.
Q3 is the CES question in plain words. If Q2 is "Yes" and Q3 is "Difficult", the problem got fixed, but getting there was likely the hard part. Think of a hard-to-find portal, or three replies before anyone understood the request.
Q4 often tells you more than the rating does. You'll learn things your categories never listed, like "the technician fixed it but deleted my desktop shortcuts." Keep it optional: a required text box adds homework, and some people may close the tab.
Q5 joins the answer to its ticket, and the ticket number is the key. A description or a blank leaves the answer unmatched: it counts in CSAT, but you can't join or deduplicate it. Anonymous answers are unmatched by design.
Q6 asks permission to follow up, and its "If Yes" line collects a way to reach the person when the form doesn't record an email. A "Yes" on a low score is an invitation; a "No" is a request to leave it. Treat a blank Q6 as a No.
Part B goes to people at each client, not just those who opened a ticket. Info-Tech notes that ticket surveys "can leave out many users who may rarely or never contact the service desk."
B0 asks for the company name, so each named answer lands under the right client. B4 offers "Not applicable", because regular users may never see your reports. With three or four answers per client, read them as input for the quarterly conversation, not as a score to trend.
Keep B1 to B4 word for word the same every quarter. An r/ITManagers lead explains why. "I have a series of Likert questions that I've kept basically the same YoY to be able to track those as metrics over time." Reworded satisfaction survey questions can make one quarter hard to compare with the last.
For internal IT or a school, send Part B to all staff and ask B4 only of people who use the device or app. One member learned why when "our worst app got a high score cos people who didn't use it have it a 10." If your form tool can branch on an earlier answer, ask "Do you use [app]?" first.
Send the customer satisfaction survey when the ticket closes, while the person still remembers the request.
One r/ITManagers member at a larger organization works this way: "for every ticket closed, a request for feedback on that ticket goes out." Here is how to set up the same loop in a small team.
Copy the questions into your form tool. Make Q1 required, add the identity setting you chose, and turn on the thank-you screen text.
Pew calls pretesting "an essential step in the questionnaire design process," especially for new questions. Ask two people outside IT to answer on their phones and say what confused them.
Use the email line from the template. Keep the link near the top, before any signature or legal footer.
Common mistake: sending the survey as a separate email an hour later. It arrives cut off from the closing message and is easier to miss.
Send the client satisfaction survey two weeks before each client's quarterly review, with one reminder. Info-Tech's example cadence for relationship surveys is semi-annual or annual, which suits a staff survey.
CSAT is the number of answers rated 4 or 5, divided by all answers, times 100. Our helpdesk metrics guide covers the metric itself, next to resolution time and reopen rate. Count only Q1 answers. A 3 counts as an answer but not as satisfied, so it pulls the score down.
Calculate your CSAT score
Answers rated 4 or 5 ÷ all answers × 100. Your numbers stay in the browser.
Report the response rate next to it: tickets with a matched Q1 answer, divided by the closed tickets that got the survey email, times 100. If the same ticket number shows up twice, keep the latest answer. Unmatched answers count in CSAT but not here, because an anonymous form can send twelve answers for ten tickets.
A small team's customer satisfaction survey gets few answers, and few answers leave a wide margin. The table puts a 95% range around an 85% result at each answer count. It uses the Wilson method from the NIST/SEMATECH statistics handbook.
| Answers | Rated 4 or 5 | CSAT | 95% range |
|---|---|---|---|
| 20 | 17 | 85% | 64% to 95% |
| 40 | 34 | 85% | 71% to 93% |
| 100 | 85 | 85% | 77% to 91% |
| 200 | 170 | 85% | 79% to 89% |
| 500 | 425 | 85% | 82% to 88% |
Computed November 2026.
Read it this way. With 20 answers, scores anywhere from about 64% to 95% are consistent with the same 17-of-20 result. The range narrows as answers grow, to 82% to 88% at 500. It covers sampling only, not how the people who didn't answer feel.
Two rules follow. Report the count with every score, so readers can find its row in the table. And treat a small difference between small samples as noise to watch, not a finding.
Example: an MSP with three technicians and nine clients had 212 tickets in October that got the closed-ticket email with a survey link. Of those, 40 tickets got a matched Q1 answer, one per ticket, a response rate of 18.9%. Of the 40, 34 rated 4 or 5, so October's CSAT is 85% (34 of 40). Settings used: named answers (the form records each email), Q5 asking for the ticket number, and Q6 logged. Here are four matched rows from the response log.
| Ticket | Client | Q1 | Q2 fixed? | Q4 reason | Q6 contact? | Follow-up |
|---|---|---|---|---|---|---|
| #4471 | Harbor Dental | 5 | Yes | "Fixed before my 9 a.m. patient" | Blank | None needed |
| #4496 | Harbor Dental | 2 | Partly | "Scanner works, but only from one PC" | Yes | Called next morning; ticket reopened and fixed |
| #4502 | Westfield Builders | 3 | Yes | "Took three emails to explain" | No | No call; noted for the intake form |
| #4519 | Pine Street Law | 1 | No | "Closed while I was on vacation" | Yes | Owner called; ticket reopened, closing rule changed |
Two of the four rows changed something. Ticket #4496 went back to the queue, and #4519 was reopened and changed a habit: no closing a ticket while the user is out of office without a reply.
Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
Loading form…
The form couldn’t load. Please try again.
Or start your free trial →SHERPADESK · FREE TRIAL
Resolve tickets.
Turn time into revenue.
Bring support tickets, billable time, and invoicing into one place. Built for small IT teams and MSPs.
After your trial, keep your first agent free forever.
SHERPADESK · LIVE DEMO
See tickets, time,
and billing work together.
Walk through ticketing, time tracking, and billing with a product specialist. See how SherpaDesk fits the way your team works.
A live walkthrough tailored to your team.
Expect a low response rate and design for it. An HDI SupportWorld article puts it bluntly: "The return rates for satisfaction surveys are often poor." Its reasons include fatigue, length, the same questions every time, flattering questions, and nothing changing afterward.
Fatigue, length, and repetition. Part A already keeps the satisfaction survey short. To stop fixed questions from feeling stale, refresh what surrounds them: the thank-you screen can name the latest change you made from feedback.
Leading questions. HDI calls this "leading the witness": surveys that ask only what lets IT "promote a high CSAT score." Q1 has as many unhappy points as happy ones, and Q4 asks for the reason, not for praise.
Nothing changes. The form can't fix this one. HDI's advice is to "Act on the data" and to broadcast "the actions that are being (or have been taken)." A two-line note works: "You told us the portal was hard to find. It's now the first link in every reply."
Most mistakes in customer satisfaction survey questions come from the wording, and the rest from how scores get read. Three pairs, each with its fix:
The agree-or-disagree point comes from Pew, which calls the pull toward agreeing "acquiescence bias." Its advice: "A better practice is to offer respondents a choice between alternative statements." Q1 offers five answers instead.
A survey nobody acts on teaches people to stop answering.
A low score is a Q1 rating of 1 to 3, or a Q2 answer of "No" or "Partly", as the template's settings define it. Treat each one as open work, even when the fix itself held.
By the next business day, for each low score. If Q6 says yes, call or email the person; otherwise review the ticket without contacting them. Start with what they wrote, not with a defense. If Q2 says "No" or "Partly", reopen the ticket or open a new one linked to it. Our support ticket response templates include wording for a follow-up that doesn't sound scripted.
In the weekly review. Tag each low score with one cause: the fix, the wait, the communication, or something outside IT, such as a vendor outage. After a month, the tags show where low scores cluster. Three "wait" tags in a week are worth checking against routing and staffing before you look at one technician.
Every quarter. Join the matched answers to your ticket export by ticket number, then look by client, site, or category. For an MSP, bring each client satisfaction score, its count, and the changes you made to the quarterly business review. Our MSP QBR template has a slot for it.
How this works in SherpaDesk
There's no built-in survey tool. You edit the closed-ticket email's custom message and add your own survey link. You can run SherpaDesk as internal ticketing for your own staff or as client-facing ticketing for clients.
Close a test ticket and check that the email arrives with the link.
Admins can stop email replies from reopening closed tickets, so settle that before your survey line says "reply to this email". To join scores to tickets, export ticket data to CSV, XLS, or XML and match on the Q5 ticket number.
A helpdesk and PSA a small IT team can run alone. No contract. No implementation project. No dedicated admin.
Base Camp is $45 per agent per month ($40 billed annually). The first agent is free, forever. You get 14 days free with no card.
Ticket Management In SherpaDesk →
Who this isn't for
Customer experience teams running NPS and CES programs across thousands of customers, with sampling, dashboards, and automated follow-up. Use a dedicated survey tool for that. SherpaDesk has no built-in survey tool, so you read the scores in your form tool or a spreadsheet.
A customer satisfaction survey for IT support needs one required rating with five labeled points and an optional question for the reason. Build it in a form tool, test it, and put the link in the closed-ticket email.
A CSAT survey asks people how satisfied they are with a product, service, or interaction, usually on a 1-to-5 scale. In IT support, it goes out when a ticket closes, and the score is the share of satisfied answers.
Download the TXT above and open it in Word, or paste the copied block into a new document. That gives you a printable satisfaction survey template for a front desk or a staff meeting. For answers you can count, build the same questions in an online form, so every response lands in one table.
"How satisfied are you with how we handled this request?" with five answers: very satisfied, satisfied, neither satisfied nor dissatisfied, dissatisfied, and very dissatisfied. It asks about one thing, and every answer is a word.
We don't quote a target here, because a number without its scale and answer count says little. Keep the same question and scale, and report the count with the score. The precision table above shows how wide the range is at your count.
For ticket surveys, usually not: a named answer lets you follow up on a low score. For a staff survey, some teams go anonymous. Then say so in the intro, record no names or emails, and drop Q5 and Q6.
Send the customer satisfaction survey once per closed ticket. Add a broader survey for everyone you support: every quarter for MSP clients, once or twice a year for internal staff.
Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.