“Can I see it before it goes up?”
Customers Who Want Final Version Approval
Some customers say yes to a testimonial on one condition: they see the final version first. That is a reasonable ask, and handled well it builds trust. Nothing in StoryProof goes public until you approve it, so the testimonial can wait safely while the customer looks. The preview email below shows them the exact words, how their name appears and where it will run, and the routine covers what to do when they want a change.
- The exact words, name and placement
- A clear way to ask for changes
- Publish only after a yes
The problem, solved
Where final approval goes wrong
It went live before they replied
A teammate saw a great testimonial in the library and put it on the homepage while the preview was still out.
With StoryProof: Nothing a customer submits goes public until you approve it, so leave it unapproved until the customer says yes.
Nobody knows which ones await sign off
Three previews are out with three customers and the team has lost track of who answered.
With StoryProof: Tag each one as waiting for the customer and filter by that tag before anything is approved.
They want one sentence changed
Rewording their testimonial yourself after they asked would undo the point of the preview.
With StoryProof: Ask them to send the version they are happy with through your collection link, by text, audio or video, and approve that one instead.
They are fine with the quote, not the surname
Approval often hinges on how they are named, not on the words.
With StoryProof: On testimonial images, from Pro, show them as first name and initial or first name only, with initials instead of a photo.
They ask exactly where it will appear
Saying “on our website” is too vague for someone who asked to see the final version.
With StoryProof: You choose which approved testimonials appear in each widget, so you can name the pages before you publish.
They want their video shortened
A trimmed clip is a different final version from the one they recorded.
With StoryProof: Cut the video in an editor outside StoryProof, send them the cut to watch, then upload the finished file once they agree.
Flip the switch to see how StoryProof handles each one.
Preview emails
Send the customer a final version preview
Fill in the details. Paste the text exactly as visitors will read it, so the thing they approve is the thing that runs.
- The preview
Subject: Your testimonial, before it goes live
Hi [Daniel], As promised, here is exactly how your testimonial will appear before anything goes live: "[Setup took one afternoon and support answered every question the same day.]" [Daniel R., Operations Lead] We plan to show it on [our pricing page and homepage]. If it all looks right, a quick “yes, go ahead” is all I need. If you would like anything changed, tell me what and I will send you a link to submit the version you prefer. Nothing goes up until you say so. Thanks, [Maya]
- When they ask for a change
Send your collection link so the words that run are the words they submitted.
Subject: Re: Your testimonial, before it goes live
Thanks [Daniel], that is an easy fix. So the final wording is yours, could you submit it here in your own words? [collection link] As soon as it comes through I will send you one last look, and it will only appear on [our pricing page and homepage] after that. [Maya]
- Confirming the yes
Subject: Re: Your testimonial, before it goes live
Thank you [Daniel]. Your testimonial will go up on [our pricing page and homepage] this week, shown as [Daniel R., Operations Lead]. If you ever want it changed or taken down, just reply to this email. [Maya]
- One gentle nudge
Send once, a week after the preview. If there is still no answer, do not publish.
Subject: Quick check on your testimonial
Hi [Daniel], just making sure my last email reached you. Your testimonial is ready and waiting for your yes, and I will not publish it without one. No rush at all. [Maya]
What you type fills these templates in this browser tab only. Nothing is saved or sent.
In StoryProof
Run the preview in StoryProof
- You will need
- The testimonial in your StoryProof library, not yet approved
- The pages or widgets where you plan to show it
- Your collection link
- 1
Tag it as waiting for the customer
Leave it unapproved and add a tag your team knows means “customer preview out”.
- 2
Send the preview
Use the preview email above with the exact text, name display and the widgets you plan to add it to.
- 3
Handle changes with a fresh submission
If they want different wording, they submit again through your collection link and the new version is the one you approve.
- 4
Approve on a clear yes
Approve it, remove the waiting tag, add it to the widgets you named, and keep their reply in your records.
What happens next: Send the customer a link to the live page once it is up. Seeing their words where you said they would be closes the loop.
Before you start
What StoryProof does not do here
No customer approval button
StoryProof is not described as sending previews or collecting a customer’s sign off. The preview is an email you send, and the yes is their reply.
No editing their words in the app
StoryProof is not described as editing what a customer wrote. Changes come back as a fresh submission from the customer.
Video edits happen elsewhere
There is no trimming inside StoryProof. Edit the file in your own editor and upload the finished version.
Silence is not a yes
If the customer asked to approve the final version and never replied, leave it unpublished. That is your policy to keep, not a setting.
FAQ
Questions people ask
Short answers to what usually comes up next.
Do I have to show every customer the final version?
No, but if someone asked to see it, do. Promising a preview and skipping it is how a happy customer becomes an unhappy one.
What should the preview include?
The exact text as it will appear, how their name and title will show, and where it will run. Anything less leaves room for surprise.
What if I spot a typo in their testimonial?
Mention it in the preview. StoryProof is not a text editor for submissions, so if they want it corrected, they resubmit with the fix through your collection link.
What if they never reply?
Send one nudge after a week. If there is still nothing, do not publish. Keep it unapproved and try again in a few months if it matters.
Do they need to approve it again for a new page?
If you named specific pages in the preview, ask before adding it somewhere quite different, such as an ad or a printed brochure.
Still have a question? Ask the StoryProof team or book a demo.
Hold it until they say yes
Testimonials stay private until you approve them, so a customer preview never races your website.
Last updated 2026-11-20.