Sending customer quotes to a translator
Export Testimonials for Translation Vendors
A translator can only be as good as the file you send. Hand over a raw export and you get back product names rendered into French, a German quote twice the length of the slot it was meant for, and no way to tell which line came from which customer. Prepare the file first: a reference for every row, the words that must not change, and where each quote will appear.
- A row reference that survives the round trip
- Names and product terms marked to keep
- Context and length limits for every line
The problem, solved
Where testimonial translation goes wrong, and the fix
Retyping quotes into a brief
Pasting quotes one by one into a document drops lines and introduces typos before the translator even starts.
With StoryProof: Export the space’s testimonials as a CSV from the workspace settings and use that file as the base of the vendor file.
We paid to translate quotes we never use
Translators charge by the word. Sending the whole library pays for quotes nobody will publish.
With StoryProof: Tag the testimonials meant for the new market and filter by that tag, so you know exactly which rows to keep in the file.
Unapproved quotes went to the vendor
A submission still in the queue might never be published, or might be one you would reject.
With StoryProof: Nothing goes public until approved, so use approval as the gate: only approved testimonials go into the vendor file.
Could we skip translation entirely?
A translated quote is your wording of the customer’s words. A testimonial written in the market’s language needs no such care.
With StoryProof: Collection forms are available in 6 languages on every plan, so for new markets you can also ask customers there directly in their language.
The checker cannot see the originals
The in-house reviewer who checks the returned file needs the source quotes, not just the translation.
With StoryProof: Roles give each teammate only the parts of the workspace they need, so a language reviewer can read the library without broader settings access.
Flip the switch to see how StoryProof handles each one.
Vendor file checklist
Prepare a testimonial file a translator can work with
Tick each item as the file takes shape. The first group is what makes the returned file usable.
Ticks are held in this browser tab only; nothing is uploaded.
A sample vendor file layout
Illustrative sample, invented rows
Ref T014 · Source: "Setup took one afternoon and support answered within the hour." · Keep: Fernhill Tools · Where: product page hero · Limit: 90 characters · Target DE: (blank)
Ref T015 · Source: "We stopped chasing clients for feedback." · Keep: none · Where: email footer · Limit: 60 characters · Target DE: (blank)
The reference column is the only thing that ties a German line back to the customer who wrote the English one.
In StoryProof
From export to published translation
- You will need
- A tag marking testimonials for the new market
- A translator or agency
- A fluent reviewer on your side
- 1
Filter and export
Filter the library by the market tag to confirm the set, then export the space to CSV from the workspace settings.
- 2
Build the vendor file
Keep only approved, tagged rows; add the reference, keep-as-is, placement and length columns; delete what the vendor does not need.
- 3
Brief and send
Tell the vendor these are real customers’ words: meaning and tone first, nothing added, names untouched.
- 4
Check what returns
Count the references, have a fluent colleague compare each line, and ask customers to approve their translated quote where possible.
What happens next: Publish translations on the localised pages labelled as translations, and keep the vendor file with the reference column as your record of who said what.
Before you start
What to keep in mind
No translation feature is claimed
StoryProof is not described here as translating testimonials or storing a translation beside the original. The translation lives in your file.
The export’s fields are yours to check
This page does not say which columns the CSV contains. Inspect it before you design the vendor file.
A translation is not the customer’s words
Present it as a translation. Where possible, get the customer’s approval of the translated version.
Video and audio are a separate job
This file covers written quotes. Spoken testimonials need their own approach, which this page does not cover.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is machine translation good enough for testimonials?
It can draft, but a customer’s quote is a public statement in their name. Have a fluent person check every line before it is published.
Should I send emails and ratings to the vendor?
No. Send only what is needed to translate: the quote, the names to keep and the context. Leave contact details out.
Do I need the customer’s permission to translate their quote?
Check what they agreed to. Asking them to approve the translated wording is the cleanest route, and it is a courteous one.
How do I keep translations up to date?
Keep the reference column and the vendor file. When you add new testimonials for the market, send only the new references.
Still have a question? Ask the StoryProof team or book a demo.
Organise once, export for every market
Tag testimonials by market in StoryProof and export a clean starting file for each translation job.
Last updated 2026-11-19.