What is a feedback request email, and what makes customers reply?
A feedback request email is a short message that asks a customer about one specific experience — an order, an appointment, a support ticket, a quarter of working together — and gives them one easy way to answer. The ones that get replies share four traits: they arrive while the experience is still fresh, they name the exact thing you are asking about, they ask one question (or link to a survey that takes a minute or two), and they come from a real person rather than a "noreply" address.
Below you will find 12 copy-and-paste feedback email templates for the moments that matter most, a subject line for each, a timing table, and a simple method for linking each email to a short survey. All names, products and wording are examples to adapt.
Key takeaways
- Ask about one moment, not "our company in general": the order, the visit, the ticket, the onboarding.
- Put the first question inside the email (a 0–10 scale or a few clickable faces) so the first click already counts as an answer.
- Match the timing to the experience: after delivery for products, the same day for services, within a day for support.
- Keep the body under about 100 words and use a reply-to address someone actually reads.
- Send one reminder at most, then stop. Close the loop by telling customers what you changed.
How do you ask a client for feedback in an email?
To ask a client for feedback in an email, thank them for the specific purchase or project, say in one sentence why their opinion matters, ask one clear question, and tell them how long answering takes. Every template in this article follows the same five-part structure:
- Context: "You received your order on Tuesday" or "Your appointment with Anna was this morning". The customer should know in one line what you are asking about.
- The ask: one question, phrased the way you would say it out loud.
- The effort: "one click", "two minutes", "three questions". Be honest; an underestimated survey costs you trust.
- The reason: what you will do with the answer ("we read every reply and use them to plan next season's menu").
- A human sign-off: a first name, a role, and a reply-to address that reaches a person.
Note the difference between this email and the survey itself: this article covers the invitation. For what to ask once the customer clicks, see our guide to customer satisfaction survey questions.
12 feedback email templates you can copy
Replace everything in [brackets]. Each feedback email example below lists when to send it and a subject line that has been written to be specific rather than generic.
1. After a purchase (ecommerce)
Send: 3–7 days after delivery, once the customer has had time to use the product. Subject: "How's your [product name] working out, [First name]?"
Hi [First name],
Your [product name] arrived on [delivery date]. Now that you've had a few days with it, we'd love to know: how is it going?
Rate it in one click: [1] [2] [3] [4] [5]
Clicking a number opens a two-question form — about a minute. Every answer goes straight to our product team.
Thanks for choosing us,
[Name], [Shop name]
2. After a service or appointment
Send: the same day, ideally 2–4 hours after the appointment ends. Subject: "How was your visit with [staff name] today?"
Hi [First name],
Thank you for coming in today for your [service]. [Staff name] asked me to check that everything went the way you hoped.
Could you tell us how it went? It's three quick questions: [Share your feedback]
If anything wasn't right, just reply to this email — it comes to me directly.
[Name], [Business name]
3. After a support ticket is closed
Send: immediately after the ticket is marked solved, or within 24 hours. Subject: "Did we solve your problem? (ticket #[number])"
Hi [First name],
We've marked your request about [topic] as solved. Was it actually solved for you?
[Yes, all good] [Not quite]
If you click "Not quite", the ticket reopens and [agent name] will get back to you. Either way, one click is all we need.
The [Company] support team
4. One-question NPS email
Send: for ongoing relationships (subscriptions, memberships, regular clients), every 3–6 months, never right after a support issue. Subject: "One question, [First name]"
Hi [First name],
Just one question today:
How likely are you to recommend [Company] to a friend or colleague?
[0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
0 = not at all likely, 10 = extremely likely. After you click, you can tell us why in a sentence — or not. Thank you!
[Name], [Company]
Each number links to your survey with the score pre-filled, so the answer is recorded even if the customer closes the page. If you are new to the score, our glossary explains how the Net Promoter Score is calculated.
5. One-click satisfaction rating (CSAT)
Send: right after a short, transactional interaction — a delivery, a booking, a chat. Subject: "Quick one: how did we do?"
Hi [First name],
How satisfied were you with your [delivery / booking / chat] today?
[Very unhappy] [Unhappy] [Okay] [Happy] [Very happy]
That's it — one click. Thank you for helping us get better.
[Company]
6. Product review request
Send: 7–14 days after delivery, and only to customers who have not reported a problem. Subject: "Would you review your [product name]?"
Hi [First name],
Other shoppers trust reviews from people like you far more than anything we could write ourselves. If you have two minutes, would you share what you think of your [product name]?
[Write a review]
Honest is better than glowing — good or bad, your review helps the next person decide.
Thank you,
[Name], [Shop name]
A review request email differs from a feedback email: a review is public and helps future buyers, while feedback is private and helps you. Don't mix both asks in one message.
7. After onboarding (first 30 days)
Send: around day 21–30 of a subscription or software account. Subject: "Is [product] doing what you signed up for?"
Hi [First name],
You've been using [product] for about a month. When you signed up, you mentioned [goal, e.g. "sending a monthly newsletter"]. Is that working?
Tell us in three short questions: [Start]
If something is in your way, reply here and I'll personally help you sort it out.
[Name], [role], [Company]
8. B2B account review (quarterly check-in)
Send: once a quarter, or 4–6 weeks before a contract renewal. Subject: "Your Q[quarter] review with [Company] — 3 questions before we meet"
Hi [First name],
Ahead of our quarterly review on [date], I'd like to make the meeting about what matters to your team rather than what we want to present.
Could you (or anyone on your team who works with us) answer three questions?
- What has worked well this quarter?
- What has slowed you down?
- What should we do differently next quarter?
[Answer the 3 questions — about 5 minutes]
I'll share a summary at the start of our call.
[Name], Account manager, [Company]
In B2B, one relationship often involves several people. Ask the main contact to forward the link to colleagues, and include a "Your role" question in the survey so you can tell the decision-maker's view from the daily user's.
Most of these emails can go out on their own: trigger them after a purchase, a tag or a date with Mailpro™ automated emails, and the right request reaches each customer at the right moment.
9. After an event or webinar
Send: the same day or the next morning, together with the replay or slides. Subject: "Your slides from [event] + one question"
Hi [First name],
Thanks for joining [event name]. As promised, here are the [slides / replay]: [link]
One question while it's fresh: what topic should we cover next time? [Vote for the next topic]
See you soon,
[Name], [Organizer]
10. The plain-text "personal note"
Send: to a small group of your best or longest-standing customers, in plain text with no design. Subject: "Can I ask you something?"
Hi [First name],
I'm [Name], founder of [Company]. You've been with us since [year], so your opinion matters a lot to me.
If you could change one thing about [Company], what would it be?
Just hit reply. I read every answer myself.
[Name]
This format works because it looks like a message from a person, not a campaign. Use it sparingly; it loses its effect if every customer gets one every month.
11. After a complaint has been resolved
Send: 1–2 weeks after the fix, once the customer has had time to see that the problem is truly gone. Subject: "Following up on [issue], [First name]"
Hi [First name],
A couple of weeks ago you told us about [issue]. We [what you did, e.g. "replaced the part and changed our packing process"].
Has everything been working since? [Yes] [No, there's still a problem]
Thank you for telling us — it helped us fix it for other customers too.
[Name], [Company]
12. The reminder
Send: one reminder, 3–5 days after the first email, only to people who did not open or did not click. Subject: "Still have a minute for [product / visit]?"
Hi [First name],
A quick nudge in case our last email got buried: we'd still love to hear how [your order / your visit] went.
[Share your feedback — 1 minute]
If now isn't a good time, no problem — this is the last time we'll ask about it.
[Name], [Company]
Reminders deserve their own strategy (timing, segments, wording). We cover them in detail in reminder survey emails.
Feedback request email subject lines: what works?
The best feedback request email subject lines are specific and personal: they name the product, visit or ticket and, when it fits, the customer's first name. Vague lines like "We value your opinion" look like every other survey and get skipped. Use this table as a starting point:
| Situation | Specific subject line (use) | Generic subject line (avoid) |
|---|---|---|
| After a purchase | How's your [product name] working out? | Customer feedback survey |
| After a service | How was your visit with [staff name] today? | Tell us about your experience |
| Support ticket | Did we solve your problem? (ticket #[number]) | Rate our support |
| NPS | One question, [First name] | Our annual satisfaction survey |
| Review request | Would you review your [product name]? | Leave us a review! |
| B2B account review | 3 questions before our Q[quarter] review | Feedback request |
| Reminder | Still have a minute for [product]? | REMINDER: survey closing |
A few rules apply across all of them: keep the line short enough to be read on a phone, state the effort ("one question", "1 minute") when it is genuinely small, and avoid all caps and pressure words. Use the preheader to add the second piece of information, for example "Takes 60 seconds — your answer goes straight to our team."
When should you send a feedback request email?
Send a feedback request email at the moment the customer can judge the experience: after they have used the product, the same day as a service, and within a day of a support interaction. Too early and they have nothing to say; too late and they have forgotten.
| Experience | When to send | Why |
|---|---|---|
| Physical product | 3–7 days after delivery | Time to unpack and use it |
| Product review (public) | 7–14 days after delivery | A considered opinion, not first impressions |
| Appointment, meal, stay | Same day, a few hours later | Memory is fresh and specific |
| Support ticket | When solved, or within 24 hours | Ties the answer to the agent and the fix |
| Software or subscription | Day 21–30, then every 3–6 months | Enough use to judge value |
| B2B account | Quarterly, and 4–6 weeks before renewal | Leaves time to act before the decision |
| Event or webinar | Same day or next morning | Pairs with the replay or slides |
Two more timing rules: never send a satisfaction or NPS request to someone with an open complaint (resolve it first, then use template 11), and set a minimum gap between requests to the same person so a loyal customer is not asked after every single order.
How do you link a feedback email to a short survey?
The simplest way is to place the first question inside the email as clickable buttons, with each button linking to the survey and pre-filling that answer. The customer's first click is already a response, and the follow-up questions are optional. Here is how to set it up:
- Build a short survey. Two to five questions: the rating, one "why?" open field, and at most one or two questions about specifics. Starting from a feedback survey template saves time.
- Connect it to your contact list so answers are attached to the right customer and you don't need to ask for their name or email again.
- Create one link per answer (one per star, face or number) and place them as buttons in the email.
- Make it mobile-first. Big buttons, one question per screen, a visible progress indicator.
- Say thank you on the last screen and, where it makes sense, tell people what happens next.
Email is not the only channel for a survey; you can also place it on a receipt page, a QR code or your website. Our article on ways to share a survey covers each option. And if fewer people answer than you hoped, see how to boost survey response rates.
What mistakes stop customers from replying?
- Sending from "noreply". It tells the customer you don't want to hear from them, which is the opposite of the message.
- Asking about everything. A 25-question survey linked from a "quick feedback" email trains people to ignore your next request.
- Asking only happy customers. Filtering requests so only satisfied buyers are asked gives you flattering data and no direction.
- Mixing asks. Feedback, review, referral and a discount code in the same email: the customer does none of them.
- Never closing the loop. If people never see a change, they stop answering. A short "You said, we did" section in your newsletter fixes this.
- Ignoring the people who leave. Customers who unsubscribe or cancel are a feedback source too; a short unsubscription survey tells you why.
On the compliance side, keep the basics: send only to people you have a relationship with or consent from, identify your company clearly, and include an unsubscribe link in any email that is part of your marketing.
Frequently asked questions
How do you politely ask for feedback in an email?
Thank the customer for the specific purchase or visit, ask one clear question, say how long it takes, and explain what you will do with the answer. Polite also means easy: one click, a reply-to address that works, and no pressure if they don't have time.
What is a good subject line for a feedback request email?
A good feedback request email subject line names the specific experience and, if possible, the person: "How was your visit with Anna today?" works better than "Customer survey". Mentioning a small effort, such as "one question", also helps when it is true.
How long should a feedback email be?
A feedback email should be short enough to read in a few seconds — roughly 50 to 100 words in the body. The detail belongs in the survey, not in the invitation.
Should you offer an incentive for customer feedback?
A small thank-you, such as a discount on the next order or entry into a draw, can help for longer surveys. For one-click ratings it is usually unnecessary. Never make an incentive depend on a positive answer, and check the rules of any review platform before rewarding public reviews.
How many times should you ask for feedback?
Send one request and at most one reminder per experience, then stop. For ongoing customers, space general surveys such as NPS several months apart so each one still feels worth answering.
Mailpro and customer feedback
Feedback request emails that send themselves, survey included
Build a short survey in Mailpro, drop it into any of these 12 templates and let automation send each request at the right moment. Swiss-hosted, GDPR-native, and priced by sends, not contacts.