You email a happy customer asking for a testimonial. A week later you get back: "Great product, the team is fantastic, highly recommend!" It is warm, it is genuine, and it is completely useless. It says nothing a prospect could not guess, it names no result, and it could have been written about any company in your category. So you send a follow-up asking for specifics, the customer — who already did you a favor once — goes quiet, and the quote dies in your drafts.
The problem is almost never the customer. The problem is the request. A vague ask gets a vague answer, because the customer does not actually know what makes a testimonial useful, and "can you write us a testimonial?" hands them a blank page with no instructions. The fix is to write the request so that answering it honestly produces a specific, publishable quote. This is a writing problem on your end, not a willingness problem on theirs.
Why "can you write us a testimonial?" fails
When you ask someone for "a testimonial," you are asking them to do three hard jobs at once: figure out what you want, decide what to say, and write it well. Most people are bad at all three when handed a blank prompt, not because they are inarticulate but because they have no idea what a good testimonial looks like or what would actually help you.
So they fall back on the genre they have seen most: the back-of-the-book blurb. "Fantastic product, wonderful team, highly recommend." It is the testimonial equivalent of "thanks for everything" in a greeting card — sincere, generic, and empty. They are not withholding the good stuff; they genuinely think this is what you wanted, because the request did not tell them otherwise.
The deeper issue is that a blank ask invites opinion ("it's great") when what converts prospects is evidence ("it cut our onboarding time from two weeks to two days"). Opinion is cheap and interchangeable; specific evidence is credible and unique. Your request has to steer the customer from the first to the second, and a vague ask does the opposite.
Replace the open question with specific ones
The single highest-leverage change is to stop asking for "a testimonial" and start asking a few specific questions the customer can answer from memory. You are not writing the quote for them — you are giving them the right things to talk about.
Good questions share a shape: they ask about a concrete before, a concrete after, and the gap between them. For example:
- What were you using or doing before, and what was frustrating about it?
- What changed after you started using us — ideally something you can put a number or a timeframe on?
- Was there a specific moment you realized it was working?
- What would you say to someone on the fence about trying us?
Notice that none of these ask "is our product good?" They ask the customer to narrate, and narration produces specifics automatically. "We used to reconcile invoices by hand every Friday and it took the whole afternoon; now it runs overnight and I check it in ten minutes" is a far better quote than anything that starts with "great product" — and the customer produced it without trying, just by answering "what changed?"
This is the same principle behind a well-built testimonial request email template: the structure of the ask does the heavy lifting, so the customer only has to be honest, not clever.
Offer a draft they can edit — but get permission first
A powerful and underused move is to write a draft for the customer based on something they already said — a support ticket, a sales call comment, a Slack message — and ask them to edit and approve it. This drops their effort from "compose something" to "fix what's wrong," which almost everyone will do.
There is one rule that makes this ethical rather than sketchy: the words you draft must come from things the customer actually said or clearly believes, and they must have full freedom to change anything. You are transcribing and tightening, not inventing. If you have a real quote from a call — "honestly this saved our Q3" — building the testimonial around that and asking "did I capture this right? edit anything that feels off" is legitimate and kind. Putting words in their mouth they never said is not, and the techniques for doing this honestly are worth getting right because the credibility cost of a fabricated-sounding quote is severe.
For customers who are willing but freeze at a blank page, this draft-and-approve path is often the difference between a published quote and a dead thread. Many of the reluctant ones are not unwilling — they are just busy and bad at writing, which is exactly the friction covered in how to ask for a testimonial without being awkward.
Make the specifics easy by reminding them of the specifics
Customers forget the before. By the time they are happy enough to give a testimonial, the old pain has faded and they cannot remember how bad it was — which is exactly why their unprompted quote skips the contrast that makes testimonials persuasive.
You often have the receipts they have forgotten. If a customer told your support team "this used to take us all day" during onboarding, quote that back to them: "When we started, you mentioned reconciliation was eating a full day a week — is that a fair before-and-after to mention?" You are not feeding them a result; you are reminding them of one they lived, so the specific that makes the quote land comes from their actual experience rather than a blank-page guess.
Ask for attribution at the same time
A quote with no name, title, and company is weak proof; a prospect cannot tell whether it came from a real buyer like them or from your marketing team. Yet teams routinely get the quote and then have to go back a second time to ask "can we use your name and title?" — a second favor that often stalls.
Bundle it into the original request. Tell the customer up front where it will appear and exactly how you will attribute it: "We'd love to feature this on our homepage as 'Maria Chen, Head of Finance at Northwind' — is that the right name and title to use?" Settling attribution in the same message you settle the quote means you finish in one round, and the level of attribution detail you ask for matters too, because attributing a testimonial to a specific feature or use case versus a generic product mention changes how much a prospect trusts it.
A request template that works
Putting it together, a request that reliably returns a usable quote looks roughly like this:
Hi Maria — you mentioned a few weeks ago that reconciliation used to eat a full afternoon every week and now runs overnight. That stuck with me, and I'd love to feature it as a short testimonial. You don't have to write anything from scratch — could you tell me, in a sentence or two: what was the before, and what's the after now? If it's easier, I'm happy to draft something from what you've already told me and send it over for you to edit and approve. We'd attribute it as "Maria Chen, Head of Finance at Northwind" on our homepage — let me know if that's right or if you'd prefer something else.
Every element earns its place: it reminds her of a specific before she has forgotten, asks for a before-and-after rather than an opinion, offers the draft-and-approve escape hatch, and settles attribution in the same breath. The customer can reply in two minutes and you walk away with a publishable quote on the first round.
The bottom line
A testimonial request is not a polite gesture you fire off and hope; it is a piece of writing that determines the quality of what comes back. Ask for "a testimonial" and you get a blurb. Ask specific before-and-after questions, remind the customer of the pain they have forgotten, offer to draft from their own words, and settle attribution up front, and you get a quote that names a real result, sounds like a real person, and is ready to publish without a second round. The customer was always willing to help — the only question is whether your request made it easy for them to help well.