You have a great testimonial. Maybe you drafted it from a call, tightened a rambling email, or lifted a line from a Slack message and cleaned it up. Now you are hovering over "publish," and a question stops you: should the customer see this first?
It feels like the polite thing to do. It also feels dangerous. Send it back and the customer might strip out the specific number that made it persuasive, disappear for three weeks, or open a revision loop that never closes. Skip the preview and you risk publishing words they feel they never quite said — the fastest way to turn a happy customer into an annoyed one. The right answer isn't "always" or "never." It depends on how much of the quote is theirs versus yours, and on how much legal or reputational weight the testimonial carries.
The default: yes, but frame it as a confirmation, not an invitation to rewrite
For most testimonials, a quick preview is worth it. It does three things at once: it protects you legally (the customer has seen and approved the exact words attributed to them), it protects the relationship (nobody is surprised to find their name on your homepage), and it often improves the quote, because the customer catches a title that is out of date or a claim they'd rather soften.
The mistake is how people ask. "Here's a draft — let me know your thoughts!" is an open invitation to redesign the quote, and customers will take it. Instead, send it as a near-final confirmation:
"We'd love to feature this on our site — here's exactly how it would appear, with your name and title. Does this look accurate to you? Happy to adjust anything that doesn't feel right."
You are asking one question: is this accurate? Not how would you write this? That framing is the difference between a one-line "Looks great, go ahead" and a rewrite that sands off every edge. This is the same principle behind asking for a testimonial in a way that gets a reply: the easier you make the yes, the faster it comes.
When a preview is non-negotiable
Some testimonials should never go live without explicit sign-off:
- You wrote most of it. If you drafted the quote from a conversation rather than quoting the customer's own written words, they must approve it. Publishing words someone didn't write and hasn't seen is a real credibility and legal exposure — and if a prospect ever asks the customer "did you actually say that?", the answer needs to be yes. See how to turn a customer conversation into a testimonial for doing this cleanly.
- It names a person, a metric, or a competitor. Anything that could be checked, disputed, or held against the customer internally needs their eyes on it first.
- The customer is in a regulated industry, is public, or has a legal team. Here the preview isn't a courtesy; it's a requirement. Route it the way their compliance process expects, and build in time.
- You changed the meaning while editing. Tightening grammar is fine. If your edit made the claim stronger than what they actually said, that's no longer their testimonial — it's yours with their name on it.
When a preview can quietly hurt you
There is a real cost to the approval step, and it's worth naming honestly.
It can dilute the quote. Given a second look, customers often retreat to safer, blander language. The vivid "cut our onboarding from three weeks to four days" becomes "helped us onboard faster." You can protect against this by making it clear the specifics are why you love it: "The detail about going from three weeks to four days is exactly what makes this so helpful — is that number still accurate?" You're inviting them to confirm the specific, not delete it.
It can stall forever. A preview turns a done testimonial into an open task on someone else's plate — and other people's plates are full. Two guards against this:
- Give a soft deadline and a default. "We're refreshing the site next week — if this looks right, no need to reply; just let me know if anything's off." A no-reply default only works when the customer clearly wrote or already approved the substance; don't use it for words you drafted for them.
- Send the final artifact, not a decision. Show them the rendered testimonial card as it will actually appear, not a paragraph in an email body. People approve a thing that looks finished far faster than a draft that looks like homework.
It can invite scope creep. One customer asks to change their title, another wants a different photo, a third wants to see the whole page. Keep the scope of the ask narrow and visual, and most of this evaporates.
The practical middle path
For everyday testimonials — a customer's own written words, lightly edited, no sensitive claims — a quick "here's how this will look, all good?" is the right call. It costs you a day and buys you a clean conscience and a paper trail.
For quotes you authored, or anything with numbers, names, or legal weight, treat approval as a hard gate, not an option. And in every case, remember that the goal of the preview is confirmation of accuracy, not co-authorship. Send something that looks finished, ask one clear question, give them an easy way to say yes, and set a default so silence doesn't trap the quote in limbo.
Done right, the preview is not a risk to manage — it's the step that lets you publish with confidence that the customer will still be happy to see their words the day a prospect asks them about it. For the collection step that feeds this, see how to write a testimonial request email that actually gets a reply.