Examples before they write
Show Example Testimonials in Your Form
A blank box makes people freeze, so it is tempting to show them a finished testimonial to copy. The risk is that they do copy it: the same opening, the same adjectives, the same length, twenty times over. Answer five questions about your customers and your request to see whether an example will help or hurt.
- Whether to show an example at all
- Which kind: a full sample, a shape or prompts
- How to stop replies sounding identical
Decision helper
Should your request show an example answer?
Answer for one request you are about to send, to one kind of customer.
Answers stay in your browser.
The problem, solved
Where examples go wrong, and how StoryProof keeps answers their own
- Problem 1
Every reply starts with our example
You showed one sample and now half the library opens with “I was struggling to find a solution until…”. Side by side on a wall, it looks staged.
How StoryProof solves it
From Pro, a multi-step form asks several questions in one sitting, so you can replace the sample with short prompts answered one at a time.
- Problem 2
People read the example aloud on video
Give someone a script and they read it, stiffly. A video of a customer reciting your sample is worse than no video.
How StoryProof solves it
The same collection link takes a video, an audio note or written text in the browser, so give speakers a question to answer rather than words to say.
- Problem 3
A copied answer slipped onto the site
A customer pasted most of the example and changed one word. It is not their experience, and it should not be published as if it were.
How StoryProof solves it
Nothing a customer submits goes public until you approve it, so you can catch near copies and ask that customer for their own version.
- Problem 4
Our customers write in other languages
An English sample pushes non-native writers to translate it word for word, which flattens what they meant.
How StoryProof solves it
Collection forms are available in several languages on every plan, so customers can answer the prompts in the language they think in.
- Problem 5
We cannot tell if the example helped
You changed the request and the answers changed, but nobody recorded which replies came from which version.
How StoryProof solves it
Tags are on every plan. Tag replies by the request version they answered, then compare the two groups before deciding which to keep.
A sample to copy versus a shape to follow
Sample answer (gets copied)
- “Example: Working with this team was a game changer. I was struggling until I found them, and now I could not be happier. Highly recommend!”
- Customers lift whole phrases from it
- Every reply comes out the same length and tone
- Video speakers read it out word for word
Shape and prompts (gets stories)
- Two or three sentences is plenty
- What were you trying to fix when you found us?
- What is different now, in a normal week?
- Who would you tell about us, and why?
In StoryProof
Set up the request the helper recommends
- 1
Write the prompts or the outline first
Whatever the verdict, start with the question. An example is only ever a support for a good question, never a substitute for one.
- 2
Split long asks into steps
From Pro, put each prompt on its own step of a multi-step form so the customer answers one small question at a time.
- 3
If you use a sample, put it in your request email
The email that carries the collection link is text you write in full. Mark the sample clearly, keep it short and make it about a different situation from the reader’s.
- 4
Read for echoes before approving
When you review submissions, look for phrases lifted from your example. Ask those customers, kindly, for the same thing in their own words.
What happens next: Look at the first ten replies side by side. If they sound alike, remove the sample and switch to prompts.
Before you start
What this choice will not do
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
No sample is neutral
Even a shape nudges length and order. That is acceptable; borrowed adjectives and claims are not.
- 02
Never put a result in the example
A sample that says “saved us 10 hours a week” invites customers to repeat a number they never measured.
- 03
This page does not describe a sample field
It does not claim the StoryProof form has a dedicated place for an example answer. The request email, which you write, always does.
- 04
Prompts cannot fix a weak relationship
If customers are not keen to vouch for you, no example or prompt will produce a convincing testimonial.
FAQ
Questions people ask
Short answers to what usually comes up next.
Do example testimonials make customers more likely to reply?
They can help people who freeze at a blank page. The cost is sameness: replies drift toward the example. Prompts usually get you the help without the copying.
Is it fine to publish a testimonial that closely follows my example?
Only if it truly reflects that customer’s experience. If it is mostly your words with their name on it, ask them to say it their own way first.
Should I show real testimonials from other customers as examples?
Be careful. It shares someone’s words in a place they did not agree to, and it anchors new replies just as much as a made-up sample does.
What about video testimonials?
Give questions, not scripts. People speak naturally when answering a question and stiffly when reading.
Still have a question? Ask the StoryProof team or book a demo.
Ask good questions, get answers in their words
Build a request that guides customers without handing them a script, and approve every reply before it goes live.
Last updated 2026-11-07.