Reviews & Testimonials

How to Ask for a Testimonial: Questions, Email Templates, and Consent

A repeatable testimonial request process covering timing, useful interview questions, editing permission, incentives, disclosure, and follow-up.

Reviewed by Social Proofs Standards Editor on Aug 6, 2026

Published Aug 4, 2026 / Updated Aug 6, 2026

Best momentAfter a meaningful outcome
Best requestSmall, specific, and optional
RecordResponse, consent, edits, disclosure

The easiest way to collect weak testimonials is to ask, "Would you say something nice about us?" It signals the desired sentiment and gives the customer no useful memory prompt. A better request follows a real outcome and asks about the customer's starting point, decision, experience, and result.

Choose a moment with evidence

Trigger the request after a task has been completed, an outcome has been observed, a support issue has been resolved, or the customer has voluntarily expressed useful feedback. Do not ask on first login or before the customer has had a fair chance to evaluate the experience.

SignalRequestDelay when
Project acceptedAsk about process and resultKey stakeholders have not reviewed the work
Milestone reachedAsk about the starting point and measured changeThe metric is still provisional
Positive support replyAsk about the service experienceThe underlying issue is not fully resolved
RenewalAsk why the customer continuedThe renewal happened automatically or under dispute

Seven questions that produce useful detail

  1. What were you trying to do? Establish the job and audience.
  2. What was difficult before? Capture the baseline without exaggeration.
  3. What alternatives did you consider? Reveal the decision criteria.
  4. What did you actually use or change? Tie the story to a real intervention.
  5. What happened next? Ask for observable outcomes and time frame.
  6. What did not change, or what still needs work? Preserve limits and credibility.
  7. Who would find this most useful? Help future readers judge fit.

Send two or three questions at a time, not all seven by default. For a written quote, the smallest useful request often asks about the prior situation, the change, and one outcome.

Email and in-product request templates

Email after a completed outcome
Subject: Could we document what changed?

Hi [Name], now that [specific milestone] is complete, would you be open to answering three short questions about the experience? Honest detail is more useful than praise, and you can approve the final wording, attribution, and where it appears before anything is published. No problem if the timing is not right.
Follow-up after positive feedback
Thank you for explaining what worked. May we adapt that feedback into a short website testimonial? We would send the exact quote and attribution for approval first. Please also tell us whether you prefer your full name, first name and role, company only, or anonymous attribution.
Short in-product prompt
Would you describe what you completed today? Your answer may be considered for a customer example only if you separately approve publication.
  • Explain the intended channels: website, sales material, ads, social posts, or email.
  • Show the final quote in context, not just an isolated sentence.
  • Confirm each identity asset separately, including photo and company logo.
  • Record any incentive, free product, employment, investment, or agency relationship.
  • Give the customer a practical route to request a correction or withdrawal.
  • Store the approval date and schedule a factual review.
Incentives require care

Current FTC guidance says an incentive must not be conditioned, expressly or implicitly, on a positive review. Material connections may also need clear disclosure. A neutral request for honest feedback is safer than "Tell us how much you loved it for a coupon."

For the display step, use the formats in our website testimonial examples. For a deeper outcome story, move to the customer case study template.

Sources

How this page was prepared

The workflow and templates are original. Compliance notes were checked against current FTC guidance on incentives, material connections, false reviews, and testimonial use.

AI-assisted tools supported research organization or drafting. A human editor checked the final page for accuracy, relevance, sourcing, and originality before publication.