A business receives an enquiry in a language nobody on the team reads. It goes into the inbox with everything else.
Somebody runs it through a translator two days later and discovers it was a substantial enquiry from a company that wanted to buy immediately. They write a reply, translate it back, and send it on the third day.
No answer comes. The enquirer had already dealt with a competitor whose website spoke their language and whose reply arrived the same afternoon.
The first failure: the enquiry is deprioritised because it is difficult
Not deliberately. It simply moves to the bottom of the pile every time somebody opens the inbox and cannot immediately read it.
The second failure: nobody knows how many arrive
Businesses that check are usually surprised, and the ones that never check assume the number is zero because they never acted on any.
The third failure: the website is monolingual
So most speakers never enquire at all, and the handful who do are the most determined rather than the most valuable.
The fourth failure: translation is treated as the whole answer
A translated website with an inbox nobody can answer in that language is a shop with a sign in the window and nobody behind the counter.
The fifth failure: the reply is slower than the competition
Which is the entire mechanism of the loss, since the enquirer has contacted several businesses and will engage with whoever answers.
The sixth failure: the wrong language is chosen
Businesses guess which languages matter instead of looking at where their enquiries and their traffic actually come from, which is the ground in deciding which languages to support first.
The seventh failure: the register is wrong
Machine translation gets the words and misses the formality, which in some languages reads as rudeness and loses the relationship immediately.
The eighth failure: the specifics are mistranslated
Prices, terms, measurements and legal statements, where an approximate translation is not a small error but a real liability.
The ninth failure: the person who does speak the language is not used
Many teams have somebody, and there is no mechanism for the enquiry to reach them, which is the gap in handover to a team member who speaks the language.
The tenth failure: the time zone compounds the delay
Overseas enquiries frequently arrive overnight, so a two day reply is a four day reply in the customer's experience.
The eleventh failure: the follow up is never attempted
Because writing a second message in a language nobody speaks is harder than writing the first, and the first was already hard.
The twelfth failure: the segment is written off
The conclusion is that these customers are difficult, rather than that nothing was ever built to serve them.
The thirteenth failure: the enquiry is answered in English anyway
A reply in a language the sender did not write in tells them plainly that this business cannot serve them. Many will not respond, and the ones who do will be comparing the experience against a competitor who wrote back properly.
The fix: answer in their language, in the minute
An assistant that reads and replies in the customer's language, answers the routine questions accurately, qualifies the enquiry and hands to whoever should take it with a translated summary turns a two day silence into a same afternoon conversation. The approach is set out in multilingual ai receptionist, and a sector example in multilingual customers and insurance enquiries. Start at try, see features, and the sector view sits under small business.