# Replying to a customer who writes in a language you do not read

> A customer writes in a language you cannot read. How to understand them, reply safely, check a translation, protect their data and know when to ask a human.

- Published: 2026-10-16
- Author: Koltrix Team
- Category: Customer support
- Source: https://koltrix.com/blog/replying-to-a-customer-who-writes-in-a-language-you-do-not-read

The message arrives in your shared inbox with a subject line you cannot read. Maybe it is a payment problem, maybe a complaint, maybe a simple question. The customer clearly took the trouble to write in their own language, and now your small team has to decide what to do with it.

This is a normal situation for any business that sells beyond one country. You do not need a translation department to handle it well. You need a short routine: understand the message, decide what language to reply in, check what you send, and know when to get a person involved. This guide walks through that routine.

## Step 1: Understand what they wrote

Start by getting the meaning, not the polish. A rough reading is enough to decide the next move.

**Use a translation tool for a first pass.** Browser translation, a translation website or a built-in feature in your mail app will give you the gist in seconds. Treat it as a draft of the meaning, not a perfect record. Short, plain messages translate well. Slang, jokes, legal wording and very long sentences translate badly, and the mistakes can be quiet: a "not" lost, a date read the wrong way, a polite phrase that becomes rude.

**Read the parts that carry facts.** Order numbers, amounts, dates, email addresses and names do not need translation. Find them in the original and compare them with your records.

**Look for the type of message.** Is it a question, a problem, a request for money back, a threat to cancel? You can often tell from structure even before the text is clear: a screenshot, an invoice number, an error code.

**Be careful with two things.** First, dates: 03/04 means different days in different countries. Second, anything with legal or medical weight. If the message looks like a formal complaint, a data request or a dispute, slow down and get proper help, as below.

## Step 2: Protect what the customer wrote

Pasting a customer's message into an online translator sends their words to another company. That may be fine for a question about a feature. It is not fine for a message that contains personal data, account details, health information or anything marked confidential.

A simple rule for small teams:

- **Low risk** (a how-to question, a public product issue): a general translation tool is fine.
- **Medium risk** (names, order details, addresses): use a tool your company has chosen and understands, and remove what you do not need before pasting.
- **High risk** (identity documents, medical or legal content, passwords, payment details): do not paste it anywhere. Ask a qualified person who can work under your confidentiality rules.

If you use an AI assistant to translate, the same rules apply, and your team should know what that assistant is allowed to see. For the basics, read [AI email privacy questions](/blog/ai-email-privacy-questions) and [personal data in email: plain rules for small teams](/blog/personal-data-in-email-plain-rules-for-small-teams).

## Step 3: Decide what language to reply in

You have three honest options. Pick one on purpose.

**Reply in their language.** This is the warmest option and the riskiest if you cannot check the result. It works well for short, simple, low-stakes replies: confirming you received the message, sending a link, saying you are looking into it.

**Reply in your language, in plain words.** Many people read a second language better than they write it, and your short, clear English may be perfectly understood. This is often the safest choice for technical or sensitive topics, because you know exactly what you wrote. Our post on [support email in plain English for non-native readers](/blog/support-email-in-plain-english-for-non-native-readers) lists the habits that make this work: short sentences, one request per paragraph, no idioms.

**Reply in both.** Put their language first, then your own below a line. The reader gets the friendly version, and if the translation is off, the original is there to clarify. This costs a little extra length and avoids many misunderstandings.

If you are not sure what they prefer, ask in the very first reply, in both languages, in one line: "Would you like us to continue in [their language] or in English?" Then remember the answer. A note on the contact record saves the next person from asking again.

## Step 4: Write a reply you can trust

You cannot proofread a language you do not read, so make the reply easy to get right.

1. **Write your source text first, in simple words.** The simpler the English, the better any translation will be. Replace "We will circle back once we've had a chance to dig in" with "We will check this and reply by Friday."
2. **Keep it short.** Every extra sentence is another place for the translation to go wrong.
3. **Put the key facts in a short list or on their own lines.** Dates, amounts, steps and links survive translation better when they stand alone.
4. **Avoid humor, idioms and cultural references.** They rarely cross over.
5. **Translate, then translate back.** Run the result back into your own language with a different tool. If the meaning changed, simplify the original and try again. It is not perfect, but it catches big mistakes.
6. **Keep names, links and numbers out of the translation.** Insert them afterwards so a tool cannot "translate" an order number or a product name.
7. **Do not promise anything you have not checked in your own language.** Refunds, deadlines and policy statements should be written and approved in the language you can read.

If you use AI for the draft, read the cautions in [AI multilingual email caveats](/blog/ai-multilingual-email-caveats), and use the checklist in [reviewing AI-drafted replies](/blog/reviewing-ai-drafted-replies-checklist). AI can produce fluent text in many languages, and fluent is not the same as correct.

## Step 5: Know when to ask a person

Some replies deserve a human who reads the language. Get help when:

- The message involves a legal threat, a formal complaint or a regulator.
- It contains a request about personal data, such as access or deletion. See [handling privacy and data requests by email](/blog/handling-privacy-and-data-requests-by-email).
- Money is involved beyond a routine amount, or you are about to refuse a refund.
- The customer seems upset and the translation is unclear. Tone is easy to miss through a tool.
- The same customer writes often. A relationship is worth a proper reply.

Your options include a colleague, a friend of the business, a freelance translator or a language service. For regular volume in one language, a trusted freelancer on call is often cheaper and better than you expect. Agree the rules first: what they may see, how long they keep it, and how fast they can reply.

## Step 6: Make it repeatable

If this happens once a quarter, the routine above is enough. If it happens every week, build a little structure.

- **Save short replies in the common languages.** A first reply that says "We received your message and will answer within one business day" can be translated once, checked by a reader of that language, and reused. The approach is in [reusable reply snippets](/blog/reusable-reply-snippets-team).
- **Tag the thread with the language.** That makes it easy to see how much volume each language brings and who can help.
- **Record the preference** on the contact.
- **Keep a short glossary.** Product terms, plan names and button labels should be translated the same way every time.
- **Decide your promise.** Say clearly on your site which languages you support in full and which you handle on a best-effort basis. Do not promise what you cannot deliver.

## A model first reply

Here is a safe pattern for a first response to a message you cannot read. Write it in your own language, and add a translation below it.

> "Thank you for writing to us. We have received your message and will reply within one business day. If you prefer, tell us which language you would like us to use."

It does three things: it confirms receipt, sets a time, and gives the customer a way to choose. It makes no promise about the content of their problem, so there is nothing to retract.

## What to avoid

- **Replying with a machine translation of a complex answer and no check.** Mistakes in a refund or policy message are costly.
- **Replying in a language you cannot read just to look friendly.** A confident wrong sentence is worse than a plain correct one.
- **Ignoring the message** because it is hard. Silence reads as dismissal in any language.
- **Switching languages mid-thread without telling the customer.** It confuses people and can look automated.
- **Assuming the country tells you the language.** People live and work in languages that differ from the place you see in their address.

## The short version

Get the meaning with a tool, protect what the customer wrote, choose the reply language on purpose, keep your text simple and your promises checked, and bring in a human when stakes or feelings are high. A customer who writes to you in their own language is giving you a chance to show you take them seriously. A short, clear, honest reply does that in any language.