The best time to ask for a testimonial is right after a customer has had a good outcome, not on a schedule. Ask about the problem you solved rather than about your product, keep the ask short, get permission in writing, and place the answer next to the objection it answers rather than on a page nobody reads.
This is not about deciding what to build next. For gathering feedback to shape a product, see how to collect feedback from customers. This is about collecting praise you already earned, from people who already got the result, so other buyers can see it before they decide.
This page is one part of a larger guide. For the whole subject in one place, see feature request tools.
When is the right moment to ask?
Timing is the decision that settles everything else. Ask when someone has just had a good outcome: a ticket resolved, a migration finished, a deadline hit because the product held up. Whatever they say will be specific, because the win is still in front of them.
A scheduled quarterly outreach email misses that window. It catches people at a random moment, weeks or months after whatever went well, when the detail has faded into a vague "yeah, it's fine". If you only ever ask on a schedule, you will only ever get vague answers back. Attach the ask to the moment instead, right after a support ticket closes, right after onboarding finishes, right after a renewal.
How do you ask for more than "great product"?
Ask about the problem, not about the product. "What were you dealing with before, and what changed?" pulls out a specific before-and-after. "How would you rate us out of five?" pulls out a number and nothing else. The question decides the quality of the answer more than anything else in the process.
Keep the ask to a sentence, not a form with four fields. A short request gets answered on the spot; a long one gets marked to do later and never returns. Make it easy to decline, too: a polite no costs you nothing, and a testimonial someone felt cornered into giving reads as hollow as no testimonial at all.
Get permission in writing, and get it for more than the quote. Separately confirm you can use their name, their role, their company, and a photograph if you have one, because those details are what make a testimonial credible, and each one needs its own yes. A quote you have to pull down later because you never actually cleared it is worse than a quote you never collected.
What do you do with praise that arrives unprompted?
Most of the testimonials worth having already exist. They are sitting in a support thread where a customer said thanks in passing, in a reply that closed out a bug report with "brilliant, that's exactly it", in a cancellation survey where someone who is still leaving says something generous on the way out. Almost nobody goes back and reads their own closed tickets looking for this.
That is a mistake, because unprompted praise carries the least persuasion behind it and reads as the most credible for exactly that reason. Nobody was fishing for a quote when it was written. Search your closed conversations for the sentence someone wrote because they meant it, then go back and ask permission to use it. The words already exist; the only step left is consent.
Where should a testimonial actually go?
A testimonial placed next to the objection it answers does real work. A wall of quotes on a dedicated testimonials page does much less, because a reader arrives at that page with no specific doubt in mind, skims six similar-sounding lines, and moves on having absorbed almost none of them.
Match the quote to the hesitation a reader has at that exact point in the page, and put it there instead.
| Objection | Testimonial that answers it | Where it belongs |
|---|---|---|
| Will this actually get set up? | Someone describing how quickly they were running | Near the sign-up or install step |
| Is this worth the price? | A specific before-and-after, not a star rating | Next to the pricing table |
| Will support actually reply? | A quote describing a real response, with detail | Near the support or contact section |
| Is this still being worked on? | A quote mentioning a recent fix or release | Near the changelog or roadmap link |
| How is this different from what we use now? | A quote naming what they moved away from | Near a comparison or feature list |
What makes a testimonial credible?
This is the most important thing on the page, and the easiest thing to get wrong. An unattributed testimonial, a quote with no name, no role, no company attached, is worth close to nothing. Readers already treat marketing quotes with default scepticism, and an anonymous one reads as invented whether it was or not.
A fabricated testimonial is worse than a weak one. It is a real risk to trust once discovered, and it is also the reader's business, not just yours, to check what the rules on endorsements and reviews say where you operate. In the UK they sit in Part 4 of the Digital Markets, Competition and Consumers Act 2024, and the CMA publishes its own guidance, including specific guidance on fake reviews. Those rules are real, they vary by place, and this is not the page to summarise them: check with your own advisers before you publish a quote you did not actually collect.
The rule that avoids all of it is short. If you cannot attach the quote to a real, named person who agreed to it, it does not go on the page.
It is also worth seeing what specific looks like next to what does not. "Great tool, highly recommend" could have been written by anyone about anything, and answers no objection at all. Something closer to "we used to lose feature requests in a group chat, now they sit in one place with a vote count" reads as ordinary, even a little flat, but a reader can picture the exact thing that changed. A specific, mediocre-sounding line usually does more work than a superlative one, because it is the kind of thing a real person actually says.
One payment, no subscription, unlimited products.
What do you do when you have none yet?
Most people reading this have no testimonials at all yet. Say so, plainly, rather than inventing any to fill the gap. A testimonials section with three suspiciously polished quotes and no names, roles or companies attached reads as manufactured, even on the rare occasion it happens to be genuine, and that is a worse impression than an honest gap.
Use what you already have instead. Usage numbers you can stand behind without exaggeration, a public roadmap that shows what is actually being worked on, a changelog with a real, dated history of shipping: none of those needs anyone's permission, and all three answer roughly the same question a testimonial answers, which is whether this is real and whether it is going anywhere. See public roadmaps and changelogs and release notes for how to build each one. A testimonials section that sits next to a roadmap and a changelog rather than off on its own, which is how Docket's free edition handles it, is a shortcut to that pairing without building the layout yourself.
Frequently asked questions
When should you ask a customer for a testimonial?
Right after they have had a good outcome: a support ticket closed, a migration finished, a deadline hit because the product worked as expected. Asking on a fixed schedule instead usually catches people once the detail has faded, and you get a vaguer answer back for it.
How do you get a specific quote instead of "great product, highly recommend"?
Ask about the problem rather than about the product itself. A question like "what were you dealing with before, and what changed?" pulls out a specific before-and-after. A question like "how would you rate us?" pulls out a number and nothing else.
Can you use something a customer already said in a support conversation without asking again?
No. Get their permission before you publish it, even though the words already exist. Permission to use a quote publicly, and to attach a name, role, company or photo to it, is a separate thing from whatever they were doing when they wrote it, and each needs its own clear yes.
Is it ever acceptable to write a testimonial yourself and attribute it to a made-up customer?
No. It is a real risk to the trust your site depends on, and separately a question of what the rules on endorsements and reviews allow where you operate, which is worth checking with your own advisers rather than guessing. If a quote cannot be attached to a real person who agreed to it, leave the space empty rather than fill it.
What should you show on your site if you do not have any testimonials yet?
Say so rather than inventing one. Usage numbers you can honestly stand behind, a public roadmap, and a changelog with a real history all answer a version of the same question a testimonial answers, which is whether the product is real and still being worked on.