A company translates its customer messages into several languages. The translations are accurate and the meaning is preserved throughout.
In one market the response rate falls noticeably. The messages use an informal address that in English reads as warm and approachable, and in that language, to a business customer who has never met them, reads as a stranger being overfamiliar.
Nobody complains. They simply do not reply, and the company concludes the market is difficult rather than that the tone was wrong.
Mistake 1: assuming friendly translates as friendly
English business communication is informal by international standards, and rendering that informality directly reads as presumptuous in several languages.
Mistake 2: not choosing a register deliberately
Formal or informal is a decision, and it should be made per language and per context rather than inherited from whatever a translation tool produced.
Mistake 3: using one register for every situation
The right level frequently differs between a marketing message, a support reply and a complaint response, even within the same language.
Mistake 4: translating brand and product names
Which produces confusion and inconsistency, and is the problem described in terminology and brand names across languages.
Mistake 5: translating humour and idiom
Both fail more often than they work, and a joke that does not land in a second language makes the whole message read as strange.
Mistake 6: ignoring directness conventions
Some languages expect a direct answer and others expect context first, and getting this wrong reads as either brusque or evasive.
Mistake 7: mishandling names and titles
How somebody is addressed, whether titles are used, and whether a first name is appropriate. Getting this wrong is noticed immediately.
Mistake 8: applying one apology style everywhere
The expected degree of formality in an apology varies considerably, and an insufficient one in the wrong market causes real offence.
Mistake 9: never having a native speaker review anything
The standard messages are a finite set. One review by a native speaker, once, resolves almost all of this permanently.
Mistake 10: assuming a market is one register
Regional differences within a language are real, and a form that is standard in one country can be unusual in another using the same language.
Mistake 11: letting the versions drift
Each language maintained separately diverges within months, which is the same maintenance failure as stock and service differences between branches.
Mistake 12: not documenting the decision
A register chosen and not written down is a register that changes whenever somebody new writes a message.
Mistake 13: treating this as perfectionism
It is not. It is the difference between a market that responds and a market that quietly does not.
Mistake 14: reviewing only the marketing copy
The messages customers actually receive are confirmations, reminders, support replies and apologies, and those are almost never reviewed by anybody. The tone that matters is the operational one rather than the campaign one.
Set the register once and apply it everywhere
An assistant with the register documented per language answers consistently in the expected tone, keeps brand terms untranslated, and applies the same formality whether the conversation happens at nine in the morning or midnight. The choice of which languages to support is covered in deciding which languages to support first, and the distinction from a staffed window in the difference between a chatbot and a live chat. See features, start at try, and the sector view sits under small business.