Skip to main content

When the approver does not speak the language

Manage Multilingual Testimonials in Teams

A testimonial arrives in Portuguese, and the person who approves testimonials reads English and some French. Approving it blind is a risk; leaving it in the queue wastes it. Answer four questions below to see who should review it, then set up reviewer roles so the next one is not a puzzle.

  • Four questions, one named reviewer
  • A language tag on every submission
  • Nobody approves what they cannot read

Reviewer picker

Who should review this testimonial?

Answer for one testimonial, or for one language you receive regularly.

Does someone on your team read this language fluently?
Where will it be shown?
Does it mention results, money, health or safety?
How often do you get testimonials in this language?

Your answers stay in your browser. Nothing is saved or sent.

The problem, solved

What happens without a reviewer for each language

  • Problem 1

    Someone approves what they cannot read

    A four-star rating and a few familiar words look fine. The text turns out to praise one thing and complain about another.

  • Problem 2

    Auto-approval lets it straight through

    A rule that approves 4 and 5 star testimonials with text does not know which language the text is in.

  • Problem 3

    Nobody can tell which language is waiting

    Submissions in five languages sit in one queue, and each reviewer has to open all of them to find theirs.

  • Problem 4

    The fluent colleague has no access

    The Spanish speaker is in sales and cannot open the queue, so every review is a forwarded screenshot.

  • Problem 5

    Customers cannot write in their own language

    Forced into English, customers write shorter, flatter testimonials, which then need less review but say less.

A reviewer map for a small team

Write one row per language you receive. Leave the reviewer blank only if the action is to hold.

Sample map. Replace the rows with your own languages and people.
LanguageNamed reviewerIf they are awayShown where
EnglishUsual approverAny approverAll English pages
SpanishFluent colleague in salesAsk the customer to confirmSpanish pages only
GermanNobody in teamOutside linguist for result claimsGerman pages after check
Any new languageNobody yetHold with language tagNot shown

In StoryProof

Set up language review in StoryProof

  1. 1

    Tag by language on arrival

    Whoever checks the queue adds a language tag, so each reviewer can look only for theirs.

  2. 2

    Give reviewers access

    Add one reviewer per language to the space, within your plan’s seat count.

  3. 3

    Approve only after review

    The reviewer reads it and leaves a decision; the approver approves. Submissions stay private until then.

  4. 4

    Place it with its language

    Choose which approved testimonials each widget shows, so the Spanish one appears in the Spanish page’s widget.

What happens next: When a reviewer leaves the company, update the map that day. A language with no reviewer goes back to hold.

Before you start

What StoryProof does not do here

What this does not cover, and what to check on your side. Better to know now than after launch.

  1. 01

    No translation is claimed

    StoryProof is not described as translating testimonials. Any translation is done by a person and should be labelled as one.

  2. 02

    No language detection is claimed

    The language tag is added by whoever reads the queue, not by the product.

  3. 03

    Forms cover six languages

    Collection forms come in 6 languages. A customer writing in another language can still type in it, but the form around them will not be in it.

  4. 04

    Auto-approve does not check language

    The automation approves by rating and text. It cannot tell whether a reviewer has read it.

FAQ

Questions people ask

Short answers to what usually comes up next.

Can we use a machine translation to check a testimonial?

It is a reasonable first look, not a review. It can miss sarcasm, a complaint tucked into praise, or a claim that matters. Use it to decide whether to bring a reviewer in.

Should the reviewer be allowed to correct grammar?

Treat it the same as in your own language: leave the customer’s words alone unless they agree to a change.

What if the customer wrote in two languages at once?

Review it with whoever reads the less familiar part. If it will be shown on a single-language page, ask the customer which version they prefer.

Do we need a reviewer for languages we rarely see?

Not a standing one. Use the customer-confirm or hold route until a language turns up often enough to justify naming someone.

Still have a question? Ask the StoryProof team or book a demo.

Review every language before it goes live

Collect in the customer’s language, tag it, and approve only once someone who reads it has checked.

Last updated 2026-11-17.