Skip to main content

Translation and localization agencies

Client Testimonials for Translation Agencies

A translation agency’s best work is invisible by design. The contract reads as if it had been written in German, the app launches in Japanese on the same day as in English, and nobody outside the client ever knows a translator touched it. Much of it is also confidential: unreleased products, legal filings, financial reports. Clients work in many languages, and the person best placed to judge quality is often a reviewer in another country you have never spoken to. The checklist below handles each of those before you ask.

  • Keeps document and product names out of proof
  • Brings in the in-country reviewer’s view
  • Shows proof by language pair and service

The problem, solved

What makes testimonials hard for a translation agency

Situation 1 of 5

The client names the confidential document

“They turned our merger filing around overnight” is glowing, and it tells the world about a deal that may not be public.

How StoryProof solves it

Nothing a client submits goes public until you approve it, so every testimonial passes a check for document names, deals and unreleased products before it can appear.

Workflow checklist

Collect translation agency testimonials safely

Run it per client account. Most of the risk sits in the first and third groups.

Before you ask
In the request
Before you approve
On your site

Your ticks stay in this browser tab and are not sent anywhere.

Prompts

Questions for buyers and for reviewers

Two people, two kinds of proof. Put the matching questions on separate forms.

The buyer: localization or marketing manager

  • What were you worried about before handing the project to us?
  • How did we handle a deadline that moved or a question that came up mid project?
  • What would you tell a colleague choosing a language partner?

Leave out

  • Which product launch was it for?

The in-country reviewer

  • How much did you need to change before it was ready to publish?
  • Did it read as if it had been written in your language from the start?
  • How well did the terminology match your company’s own?

Leave out

  • Can you quote a sentence from the translation?

A long running account

  • How has working with us changed since the first project?
  • What do you no longer have to check that you used to?

In StoryProof

Run the routine with StoryProof

  • You will need
  • Collection forms set up in the languages your clients use
  • A list of each account’s buyer and reviewer
  1. 1

    Add buyer and reviewer as contacts

    Add both people for each account you plan to ask, after checking the contract and getting the client’s agreement to contact the reviewer.

  2. 2

    Send each the form in their language

    Email each person the collection link in their language, with the matching questions from above. They can record or write their answer.

  3. 3

    Screen for confidential detail

    Read every submission against the “Before you approve” group. Approve only what is clean, and ask the client to resend anything that names a document or deal.

  4. 4

    Tag by language pair and service

    Tag each approved testimonial, for example “EN to JA” and “software localization”, so each service page can pull its own.

  5. 5

    Thank them

    From Pro, a thank you email can go out two hours after a testimonial is approved, with a link to it.

What happens next: Keep the buyer and reviewer as contacts. A reviewer who moves to another company often becomes your next client.

Before you start

What StoryProof will not do here

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

  1. 01

    It does not screen for confidentiality

    StoryProof will not recognise a document name or a deal. The approval step is where you check, and the judgement is yours.

  2. 02

    Translation is your job

    No translation feature is relied on here. Testimonials arrive in the language the client chose; any translation you show is yours to write, approve with the client and label.

  3. 03

    Your NDA comes first

    Many translation contracts restrict naming the client or the material. Where yours does, use role only attribution or do not publish.

  4. 04

    Reviewers are not your client

    In-country reviewers work for your client or a third party. Contact them only with the client’s agreement and keep the ask short.

FAQ

Questions people ask

Short answers to what usually comes up next.

Who should a translation agency ask for testimonials?

Two people per account where possible: the person who bought the service, for deadlines and process, and the in-country reviewer who checked the translation, for quality.

How do we get testimonials when our work is under NDA?

Check what the NDA allows, ask about the experience rather than the material, and offer role only attribution. Approve nothing that names a document, product or deal.

Should testimonials be in the client’s language?

Ask in the language they are most comfortable in. Show it in that language on the matching page, or with an agreed and labelled translation elsewhere.

How do we show proof for a specific language pair?

Tag each testimonial with its language pair and service, and give each language or service page a widget holding the matching testimonials.

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

Proof as careful as your translations

Ask in each client’s language, keep confidential material out and show the right testimonials for every language pair.

Last updated 2026-11-12.