One submission, zero readers
Testimonials in a Language Nobody Speaks
A five star testimonial arrives and nobody on the team can read a word of it. Machine translation gives you a rough idea, but a rough idea is not enough to put on your website under a customer’s name: idioms flip, sarcasm vanishes and a complaint can read like praise. StoryProof keeps the submission private until someone approves it, which gives you time to find out what it actually says. This page is the check you run before that approval.
- Hold it while you check
- Confirm meaning with a person, not only a tool
- Decide where, if anywhere, it should run
The problem, solved
The risks in a testimonial nobody can read
Situation 1 of 5
Someone might approve it on stars alone
Five stars and a long paragraph look like praise, so it is tempting to publish and move on.
How StoryProof solves it
Nothing a customer submits goes public until you approve it, so the testimonial can wait unapproved while you check.
Situation 2 of 5
Our auto-approval might let it through
A rule that approves high ratings with text cannot tell whether anyone understood the text.
How StoryProof solves it
From Pro, auto-approval acts on 4 and 5 star testimonials with text, so check what it approved, or switch it off if stray languages are common.
Situation 3 of 5
It gets lost at the bottom of the queue
Things nobody can act on drift, and months later the customer wonders why their words never appeared.
How StoryProof solves it
Tag it with the language and “meaning check”, and filter by that tag at each review so it stays visible.
Situation 4 of 5
Machine translation might be wrong
Slang, irony and local idioms are exactly what automatic tools get wrong, and they are common in heartfelt reviews.
How StoryProof solves it
Ask the customer to confirm the meaning. If they offer to say it again in a language you read, they can submit through the same collection link.
Situation 5 of 5
The fluent reader cannot see it
A freelancer or a colleague in another office could check it, but you do not want them in the whole workspace.
How StoryProof solves it
Roles and permissions give each person only the parts of the workspace they need, on every plan.
Meaning check
Before you approve a testimonial nobody can read
Work through it for the one submission in front of you. If the same language keeps arriving, you need a standing reviewer instead.
Ticks stay in this browser tab. Nothing is saved or sent.
Ways to confirm the meaning
Pick by how much the testimonial matters and how quickly you need it.
In StoryProof
Handle it in StoryProof
- 1
Tag it and leave it unapproved
Add the language and a meaning check tag so it stays in view at every review.
- 2
Ask the customer or a reader
Email the customer to confirm what they meant, or give a fluent reader a role limited to what they need.
- 3
Take a second version if offered
If the customer would like to say it again in a language you read, send them your collection link.
- 4
Approve and place it with care
Approve it once the meaning is confirmed, and choose a widget whose page is read by people who speak the language.
What happens next: If a second testimonial in the same language arrives, that is a pattern. Offering your form in that language and naming a standing reviewer are both worth considering.
Before you start
What StoryProof does not do here
No language detection
StoryProof is not described as recognising which language a testimonial is in. You identify it yourself.
No built-in translation
StoryProof does not translate testimonials. Translation happens in a tool or with a person outside it.
Spoken video stays spoken
StoryProof does not turn speech into text. A video in an unknown language needs a person who understands it.
No editing of the original
The customer’s words stay as submitted. Show any translation as a labelled addition on your own page.
Form languages are limited
Collection forms are available in 6 languages on every plan. A customer may still write in a language your form does not offer.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is machine translation enough to approve a testimonial?
It is a useful first read, not a confirmation. Have a person who reads the language check it before the testimonial appears under the customer’s name.
Should I publish the original or a translation?
Publish the original where readers of that language will see it. If you add a translation, label it and make sure the customer is happy with it.
Can I ask the customer to rewrite it in English?
You can offer, not insist. Some people write more warmly in their own language. A short confirmation of meaning is often enough.
What if nobody can confirm it?
Leave it unpublished and tell the customer you are grateful. An unchecked testimonial on your site carries more risk than a missing one.
Still have a question? Ask the StoryProof team or book a demo.
Keep it private until you know what it says
Testimonials wait for your approval, so an unreadable one never reaches your site by accident.
Last updated 2026-11-20.