Every testimonial request email template on this page follows the same skeleton: a specific reason for writing now, one small ask, and a single link that does all the work. Copy the one that matches your situation, swap the bracketed placeholders, and send it while the good moment is still warm.
The short version:
- Send the ask at a moment of success, not on a calendar schedule.
- One email, one ask, one link. No attachments, no “hop on a quick call”.
- Personalize the first line with something only that customer’s file would tell you.
- Follow up exactly once, five to seven days later, then stop.
- Point the link at a form that captures the words, a name, a photo, and publishing permission in one pass.
What makes a testimonial request email template work
Four things, and none of them are clever copywriting. The ask arrives at a moment of success, so writing something positive is easy. It names a specific reason for emailing today, so it reads as personal rather than automated. It makes exactly one request, with one link and an honest time estimate. And it makes clear the customer controls what gets published.
People mostly say yes when asked at the right moment — the evidence, and the full playbook on timing, channel, and tone, lives in how to ask for a testimonial.
These templates handle the ask itself. What you prompt for inside the form is a separate craft, covered in testimonial questions to ask customers. The two jobs meet at one point: an email that ends in “could you write us a testimonial?” hands the customer a blank page, and a blank page is what a chatbot is for. Every template below points at a form with specific questions instead, which is also why fluent, empty praise arrives in the first place.
Which template to send when
Match the template to the moment, not the mailing list. Blasting every customer with one generic request is the most reliable way to get silence.
| Situation | Best moment to send | Why that moment |
|---|---|---|
| Post-purchase | 3 to 14 days after delivery | The product has been used and the experience is fresh |
| Project wrap-up | Within a week of handoff | Goodwill and visible results peak together |
| SaaS milestone | The day a usage milestone lands | The product’s value is self-evident, no persuasion needed |
| Renewal | The day after renewal | Staying is proof they would recommend you |
| Coaching or consulting | At a visible client win | The before-and-after contrast is sharpest |
| Unprompted praise | Same day, as a reply | The testimonial already exists |
| Second nudge | 5 to 7 days after the first ask | Long enough not to pester, short enough to remember |
One mechanical choice runs through all seven: the ask resolves to a single link the customer clicks. Nothing to download, nothing to schedule, nothing to compose from scratch in a reply.
Post-purchase and project wrap-up templates
These two carry most small businesses. The post-purchase version works for products; the wrap-up version works for freelancers and agencies, where the ask belongs inside the closing ritual of the project itself.
Template 1: the post-purchase check-in
Subject: How is the [product] working out?
Hi [first name],
You picked up [product] about a week ago and I wanted to check in. Is it doing what you hoped?
If it is, would you share a few sentences about it? It takes about two minutes, and there's no account to create:
[your form link]
Words from real customers convince people far better than anything I could say about myself. And if something is off, just reply to this email. I read every answer.
Thanks either way,
[your name]Why this works: it reads as a check-in first and an ask second, and the escape hatch (“just reply”) routes unhappy customers into a conversation instead of a public quote.
Template 2: the project wrap-up
Subject: One last thing before we close out [project]
Hi [first name],
Now that [project] is wrapped and [concrete outcome, e.g. "the new site is live"], I have one small ask.
Would you write a few sentences about what it was like to work together? What the problem was, what changed, and whether you'd recommend it. Two minutes, one link:
[your form link]
A line from you helps the next [their role, e.g. "founder"] decide whether to trust me with something similar. Nothing gets published without your say-so.
Thanks for a great project,
[your name]Why this works: it lands at the goodwill peak and hands over a three-part outline, so the client never faces a blank page.
SaaS milestone and renewal templates
Software has an advantage here: the product tells you when the customer succeeded. A milestone crossed or a renewal processed is a stronger trigger than any date-based drip, because the email can point at something the customer just did.
Template 3: the milestone ask
Subject: You just hit [milestone] in [product]
Hi [first name],
I noticed your team just [milestone, e.g. "published your 100th report"]. That's exactly what we hoped people would do with [product].
Since it's clearly doing its job, would you tell us what it replaced or improved for you? A few honest sentences, about two minutes:
[your form link]
We read every submission, and nothing appears publicly unless you say it can.
Thanks for building with us,
[your name]Why this works: the milestone proves the value already happened, so the email asks at the exact moment the product’s usefulness needs no arguing.
Template 4: the renewal ask
Subject: Thanks for staying with us. One small ask
Hi [first name],
You renewed [product] this week, which is the best compliment a product can get. Thank you.
Can I ask for one more? Would you share why you stayed? What [product] handles for you, and what almost made you look elsewhere. Honest answers help the most:
[your form link]
Two minutes, no account needed, and you choose whether your words can be used publicly.
Appreciate you,
[your name]Why this works: renewal is revealed preference, and “why did you stay” surfaces the objection-handling quotes a pricing page actually needs.
The coaching ask and the reply to unprompted praise
Coaches and consultants sell transformation, so the email’s job is to make the client see their own before-and-after. The praise reply is different: the testimonial already exists, and you are only asking to keep it.
Template 5: the client transformation
Subject: Where you started vs. where you are now
Hi [first name],
When we started, you were [starting point, e.g. "posting once a month and dreading it"]. This week you [current state]. That contrast is worth writing down while it's fresh.
Would you put it in your own words? Where you were, what changed, and what you'd tell someone on the fence. One link, a couple of minutes:
[your form link]
It doubles as a record of your own progress, and nothing goes public without your approval.
Proud of the work you put in,
[your name]Why this works: the before-and-after frame writes the testimonial’s structure for the client, and transformation stories are the strongest proof this kind of work can show.
Template 6: the reply to unprompted praise
Subject: Re: [their original subject]
Hi [first name],
This made my week. Thank you for taking the time to write it.
Would you be open to me using it publicly? The easiest way: paste it into this short form, which also asks how you'd like to be credited and confirms you're okay with it being published:
[your form link]
Feel free to edit or expand it there. And if you'd rather keep it between us, that's completely fine too.
Thanks again,
[your name]Why this works: the words already exist, so you are only asking for permission and a byline, the lowest-friction ask on this page.
The polite second nudge
An unanswered ask usually died under a Tuesday inbox, not from objection. One reminder recovers a meaningful share, and naming it as the last one keeps the relationship intact.
Template 7: the second nudge
Subject: No pressure, promise
Hi [first name],
A quick nudge on my note from last week. If you have two minutes, I'd still love a few sentences about [product/project]:
[your form link]
If it's a no, or just a busy month, ignore this and we're square. This is the last time I'll ask.
Either way, thanks,
[your name]Why this works: stating the ceiling (“this is the last time I’ll ask”) removes the dread of a drip campaign and gives fence-sitters a reason to act now instead of later.
Where the link should point
Every template above stakes its two-minute promise on the link, so the link has to keep it. Point it at a short testimonial form, not a survey — the exact fields, and what each one builds, are in testimonial questions to ask customers. Collect by plain reply instead and you inherit a second job: going back to each person to ask whether you can actually publish what they wrote, which is the one email worth designing out.
If the person you have in mind is not an email relationship at all, the same ask rewritten for a LinkedIn DM or a text is in the testimonial request generator, which fills in the name, the project and the link for you.
The cleaner pattern is a form with the permission step built in, which is how Testymo forms work: the public-or-private choice is made inside the form and travels with the words, and the “can I publish this?” round-trip never happens. However you collect them, the replies then need a home on your site; the layout patterns in how to display testimonials cover what to do once the first few land.
Frequently asked questions
How long should a testimonial request email be?
Short enough to read without scrolling — none of the seven templates on this page reaches a hundred words. Length is a signal in itself: a long email implies a long task, which undercuts the two-minute promise the link has to keep.
Should the second nudge be a new email or a reply in the same thread?
A reply, so the original ask and its link sit directly below the nudge and nobody has to go hunting. Template 7 above is the shape it should take: shorter than the first email, the two minutes restated, the ceiling named out loud. When to send it, and when to stop, belongs to follow-up etiquette that isn’t nagging.
Should these emails come from a person or a shared inbox?
From a person, at an address a reply actually reaches. Several of these templates offer “just reply if something’s off” as the escape hatch, and that offer is worthless from a no-reply address. Sending through a tool is fine; the from-line and the reply path should still be human.
Is it okay to automate testimonial request emails?
Yes, when the trigger is an event rather than a date — a delivery, a milestone, a renewal — and the personal line is filled from something real in that customer’s record. An email that arrives at the right moment reads more personal than a hand-typed one sent at random. Automate the timing, never the specifics.
Should I paste an example testimonial into the email?
One short example helps, in the body rather than as an attachment, which only adds a download and a decision. Expect it to shape what comes back, though — people mirror the sample they are shown, so pick one that is specific rather than gushing.
What if the reply is a complaint instead of a testimonial?
Every email here asks for two things while naming only one: a testimonial, or the reason there isn’t one yet. The second is the more useful answer, and the reason each template keeps a “just reply” escape hatch. A customer who lands in your inbox instead of on a public form has told you what to fix, and fixing it is usually what makes a testimonial possible later.