How to Send Cold Email in Different Languages Without Sounding Like a Robot

You found a great set of prospects in Germany, Brazil or Spain. Then the question hits: do you email them in English and hope, or write in their language and risk an awkward translation? Both can go wrong. A clumsy machine translation reads like spam, and an English email to a local bakery in Lyon may simply get ignored.

This guide walks through a process you can start today: decide which language each lead gets, write a version that sounds native, and send it so the languages never get mixed up.

Step 1: Decide which language each lead should get

Don't decide by country alone. Belgium, Switzerland and Canada each have more than one common business language, and plenty of tech companies everywhere work in English.

Use these signals, roughly in this order:

• The language of their website. This is the best clue. If their site is only in Portuguese, write in Portuguese.
• The type of business. Local service businesses (dentists, plumbers, restaurants) usually expect their local language. SaaS companies and agencies often work comfortably in English. See the notes on SaaS companies for how that segment tends to operate.
• The city. In bilingual countries, the city often tells you the main language (Montreal versus Toronto, for example).

When you build your list, record the language as its own field. Thinking in firmographics helps here: language is just another attribute of the company, like size or category.

Step 2: Split your list into one campaign per language

Never put two languages in one campaign. It makes follow-up timing, subject lines and reply handling messy, and one wrong merge sends Italian text to a French prospect.

A simple structure:

1. One folder or list per language (for example "Dentists - Spain - ES").
2. One campaign per folder.
3. One sending account or set of accounts per market, if your volume justifies it.

In GetClient you can scrape Google Maps by keyword and city, save leads into separate folders in My Leads, and run a separate campaign for each, so the Spanish leads and their Spanish sequence stay together. If you already have leads elsewhere, CSV import with a custom "language" field works the same way.

Step 3: Write the email in your language first, then translate carefully

Write a short, clear master version first. Short sentences translate better than clever ones. Avoid idioms, jokes and wordplay; they rarely survive translation.

Then translate with this order of preference:

• A native speaker reviews it. Best option. Even a 20-minute paid review from a freelancer catches the phrases that scream "foreigner using a tool".
• AI translation plus a native check. Good middle ground. Ask the tool to make it sound like a local business owner wrote it, not to translate word for word.
• AI translation alone. Only for testing a market, and keep it very short and plain.

One trick: translate the result back into English with a different tool. If the meaning drifted, fix the original sentence.

Step 4: Adapt tone, not just words

Languages carry different expectations about formality. Some practical points:

• Formal versus informal "you". German (Sie/du), French (vous/tu) and Spanish (usted/tú) all force a choice. For a first cold email to a business owner, the formal form is the safer default. Startups and younger brands may use informal language on their own site; match what they use.
• Greetings and sign-offs. "Hi {{params.firstname}}" works in English. In German, "Hallo" plus the name is common for casual B2B, while "Guten Tag" is more formal. Ask your reviewer what a local would write.
• Directness. Some markets prefer a bit more context before the ask. Keep your email short anyway, but one sentence explaining why you're writing can help.
• Dates, numbers and currency. Write prices in local currency if you mention them, and use local date formats.

Step 5: Check your merge tags and personalization

Merge tags pull data straight from the lead, and that data may be in a different language or format from your email.

• {{params.name}} is the business name as listed. Make sure the sentence around it still works grammatically, since some languages change word endings or need articles.
• {{params.category}} often comes in the scraped language (for example "Zahnarzt"). Preview it in context, or avoid it if categories look inconsistent.
• {{params.city}} may come out as "München" or "Munich". Pick one and clean the list.
• {{params.firstname}} is only useful when present. If many leads lack an owner name, write a greeting that works without it.

Always preview a few real leads per step before sending. Small grammar glitches are what make translated emails look automated.

Step 6: Translate everything around the email too

People forget the parts outside the main body:

• Subject line. Write it natively; don't just translate the English one.
• Follow-ups. Every step in the sequence needs a native version. Spacing between steps works the same as in English; see how long to wait between follow-ups.
• Unsubscribe text. The link text should be in the recipient's language so they can actually find it. More on why it matters in the unsubscribe link guide.
• Signature. Include your company name and contact details. Rules on sender identification differ by country, so check what applies where you're sending. This is not legal advice.

Step 7: Plan for replies you can't read

Someone will reply in fluent Dutch. Have a plan before that happens:

1. Read replies with a translation tool to understand them.
2. Write your answer in English, translate it, and keep it short. Simple sentences survive.
3. If a lead is serious, tell them honestly you work best in English and ask if a call in English is fine, or bring in a native-speaking partner.
4. Treat polite refusals the same way in every language. The not interested replies guide applies regardless of language.

Keep all replies in one place so none get lost. GetClient's Inbox shows replies from your connected Gmail or SMTP accounts together, which helps when you're juggling three markets.

Step 8: Start small in each new language

Treat each language as its own test. Send a small batch first, read the replies, and fix tone problems before scaling. Keep your normal deliverability habits: warm up new accounts (email warm-up), verify lists before sending, and consider a secondary domain for outreach so testing a new market doesn't put your main domain at risk.

Compare campaigns side by side. If one language gets replies and another gets silence, look at the translation and the targeting before blaming the market.

Want to try it? New GetClient accounts get 100 free credits with no card needed, enough to pull a small list in one city and test a single translated sequence. Plans are on the pricing page.