Testimonial Request Template: How to Ask a User for a Quote They Will Actually Write

When is a user ready to be asked?

Right after something good happens to them, and not before. The moment is usually one of three. They tell you unprompted that the product saved them time. They finish the job the product exists for, and you can see it in your own records. Or they answer a feedback request with something warm and specific. In each case the feeling is fresh and the words are easy to find. A request sent three weeks later, to someone who has forgotten the detail, gets a polite “sure” and no reply.

Do not ask on the first day, before the person has had a result, and do not ask everyone at once. Ask the handful who showed you real value, such as the people you let in through a beta invite. If nobody has yet, you do not have testimonials to collect; you have a product to improve, and the feedback request templates are the better use of the week.

What makes a testimonial worth putting on a page?

• A specific before and after. “I used to spend Sunday evenings on this; now it takes ten minutes” persuades. “Great product, highly recommend” does not.
• A role or situation the reader recognises. “Freelance illustrator” does more than a first name alone, because the reader can see themselves.
• A detail only a real user would know. A named feature, a particular moment, a number they measured. Do not supply the number for them.
• Their voice. Typos and short sentences are fine. A quote that sounds like marketing copy loses trust.

The prompts in the templates below are designed to draw out those four things, because most people do not know what makes a testimonial useful and will write one line unless you give them a shape.

Template 1: after a user reports a win

Subject: Could I quote what you said about [product name]?

Hi [first name],

Your note about [the specific thing they said or did] made my day. Would you be willing to turn it into a short quote I could put on the [product name] site?

If it helps, here are three prompts. Answer any you like, in your own words:
- What were you doing before you found [product name]?
- What changed once you started using it?
- Who would you tell about it, and what would you say?

A sentence or two is plenty. I'll send you exactly how it would look, with your name and role or without them, before anything goes up. And you can say no, no hard feelings.

Thank you,
[Your name]

Template 2: asking permission to use words they already wrote

Sometimes the best testimonial is already sitting in a comment, an email or a post. Do not copy it onto your page without asking, even if it was written in public. Ask, show them the exact words, and say how they will be shown.

Subject: Can I use your comment about [product name]?

Hi [first name],

You wrote this on [where and when]:

"[exact quote, unedited]"

May I use it on the [product name] website [and in launch posts]? I'd show it as: "[Name, role]" [or: "[first name and initial]" or: anonymous, your call].

If you'd prefer I change a word or leave it out, tell me and I will. I won't use it until you say yes.

Thanks again for taking the time to write it.
[Your name]

If the original was a comment on your launch page, remember that the person wrote it in a thread, not in a request for an endorsement. Asking first respects that, and it keeps the quote accurate.

Template 3: inviting a user to a short case-study call

A fifteen-minute call can produce a better quote than any form, and gives you a story for later. Offer to do the writing, but let them approve the result.

Subject: Fifteen minutes about how you use [product name]?

Hi [first name],

I've noticed you've [specific usage pattern, such as run it every Monday since March], which is exactly the kind of use I'd like other people to understand. Could we talk for fifteen minutes about how it fits into your work?

I'd ask what the job looked like before, what it looks like now, and what almost stopped you. I'd write it up in a few short paragraphs and send it to you to correct or reject before it appears anywhere.

If that is more than you'd like to do, a two-line quote works just as well. Your call.

[Your name]

What rules keep testimonials honest?

1. Only publish words a real user agreed to, in the form they agreed to. Light edits for length are fine if the meaning is unchanged and they approve.
2. Never write a testimonial and attribute it to a person who did not write or approve it. Never invent a user, a company or a photo.
3. Say if you gave anything in exchange, such as free access, whenever it could affect how the quote reads. Regulators in several countries, including the US Federal Trade Commission, expect endorsements to be genuine and incentives disclosed. This is general information, not legal advice.
4. Ask before showing a name, a photo or an employer’s name. Many people are happy to be quoted but not to be identified at their company.
5. Date the page, and remove a quote if the person asks or the product changed enough that it no longer applies.

Where do testimonials go once you have them?

Put the strongest one next to the main call to action on your landing page and the rest lower down, near the pricing or sign-up step where a visitor is deciding. Reuse the best line in your launch posts, but keep it attributed. The landing page launch checklist covers where they sit on a page, and launch your product free here if you want a public page where early users can say what they think in a comment. Browsing the board’s productivity ideas is a good way to see what problems early users describe in their own words.