Multilingual Inquiry Responses: Identifying, Translating, and Adapting Your Pitch for Less Common Languages

Handling Inquiries in Less Common Languages: Language Tiers, Translation Workflow, and Pitch Adaptation

Multilingual Inquiry Responses: Identifying, Translating, and Adapting Your Pitch for Less Common Languages

Bottom line first: The worst thing you can do with an inquiry in a less common language is reply with raw machine translation. When a buyer gets an Arabic or Russian email full of awkward grammar and garbled terminology, they immediately question how professional you really are. Do it right by sorting inquiries into language tiers: reply to English inquiries through your standard process; for major languages like German, Spanish, and French, draft in English, machine translate, then have someone proofread the terminology; for less common languages like Arabic, Russian, and Vietnamese, reply in English first and ask the buyer whether they’d prefer their local language. You must build a terminology base, so the same product name is translated the same way every time in every language. Counterintuitive but true: replying to an inquiry in a less common language in English earns more trust than machine translating into that language.

1. Why You Shouldn’t Reply to Inquiries in Less Common Languages with Raw Machine Translation

Once your site has multilingual versions, you’ll get inquiries in all sorts of languages: German, Spanish, Arabic, Russian, Vietnamese. Many teams react the same way: reply in whatever language the buyer wrote in. So they open Google Translate, convert an English template into Arabic, copy, paste, and hit send.

The buyer has the opposite experience. They open this “Arabic” reply and find the grammar is off, the terminology is wrong, and a few words are even in English. Their conclusion isn’t “this company is making an effort to speak my language” but “this company can’t even translate its own product names correctly. Are they a middleman?”

Machine translation is good enough for everyday phrasing, but in a B2B inquiry, what the buyer cares about is precisely the technical terminology: model specs, material grades, certification standards. Machine translation gets these wrong constantly, and wrong with total confidence. For the quality bar on multilingual content, see Multilingual Content Publishing Process.

Language tier	Example languages	What to do	Response SLA
English	English inquiries	Reply through the standard process	5 minutes during working hours
Major languages	German, Spanish, French, Portuguese	Draft in English, then translate and proofread	2 hours during working hours
Less common languages	Arabic, Russian, Vietnamese, Thai, Turkish	Reply in English first	1 hour during working hours
Mixed language	Half English, half local language	Identify the main language, reply in English	1 hour during working hours

2. Language Identification and Routing

When an inquiry comes in, the first step isn’t translating. It’s figuring out what language the email is in and whether it needs special handling. Many emails are actually mixed: the greeting is in Arabic, but the specs are copied straight from English. In that case the main language is Arabic, but the technical specs are already in English, so there’s nothing to translate.

You only need the first two sentences of the email body to identify the language. No need to analyze the whole thing. Once identified, route it using the tier table above: English inquiries go straight to the sales queue; inquiries in major languages go to a sales rep who speaks that language or to a translator; inquiries in minor languages get an English reply first, with a line at the end: “If you’d prefer to communicate in Arabic, we can arrange a translator.”

Routing action	Trigger	Owner	Timeframe
Reply in English directly	English or minor-language inquiry	On-duty sales rep	Within 1 hour
Translate, then reply in local language	Major language with steady inquiry volume	Sales + translator	Within 2 hours
Escalate to native-speaking sales rep	Buyer explicitly requests local language	Sales rep for that language	Take over within 4 hours
Outsource translation	Minor language and buyer insists on local language	Translation vendor	Within 24 hours

Counterintuitive call: replying to a minor-language inquiry in English is more credible than forcing a translation into that language. B2B buyers generally know enough English — if they found your products on your English site and filled out the form, they can at least read an English email.

A grammatically clean English reply comes across as far more professional than a machine-translated minor-language reply full of garbled terminology. For the market logic behind multilingual GEO, see Multilingual GEO.

3. Translation workflow and message adaptation

When you do need to reply in the local language — say the buyer explicitly asks to communicate in German — here’s the workflow: sales writes the reply in English first, then machine-translates it into German, and finally a human proofreads only the key terminology and specs. For general phrasing, use the machine translation as is.

Why not translate everything by hand? Because 80% of a B2B email is general phrasing — “Hello,” “Thanks for your inquiry,” “We’ll send the spec sheet tomorrow” — and machine translation handles that fine. Only 20% is technical terminology—

—model numbers, specs, certification names—and that has to be checked by a human. Full human translation is too expensive and too slow. Machine translation plus human proofreading of terminology gives you the best value for money. This is the idea behind machine translation post-editing (MTPE). For details, see translation post-editing (MTPE).

Content type	Translation method	What to proofread	Example
Greetings and general phrasing	Use machine translation as is	No proofreading needed	“Hello, thanks for your inquiry”
Product models and specs	Human translation	Check word by word	5mm wall thickness, operating temperature -20 to 80°C
Certifications and standards	Check the official translation	Fixed terminology	CE, ISO 9001, FDA
Business commitments	Human translation	Accurate tone	“30-day lead time” must not become “about 30 days”

A terminology base is a must. If the same product name is translated as “pump” one time and “water pump” the next, buyers will suspect you’re a middleman reselling goods. Build a lookup table of the 50 to 100 terms that come up most often,

with a column each for English, German, Spanish and Arabic, and have both sales and translators use the same table. For terminology consistency settings in AI translation tools, see AI translation for your own site.

There’s a detail that matters when adapting your messaging: business communication styles differ from market to market. Germans like it direct, with bullet points. Japanese buyers prefer small talk before getting down to business. Middle Eastern buyers care more about building a relationship. Don’t just run the same English email through machine translation and call it done.

Adjust the length of your opening small talk to suit the market. For an overall approach to identifying intent in inquiries, see Identifying inquiry intent and responding differently.

4. Common mistakes

Mistake	What teams do	What actually happens	The right way
Replying with raw machine translation	Copy-pasting from Google Translate	Terminology errors make you look unprofessional	Have a human check the terminology before sending
Forcing yourself to write in the local language	Insisting on replying in the local language even for rare languages	Poor machine translation costs you the deal	Reply in English first for rare languages
No terminology base	Looking up every term from scratch each time	The same term translated several different ways	Build a reference table for high-frequency terms
Translating everything by hand	Finding a translator for every email	Slow responses lose deals	Machine-translate the generic parts, human-translate the terminology
Ignoring mixed-language content	Treating the whole email as if it were in the local language	Technical specs get mistranslated	Identify which parts don’t need translating

Example: a foreign trade team got an inquiry in Arabic and had a salesperson who’d studied Arabic for just six months force out a reply. The buyer wrote back in Arabic, and the salesperson stumbled through the translation, spending half an hour with a dictionary on every round.

Two weeks later, the buyer was gone. Then they tried a different approach: reply in English from the first email, saying “we’re more efficient in English, and if you need Arabic materials we can provide a translated version.” The buyer agreed right away,

the conversation moved along smoothly, and the deal closed three months later.

How fast to build a multilingual team: don’t staff salespeople for five languages from day one. Look at the data first. If inquiries in a given language make up more than 10% of total inquiries, bring on someone or outsource for it. For languages below 10%, replying in English with terminology support is enough. For the overall process of translating multilingual content, see Translating multilingual content for your own website.

FAQ

If I get an inquiry in a rare language, do I have to reply in that language?

Not necessarily. B2B buyers generally know enough English. If they found your products on your English site and filled out the form, they can at least read an English email. Reply in English first, and add a line at the end: “If you’d prefer to communicate in your local language, we can arrange a translator.” That comes across as far more professional than forcing out a reply in a rare language full of garbled terminology from machine translation.

How should I handle major languages versus rare ones differently?

German, Spanish, French and Portuguese are major languages: inquiry volume is steady and translation resources are easy to find, so draft in English, machine-translate, then have a human check the terminology. Arabic, Russian, Vietnamese, Thai and Turkish are rare languages: translation resources are scarce and machine translation quality is poor, so reply in English first and ask the buyer whether they need the local language. Besides the language itself, the other criterion is whether inquiries in that language make up more than 10% of the total.

Can I send machine-translated results straight to a customer?

You can machine-translate the generic parts, but not the technical terms. In B2B email, 80% is pleasantries and boilerplate — “Hello,” “Inquiry received,” “I’ll send the spec sheet tomorrow” — and machine translation handles that fine. The other 20% is model numbers, specs, and certification names, and those have to be checked by a human. If you machine-translate everything and hit send, a wrong term makes the buyer wonder whether you’re just a middleman. Full human translation is too slow, so the right approach is machine translation plus human review of the key terms.

How do you build a terminology base?

Turn the 50 to 100 terms that come up most into a reference table, with one column each for English, German, Spanish, and Arabic. Include product model numbers, core specs, certification standards, and commercial terms. Sales and translators use the same table, so the same product name is translated the same way every time. Don’t look it up fresh each time — if the same model is A one day and B the next, the buyer will suspect you’re reselling. Add new terms to the terminology base once a quarter.

What if the buyer insists on a reply in a minor language?

If the buyer explicitly asks for their local language, hire a freelance translator and deliver within 24 hours. Don’t make an English-speaking salesperson struggle through it. The process: the salesperson writes the reply in English, sends it to the translator to render into the target language, and once it comes back, checks the content over before sending. On cost, minor-language inquiries won’t be high in volume, so paying a freelancer per message makes sense — you don’t need to hire a full-time salesperson for a minor language.

Do the talking points need to change from language to language?

Fine-tuning helps. Germans like bullet points up front, no warm-up. Japanese buyers like a couple of pleasantries before getting down to business. Middle Eastern buyers put more weight on relationship building, so you can open with a couple more greetings. Don’t just machine-translate the same English email and call it done. The core information — specs, lead time, MOQ — is the same worldwide, but how long the opening pleasantries run and what tone they take should shift by market.

Final thoughts

Handling multilingual inquiries isn’t really a translation problem — it’s a trust problem. What buyers care about isn’t whether you can write to them in their language, but whether you understand what they need, whether your specs are accurate, and whether your lead times are reliable. Forcing out a translated email full of garbled terms just to look “localized” costs you trust instead of earning it.

Three steps to put this in place: first, sort by language — reply in English directly, translate and review for major languages, and start in English for minor ones. Second, build a terminology base of 50 to 100 entries that all salespeople and translators share. Finally, for any language that makes up more than 10% of your inquiries, assign a dedicated or freelance translator; below 10%, replying in English with terminology support is enough.

One line worth remembering: for a first reply to an inquiry in a minor language, clean English is more professional than bad machine translation — buyers want a reliable supplier, not a salesperson who speaks their hometown dialect.