Asking a customer for a testimonial can feel uncomfortable. You want to learn what worked and share their experience, but you do not want the request to sound like a demand for praise.
The best testimonial request emails make three things clear: why you are asking this particular person, what kind of feedback would be useful, and how little effort it takes to respond. They also leave room for an honest answer, including an experience that was mixed or disappointing.
This guide contains eight original templates for common situations: completed projects, recent purchases, repeat clients, software onboarding, courses, referrals, case study interviews, and a gentle follow-up. You can adapt the wording to your relationship with the recipient rather than copying a generic "please leave us a five-star review" message.
Important distinction: A private testimonial request and a public review request are not identical. If you plan to publish someone's words, name, photo, job title, or business, get appropriate permission and preserve the meaning of their feedback. Platform rules and applicable advertising or privacy requirements may impose additional conditions.
What a good testimonial request email does
A testimonial request works best when it is part of an existing customer relationship, not a surprise sales pitch.
There are four jobs to do:
- Provide context. Mention the project, purchase, or service experience so the reader knows why you contacted them.
- Invite honest feedback. Ask what the experience was like rather than requesting a flattering quote.
- Make replying simple. One or two clear prompts are often easier than an empty request to "write a testimonial."
- Respect the customer's choice. Make it easy to decline or ignore the request without an uncomfortable exchange.
A testimonial is more useful when it explains the situation and the actual experience in the customer's own words. "They were great" may be sincere, but "The team explained each revision and delivered the agreed pages before launch" gives another buyer clearer context.
The principle resembles clear email CTA writing: a recipient should know exactly what you are asking them to do.
For other email examples and guides, visit the email copy category.
When to ask for a testimonial
There is no universal number of days to wait. The useful trigger is evidence that the customer has experienced what you delivered.
After a service project: Ask when the deliverables have been accepted and the client has had an opportunity to use them. If the work has not been reviewed yet, a satisfaction check is more appropriate.
After a physical-product purchase: Allow enough time for delivery and actual use. A request sent before the package arrives signals that the feedback is just a marketing checkbox.
After software onboarding: Wait until the customer has completed a meaningful task. A customer who logged in once may not have enough context for a useful testimonial.
After a course or workshop: Give the learner time to apply an exercise. Ask about the learning experience or a specific takeaway rather than implying results that have not been measured.
After a problem or complaint: Resolve the issue first. Do not pressure someone with an unresolved problem to provide positive public feedback.
These are practical guidelines, not automated timing rules. Your actual customer journey should determine when the request feels relevant.
A five-part testimonial request framework
Write the first draft using this structure:
1. Specific opening: "Thanks again for working with us on the new booking page."
2. Reason for asking: "We are collecting feedback on how our review process worked for clients."
3. Manageable question: "What was most helpful, and what could we do better?"
4. Low-friction reply: "A couple of sentences in reply to this email is plenty."
5. Permission boundary: "We will ask separately before using any part of your response publicly."
Not every email needs five separate paragraphs. The structure is a checklist for information, not a formula that must sound robotic.
If the intended use is a public review on a third-party platform, use the platform's permitted process rather than assuming you may copy an internal testimonial request into a review solicitation. Any incentive or material relationship needs appropriate handling and disclosure.
Eight testimonial request email templates
The business and customer situations below are fictional examples. Replace names, project details, and any product descriptions with facts from your own customer relationship. Never invent a customer's experience or write their answer for them.
1. Completed client project
Best for: Freelancers, agencies, designers, and consultants after a project has been completed and accepted.
Subject: Could I ask about your experience with [project name]?
Hi [First name],
>
Thanks again for working with us on [specific project].
>
We're reviewing what clients found useful about the process. If you have a moment, what made the biggest difference for you, and is there anything we could have handled better?
>
Two or three sentences in a reply would be more than enough. No pressure if now isn't a good time.
>
Thanks, [Name]
Why it works: The project reference makes the email personal. The request invites both positives and improvements, making it a genuine feedback conversation rather than a scripted endorsement.
Adapt it: If you are collecting feedback only for internal service improvement, say so. Ask for publication permission later if the reply would make a helpful testimonial.
2. A recent product purchase
Best for: Ecommerce businesses asking customers about something they have had time to receive and use.
Subject: How is [product name] working out?
Hi [First name],
>
I wanted to check in now that you've had some time with [product name].
>
What has your experience been like so far? If anything surprised you, worked particularly well, or could be improved, I'd appreciate hearing it.
>
You can reply directly to this email. A short, honest note is perfect.
>
[Name]
Why it works: It avoids asking for a rating before confirming that the buyer actually used the product. The wording allows criticism instead of treating customer feedback as advertising inventory.
Adapt it: If you send customers to a third-party review platform, check that platform's review-solicitation and incentive policies first. Do not selectively request public reviews only from customers you expect to be positive if the platform prohibits that practice.
3. A repeat service customer
Best for: Businesses with an ongoing relationship, such as accountants, maintenance providers, or marketing agencies.
Subject: One quick question about working together
Hi [First name],
>
We've now worked together on [relevant scope or period], and I'd value your perspective.
>
What's one part of the service that has been especially useful in your day-to-day work? And is there anything you'd like us to improve?
>
A few lines by email is fine. We appreciate the chance to learn from your experience.
>
[Name]
Why it works: Long-term customers have useful context, but they may also be busy. A specific question is easier than asking them to summarize an entire relationship.
Adapt it: Avoid asking the recipient to confirm a claimed outcome you have not independently verified. "Did we save you ten hours a week?" is a leading question unless the customer has actually reported that saving.
4. Software customer after a successful task
Best for: SaaS products where you know the customer has used a feature, not simply signed up.
Subject: How did [specific workflow] go for you?
Hi [First name],
>
I saw that your team completed [specific workflow, if you are permitted to use this account information]. I'd love to understand how that experience felt.
>
Was anything easier than you expected? Was there a step that caused confusion?
>
If you'd like to share a few sentences, just hit reply. This feedback helps us improve the product.
>
[Name]
Why it works: It asks about a concrete task and opens the door to product feedback. That makes it easier for the customer to answer from memory.
Adapt it: Personalization should be based only on information the business is authorized to use. If you do not have a reliable task signal, use a broader check-in instead of pretending you know what happened.
5. A course or workshop participant
Best for: Educators, creators, and trainers after a participant has had time to try the material.
Subject: What did you take away from [course or workshop]?
Hi [First name],
>
Thanks for joining [course or workshop]. I'm interested in what was useful once you had a chance to try the material.
>
Was there a lesson, example, or exercise that helped you approach something differently? What could we make clearer for future participants?
>
A short reply would be very helpful. There is no need to share results you aren't comfortable discussing.
>
[Name]
Why it works: It invites an account of the learning experience rather than prompting dramatic claims about income, grades, or business performance.
Adapt it: When using educational testimonials publicly, do not imply that one participant's outcome is typical without appropriate substantiation and context.
6. After a customer makes a referral
Best for: Service businesses whose customers have voluntarily recommended them to someone else.
Subject: Thanks for the introduction
Hi [First name],
>
Thank you for introducing us to [person or company, where appropriate]. We appreciate your trust.
>
Since you've worked with us yourself, I'd also be interested in what you felt comfortable recommending. What stood out about the experience?
>
Even one or two sentences would be useful. Please don't feel obliged to reply just because you made the introduction.
>
[Name]
Why it works: The referral provides a natural reason to ask, but the note avoids turning the customer's goodwill into an obligation.
Adapt it: Never reveal another person's private details in an email without an appropriate basis. If the introduction is confidential, simply say "Thanks for recommending us."
7. An invitation to discuss a case study
Best for: B2B customers who may have a detailed story to share, but whose company requires an approval process.
Subject: Would you be open to a short customer story interview?
Hi [First name],
>
Your team used [service or product] during [specific project], and we'd be interested in learning how the process worked from your perspective.
>
Would you be open to a 15-minute conversation about what you were trying to achieve, what actually happened, and what you might change?
>
This would be an interview, not a commitment to be featured. We would confirm any proposed quotes, identifying details, and publication permissions before sharing a customer story.
>
No problem at all if that isn't something your team can do.
>
[Name]
Why it works: It separates an interview invitation from consent to publish. The customer can consider company approval requirements before sharing information intended for a public case study.
Adapt it: Verify specific metrics with the customer and distinguish observations from independently measured results. Never turn an internal estimate into a definitive public claim.
8. One gentle follow-up
Best for: A customer who has not responded to the original request and has no open support or service issue.
Subject: Re: Your thoughts on [project or product]
Hi [First name],
>
Just bringing this back to the top of your inbox in case you meant to reply.
>
If it's easy, I'd still appreciate a sentence or two about your experience with [specific project or product]. If not, there's nothing else you need to do.
>
Thanks again, [Name]
Why it works: It restores context without guilt, urgency, or false familiarity. It gives the recipient an easy exit.
Adapt it: One reminder is usually enough for a simple request like this. Stop when someone declines or asks not to receive further messages. For follow-up structure in a different context, see the follow-up email template guide.
Subject lines that explain the request
Good subject lines should match what the email actually asks. They do not need artificial curiosity.
Use the recipient's real context where possible:
- Could I ask about your experience with [project]?
- How is [product] working out?
- One question about your recent [service]
- What was useful about [course]?
- Feedback on our [process or feature]?
- Would you be open to a customer story interview?
- Thanks again for working with us
- Your thoughts on [specific outcome or deliverable]?
Avoid subjects like "Urgent: We need your review" when nothing is urgent, or "Your account needs attention" when you simply want marketing feedback. The subject line should earn the open without misleading the reader.
Preview text can add context without repeating the entire subject. For example:
Subject: How did your website review go?
Preview: One short question about what helped and what we could improve.
See the email preview text examples guide for further ways to make the subject and preview work together.
Questions that lead to useful, honest feedback
A testimonial is often stronger when you ask about an experience instead of requesting a polished compliment.
Choose one or two, not all of these prompts in the same email:
- What were you trying to accomplish when you first contacted us?
- What part of the product or service was most useful?
- Was there anything confusing or harder than expected?
- What changed in your workflow after using it?
- What would you tell someone considering the same service?
- Which feature or deliverable do you use most?
- What should we improve for the next customer?
- Is there a detail you think a prospective customer should know?
The answers may be positive, negative, or mixed. That is useful information. Do not edit a quotation to reverse the customer's meaning or remove a qualification that materially changes the claim.
If a customer offers a specific performance number, ask how it was calculated and whether it can be verified before treating it as a marketing claim. The better the evidence, the more responsibly you can present it.
Asking permission to publish a testimonial
A reply to an email does not automatically grant permission to publish the person's name, quote, or image. Handle public reuse as a separate step.
Sample permission email:
Hi [First name],
>
Thank you for sharing your feedback. Would you be comfortable with us featuring this exact excerpt on our website?
>
"[Insert the proposed quote exactly, preserving its meaning.]"
>
We would display it with [name, role, and company, or a clearly described anonymous attribution].
>
Please let me know if you approve that use or would prefer we keep your feedback private. Either answer is completely fine.
>
[Name]
Store the response and any conditions of permission. If the proposed wording differs from the original message, show the edited version and seek approval before publishing it.
A private testimonial and a review on a marketplace or review site may be subject to different policies. Treat those as different workflows.
Before-and-after rewrites
These examples show how small changes can remove pressure and make the reply easier.
Rewrite 1: The demanded endorsement
Weak
We loved working with you. Please write us a glowing testimonial we can put on our homepage.
Stronger
Thanks for working with us on the launch. If you have a minute, what part of the process was most helpful, and what could we improve? A short reply is plenty.
Why it works: The stronger version asks for experience, not praise. It also avoids assuming public permission.
Rewrite 2: The empty question
Weak
Can you send feedback?
Stronger
Now that you've used the new booking form, was there a step that felt easier or harder than before?
Why it works: The recipient can answer a specific question without having to guess what kind of feedback is expected.
Rewrite 3: The guilt-based reminder
Weak
I emailed last week and still haven't received your testimonial. Can you send it today?
Stronger
Following up once on my earlier question about your experience with the workshop. If now isn't a good time, no reply is needed.
Why it works: The revised message respects the recipient's time and avoids pretending that feedback is owed.
Seven common testimonial request mistakes
- Asking before the customer has experience. A buyer cannot describe meaningful use of a product they have not received.
- Only asking for positive feedback. This encourages biased responses and can undermine the credibility of the resulting collection.
- Asking too many questions. A survey disguised as a two-minute email creates more work than the customer expected.
- Writing the testimonial for the customer. Supplying ready-made praise may produce wording that is not the customer's genuine account.
- Failing to separate feedback from publication permission. Private customer responses should not be treated as automatically cleared for public marketing.
- Pushing repeatedly after silence or a refusal. Follow-up pressure damages the relationship and may conflict with messaging preferences.
- Using unverifiable outcome claims. Numbers, before-and-after statements, and performance stories need adequate context and evidence.
The same principle applies to other sales and email writing: a specific, truthful message beats pressure. For adjacent examples, see promotional email copy and offer copywriting.
Quick checklist before sending
Use this checklist on the finished email rather than the template alone:
- Did we mention a real project, product, or experience?
- Has the recipient had a reasonable opportunity to use what we delivered?
- Are we inviting honest feedback rather than requesting praise?
- Is the request limited to one or two manageable questions?
- Can the recipient reply directly without creating an account?
- Is the subject line accurate?
- Have we avoided inventing customer results, timelines, or relationships?
- Does the email respect a decline or no response?
- If we want to quote the response publicly, will we request appropriate permission?
- Are any review-platform policies, incentives, privacy rules, and advertising requirements accounted for?
A simple test is to read the email from the recipient's perspective: do they understand why you contacted them, what you want to know, and whether answering is optional?