Reply in the customer’s language when you can check the result, and say so plainly when you cannot. Write your answer in short, literal sentences so a translation tool renders it reliably, then check every number, date, name and link in the translated version. For languages you receive often, keep a set of answers a fluent speaker has checked once, and reuse them.
Should you reply in the customer’s language at all?
Usually yes, if you can do it without introducing mistakes. A reply in their own language is easier to act on, and it tells the customer you read their email properly. But a confident-looking reply with a wrong date in it is worse than a clear reply in English.
| You can… | Do this |
|---|---|
| Read and write the language well | Reply in it |
| Read it, but write it slowly | Draft in the language with a tool, check it line by line, send |
| Barely read it | Translate their email to understand it, write in your language, translate, and check the fixed parts (numbers, dates, links) |
| Not read it at all | Reply in English or your own language, say why, and keep it simple |
Whatever you choose, keep the whole thread consistent. Switching language halfway through confuses customers and anyone who later reads the thread.
How do you write a reply that translates well?
Machine translation handles plain sentences far better than clever ones. Write the source text for the translation, not for style.
- One idea per sentence. Long sentences with several clauses are where meaning gets lost.
- No idioms or jokes. “We’ll bend over backwards” translates badly; “We will do what we can” does not.
- Repeat the noun. “Your order” instead of “it”, so the translation cannot attach the pronoun to the wrong thing.
- Unambiguous dates. “3 October” instead of “10/3”, which reads as March in some countries and October in others.
- Numbers with units. “€25”, “5 business days”, “2 kg”.
- Keep product and plan names in their original form, so the customer can find them in your product.
An example. The original: “No worries, we’ll sort it out asap, it should be with you early next week-ish.” Rewritten for translation: “We will send a new package today. It will arrive by Tuesday 6 October.”
What should you check after translating?
You may not be able to judge the style, but you can check the parts that matter most, because they look the same in every language:
- Numbers and amounts: prices, quantities, order numbers
- Dates and times: that the day and month did not swap
- Names: the customer’s name, product names, plan names
- Links and email addresses: unchanged and still working
- Negations: translate the sentence back to your language and check “can” did not become “cannot”
Back-translation (translating the result back into your own language) is a crude check, but it catches reversed meanings and missing sentences.
Formal or informal “you”?
Many languages distinguish a formal and an informal “you”: Sie and du in German, vous and tu in French, u and je in Dutch. Getting it wrong reads as either cold or overfamiliar.
A safe rule: mirror the customer. If they write informally, reply informally; if they write formally or you cannot tell, use the formal form. Then keep it consistent for the whole thread. Write the choice per language into your team’s tone rules, so every reply from your business uses the same form.
Which parts need a fluent check before you rely on them?
Some text is worth having checked once by someone fluent, because a small error has real consequences:
- Refund, cancellation and warranty terms
- Anything with legal meaning, such as consent or data requests
- Safety instructions
- Your most frequent answers, which will be reused hundreds of times
Once checked, save them as reusable answers in that language. How to handle the same customer question for the hundredth time explains how to build and maintain such a library.
What should you say when you reply in another language?
Be open about it, briefly, and make it easy for the customer to continue in their language:
Hi Marco, thanks for your email. I’m replying in English because I want to be sure the details are right. Your refund of €42 was sent today and should reach your account within 5 business days. If anything is unclear, feel free to reply in Italian and we’ll make sure it gets answered.
This keeps the facts accurate, sets expectations, and does not pretend to a fluency you do not have. (The amount and timing here are examples; use your own.)
How do you handle languages you receive often?
If one language makes up a noticeable part of your inbox, invest once:
- List the ten questions you get most in that language.
- Write the answers in your own language, in plain sentences.
- Have a fluent speaker translate and check them once, including the formal or informal choice.
- Save them as templates or reusable answers, labelled by language.
- Review them when your policy changes, together with the originals.
That turns every future reply in that language into adapting a checked answer, instead of trusting a fresh translation each time.
Can drafting software write in the customer’s language?
Yes. ReplyPen writes each Draft in the language the customer wrote in: a question in German gets a German Draft, in your own Gmail or Outlook thread. It follows your Tone profile and draws on your help pages and past replies, and the Check note under the Draft shows which sources the answer came from, so you can check the facts even in a language you read slowly. The same checks apply as for any translation: numbers, dates, names and links first.
For the full routine around replying faster without losing quality, read How to answer customer email faster without lowering quality.
