The reason your testimonial requests go unanswered is almost never that the customer dislikes you. It is that you asked them to do too much. "Would you mind writing us a testimonial?" lands in a busy inbox as a small, open-ended writing assignment with no deadline and no format — exactly the kind of task that gets postponed forever. The customer is not saying no. They are saying "later," and later never comes.
The email that actually works does the opposite: it removes nearly all the effort from the customer's side and leaves them with a yes-or-no decision instead of a writing project. This guide walks through that email line by line — the timing that makes it land, the single specific ask, the draft you write for them, and the close that gets a reply this week instead of next quarter. Templates are at the end.
Time the ask to the moment of value
The single biggest predictor of whether you get a testimonial is when you ask. Send the request at the moment the customer has just felt the value, and the reply rate climbs dramatically. Send it cold, months after the last interaction, and you are asking someone to reconstruct a feeling they have moved on from.
The high-value moments are specific and they are easy to spot if you are watching for them: right after a customer hits a result milestone, just after they renew or upgrade, the moment they send you unprompted praise, or immediately following a support interaction that went well. A customer who just emailed "this saved us hours this week" has handed you the ask on a plate — that compliment is a testimonial waiting to be formalized. (We cover that exact move in how to turn a one-line compliment into a usable testimonial.) The worst time is "whenever we remember to do outreach," because that timing is disconnected from any moment the customer actually felt something.
Open by reminding them of the result, not by asking
The first two sentences should not contain the ask. They should remind the customer of the specific value they got, because that is what makes them willing to spend two minutes helping you. Lead with the outcome:
"Hi Jenna — I saw your team hit 500 published proofs last week, which is fantastic. Onboarding three new clients in a month is no small thing."
This does two jobs. It shows you are paying attention to their success rather than just hunting for marketing material, and it pre-loads the exact result that makes a strong testimonial. By the time the customer reads your ask, the proof is already in their head — you have reminded them why they would say yes before you asked the question.
Make one specific ask, not an open-ended one
Here is the line that separates effective requests from ignored ones. Do not write "would you be willing to give us a testimonial?" Write a request scoped so tightly that answering is nearly automatic:
"Would you be open to a two-sentence quote we could use on our site? I can even draft it based on what you've told me, so all you'd have to do is tweak and approve it."
Notice what this does. It names the format (two sentences), names the use (on our site), and — critically — offers to write the draft. The effort you are asking for has shrunk from "compose a testimonial" to "approve or edit one." That is the whole game. A request the customer can satisfy in thirty seconds gets answered; a request that requires them to open a blank document does not.
Write the draft for them
Including a draft is the highest-leverage thing in the entire email, and most people skip it because it feels presumptuous. It is not. You are not putting words in their mouth — you are giving them a starting point they are free to change, and you are removing the blank-page problem entirely. Base the draft on something they actually said or a result you can see:
"Here's a starting point, but please change anything that doesn't sound like you:
'ProofShow cut our testimonial collection from a two-week chase to a single afternoon. We onboarded three clients last month and had social proof live before the kickoff calls.'"
Customers almost always lightly edit the draft and send it back, because editing is easy and writing is hard. A draft built around a numeric, quantified result is best of all — it gives you the most persuasive kind of testimonial while asking the customer for the least work. And if their reply praises something you no longer offer, our guide on what to do when a testimonial praises a removed or renamed feature covers editing it without losing the customer's voice.
Handle permission and attribution up front
Address the two things that make customers hesitate before they have to ask: where it will appear and how they will be credited. Say it plainly:
"We'd use it on our homepage with your name, title, and company logo — but if you'd prefer first name only or no logo, just say the word."
Naming the attribution options up front removes the friction of the customer wondering whether agreeing means exposing more than they want. Offering the lighter-touch option (first name only) signals you respect their boundaries, which paradoxically makes them more willing to give you the full attribution. If a customer can't use their name at all, that is a solvable problem, not a dead end.
Close with an easy yes and a soft deadline
End by shrinking the decision and adding gentle time pressure. Do not close with "let me know your thoughts" — that is another open loop. Close with a binary:
"If you're open to it, just reply 'looks good' or send back your edits, and I'll take it from there. Hoping to update the site by the end of next week — no pressure if the timing's bad."
A soft deadline ("end of next week") gives the email a reason to be answered now instead of filed away, while "no pressure if the timing's bad" keeps it from feeling like a demand. The reply you want — "looks good" or a quick edit — is one tap away.
The full template
Putting it together:
Subject: Quick favor — two-line quote?
Hi Jenna — I saw your team hit 500 published proofs last week, which is fantastic. Onboarding three new clients in a month is no small thing.
Would you be open to a two-sentence quote we could use on our site? I can even draft it based on what you've told me, so all you'd have to do is tweak and approve.
Here's a starting point — please change anything that doesn't sound like you:
"ProofShow cut our testimonial collection from a two-week chase to a single afternoon. We onboarded three clients last month and had social proof live before the kickoff calls."
We'd use it on our homepage with your name, title, and company logo — but first name only or no logo is totally fine if you'd prefer.
If you're open to it, just reply "looks good" or send back your edits, and I'll handle the rest. Hoping to update the site by the end of next week — no pressure if the timing's off.
Thanks either way, [Your name]
Why this version works
Every line is built to remove a reason to delay. The timing catches the customer when the value is fresh. The opening reminds them of the result before asking. The ask is scoped to thirty seconds of effort. The draft solves the blank page. The attribution note removes the hesitation about exposure. The close turns a writing project into a one-word reply. You are not asking the customer to do you a favor that costs them an afternoon — you are asking them to approve something you have already done. That is the difference between a request that gets ignored and one that gets a "looks good" the same day.