A customer satisfaction survey email asks one question about a conversation or a period of service, on a scale the customer can answer with a single click. It is sent right after the conversation closes. The best version is short enough to read in the preview pane, comes from the person who handled the matter, and asks for a rating first and a comment second. Send it at most once per customer per week, and reply to every low rating within a day.
Send the survey within an hour of closing a conversation, from the teammate's own name, with one rating question and an optional comment box. Cap it at one per customer per week. Use a different template for support, account management, a complaint, onboarding and the annual check, because the question changes with the moment. Read the scores per teammate and per inbox with the response count beside them, and reply to every one and two within a day. Switch the sending to a rule in the inbox once the wording is settled.
When to send a customer satisfaction survey email
The right moment is when the conversation closes, while the customer knows what they are rating and before the memory fades. On a support conversation that means within an hour of the closing reply, either under that reply or as a separate message. On account management it means after a milestone, such as a delivery or a review meeting. On onboarding it means once the customer has done the first real piece of work in the product. A survey sent days later rates a memory, and one sent after every reply rates the same problem several times.
The cap is one request per customer per week, whatever the number of conversations. A customer with three questions on Tuesday is asked about one of them, and a customer whose conversation reopened is not asked again when it closes the second time. Complaints follow their own rule, which is to ask only after the fix is confirmed and never in the same message as an apology. What is CSAT covers the formula and the response rate a team should expect.
How to write the survey email
The email has four parts and nothing else. They are one line of context that names the conversation, the question with its scale, an optional comment box, and a sign-off from the person who handled it. The scale is three faces, five points or five stars, and each option is a link so one click records the answer. The comment box opens after the click rather than in the email, since a blank box in the email lowers the response rate. The sender is the teammate rather than a no-reply address, because a reply to the email should reach a person.
Length matters more than the exact wording of the question. The whole email fits in the preview pane of a phone, which is about forty words before the scale. Nothing is sold in it, nothing is linked except the scale and the comment, and the subject line says what it is. A survey that arrives looking like marketing is deleted with the marketing.
Subject lines for a customer satisfaction survey email
- How did we do with {topic}?
- One click: how was our help today?
- Quick rating for your conversation with {name}
- {Company}: was your issue resolved?
- How is the first month going?
- A one-question check on this year
The subject names the conversation or the period so the customer knows what is being asked about, and it says that the answer is one click. A subject that promises a minute and asks for five loses the customers who open it. The topic placeholder is filled with the subject of the conversation, which is the detail that makes the request feel specific rather than automated.
Five customer satisfaction survey email templates
1. After a support conversation
Subject: How did we do with {topic}? Hi {name}, we closed your conversation about {topic} today. Could you rate the help you received with one click? {scale: very dissatisfied to very satisfied} If anything was missing, reply to this email and it will reach me directly. Thanks, {teammate}
This is the template a rule sends on close. The first line names the topic so the customer knows which conversation is meant, and the scale is the only thing to click. The reply address is the teammate's, so a comment arrives as an email to the person who can act on it.
2. After an account management milestone
Subject: Quick rating for {milestone} Hi {name}, {milestone} is done, and I would like to know how it went from your side. How satisfied are you with how we handled it? {scale} One line on what we could do better next time would help me more than the score. Best, {account owner}
An account survey is sent by the account owner after a milestone rather than after each email, since the relationship is the unit. It asks for the comment more directly than the support version, because the account owner can act on a sentence and has fewer customers to read.
3. After a complaint is resolved
Subject: Is this resolved for you? Hi {name}, you told us on {date} that {problem}, and we {what was done}. Before I close this, I want to check that it is resolved from your side. {scale: not resolved to fully resolved} If it is not, reply here and I will pick it up today. {teammate}
The complaint version asks whether the problem is resolved rather than whether the customer is satisfied, because a customer can be satisfied with the handling and still have the problem. It restates what was done so the customer can disagree, and it is sent only after the fix, never with the apology.
4. After onboarding
Subject: How is the first month going? Hi {name}, you have been with us for a month and have {what they did}. How satisfied are you with the setup so far? {scale} Is there one thing that was harder than it should have been? Reply with it and I will look at it this week. {onboarding owner}
The onboarding survey waits for the customer to have done something real, which the template names. It asks a second question about friction because the answer feeds the next customer's setup. A month is a usual point, and a product with a shorter setup asks after the first completed task.
5. The annual check
Subject: A one-question check on this year Hi {name}, we have worked together for a year this month. Looking at the year as a whole, how satisfied are you with the service you have had from us? {scale} If there is one thing you would change for next year, reply and tell me. I will bring it to our review. {account owner}
The annual check is a relationship question rather than a conversation rating, and some teams send the net promoter question here instead. Either way it is sent from the account owner, away from any open conversation, and the answer is read before the yearly review rather than filed. CSAT vs NPS explains when the recommend question is the better fit.
What to do with the answers
Every rating of one or two is answered by a person within a day, with a reply that names what will be done. The reply changes the customer's view more than the survey did. Every comment is read by the person who handled the conversation and by whoever manages the queue. The ones that describe a repeatable problem go into a list that the team reviews monthly. The scores are reported per teammate and per inbox with the response count beside them, and a teammate's score is compared with the team's only above a floor of responses.
The survey also feeds the team's templates and rules. A comment that the acknowledgment was too vague rewrites the acknowledgment. A run of low ratings on one tag shows that the replies for that kind of request need a better saved reply. The answers are more useful as a list of specific changes than as a number on a dashboard.
How to send customer satisfaction surveys automatically
Once the wording is settled, a rule in the shared inbox or help desk sends the support template when a conversation is closed. It sends from the teammate who sent the last reply, with the cap of one request per customer per week built into the rule. The account, complaint, onboarding and annual versions stay manual, since each depends on a moment that only the person on the account can recognize. A rule can still help with those by setting a reminder on the date the milestone is due.
Sektra sends the survey as a rule when a conversation in a shared inbox closes, on email, WhatsApp and website chat, with the one-per-week cap. It reports the ratings and comments per teammate and per inbox in its analytics. The templates above work as saved replies in the team inbox, and the assistant sets a reminder for the manual ones on the date a milestone falls due. Most help desks have a survey rule of the same kind on their middle plans, and the wording above works in any of them.
Where to start
Start with the support template on one inbox, sent by a rule on close with the weekly cap, and read the scores for a month before changing anything. Add the complaint version by hand for the next three complaints and compare its answers with the support scores. Then add the onboarding and account versions for the customers who reach those moments, and keep the annual check for the review calendar. After three months the team has a baseline on one scale and a list of the comments that led to changes. It also has a survey that customers answer because it is short and comes from a person.
Common questions
When should you send a customer satisfaction survey email?
Within an hour of closing a conversation, while the customer knows what they are rating. For account management, send it after a milestone, for onboarding after the customer has done the first real task, and for a complaint only after the fix is confirmed. Cap it at one request per customer per week.
What should a customer satisfaction survey email say?
One line that names the conversation, one rating question with a clickable scale, an optional comment, and a sign-off from the person who handled it. It fits in a phone's preview pane and contains nothing else, so the customer can answer with one click.
What is a good subject line for a customer satisfaction survey?
A subject that names the conversation and promises one click, such as How did we do with {topic}? or One click: how was our help today? For a complaint, Is this resolved for you? asks the question that matters, and for onboarding, How is the first month going?
How do you send customer satisfaction surveys automatically?
Set a rule in the shared inbox or help desk that sends the support template when a conversation is closed. Send it from the teammate who sent the last reply, limited to one request per customer per week. Keep the account, complaint and onboarding versions manual, since they depend on a moment a person recognizes.
