Blog
Two languages, one inbox, and the wait that costs you the job
An enquiry arrives on a Tuesday morning in Dutch. It is a good one, from someone who has already decided to buy something and is now choosing who from. It goes to the one person in the office who can handle it. That person is out on a job until Thursday.
By Thursday the customer has written to two other people, and one of them answered on Tuesday afternoon in schoolboy English.
You already know how the languages break down where you work, because you live in it. What is worth saying is that the expensive part is not the translation. Translation stopped being the hard problem years ago. The expensive part is the queue.
ABOUT A 10 MINUTE READ NOTHING TO BUY WRITTEN FOR SERVICE BUSINESSES ON THE COAST
The cost is a queue, not a dictionary
Watch what happens to a second-language enquiry in a small business.
It arrives. Whoever opens the inbox reads it, recognises the language, and decides it is not theirs. It moves, formally or by leaving it unanswered, to the person who handles that language. That person is not sitting waiting for enquiries, because in a business of this size they are also doing the work. So the enquiry waits, not for a translator, but for a colleague's afternoon.
Two consequences follow, and both are worse than they look.
The reply goes out late, and the customer has already moved. In a high value purchase, the shortlist forms in the first day. Being third to reply on a residency case or a property viewing is often the same as not replying.
Your best language becomes your only language. The path of least resistance is to answer in the language your available person speaks. Do that consistently and you quietly select your customers by which of your staff was free, which is not a strategy anyone chose.
None of that is fixed by a better translation tool. It is fixed by deciding, in advance and in writing, who answers what, how fast, and in which language.
The five places it breaks in practice
-
Nobody decided what language the reply goes in
Most businesses have never written the rule down, so the rule is "whichever language the person who picked it up prefers". That produces a British customer answered in Spanish, a Spanish customer answered in English, and an occasional apologetic mixture of both.
The rule is one line: reply in the language they wrote in. It is not the only possible rule, but it is the only one that never has to be interpreted, and an unambiguous rule is the whole point. Write it down, tell everyone, and put it above the inbox.
The one exception worth building in: if a customer writes in language A and then switches to language B, follow them. They are telling you something.
-
The first reply and the second reply are different jobs
This is the distinction almost nobody draws, and drawing it solves most of the problem.
The first reply is about speed. It confirms the message arrived, confirms someone real has it, says what happens next and when. Quality of language barely matters. Nobody has ever chosen a supplier because their acknowledgement was elegant.
The second reply is about quality. It contains the answer, the price conversation, the caveat, the thing they will hold you to. Here the language matters enormously, because a mistranslated condition is a dispute six weeks later.
Split those two and you can be fast where speed is free and careful where care is expensive. You can write acknowledgement templates in both languages today, by hand, in about an hour, with no software involved.
-
The vocabulary that does not survive translation
Every sector has thirty words that a general purpose translator will render into something that sounds correct and means nothing.
On this coast the obvious ones are administrative. Empadronamiento is not "registration". NIE is not "tax number". Escritura is not "deed" in the sense a British buyer will assume. Comunidad, derrama, nota simple, IBI, autonomo. A machine will translate every one of them into a plausible English word, and your customer will make a decision based on the plausible word.
Agree the glossary once. Twenty to forty terms, with the agreed rendering in each language, and a short note where there is no real equivalent and you have to explain rather than translate. This is one hour of one afternoon and it is the highest value hour anybody spends on this problem. It improves human replies and machine ones equally, and it is the thing you hand to any system you ever buy.
-
Speaking a language you cannot then continue in
The worst outcome on this page, and the easiest one to buy by accident.
An automatic reply in flawless Dutch is a promise that this conversation happens in Dutch. If nobody at your end can hold the next three messages, you have converted a mild disappointment into a real one. Answering slowly in English is recoverable. Answering instantly in a language you then abandon is not.
Only open a language you can close. If you cannot staff it, say so early and in plain words: we work in English and Spanish, and we are happy to continue in either. Customers on this coast are used to that sentence and nobody is offended by it.
-
Your internal record ends up in two languages
Six months later somebody searches the system for what was agreed and finds half of it in one language and half in the other, and neither in the language of the person now looking.
Pick one language for the internal record and keep the customer's own words alongside it, unaltered, so nothing is lost. What you must not do is let the record itself drift bilingual by accident. That is how a quote gets honoured at the wrong figure.
READ
The five things to write down before you buy anything
ALL FIVE ARE FREE ALL FIVE FIT ON ONE PAGE
- The language rule. One sentence, decided and visible.
- Acknowledgement templates, in both languages, saying what happens next and by when.
- The glossary. Twenty to forty terms, agreed, in one shared document.
- The escalation line. Who a second-language enquiry goes to when the usual person is out, named, not implied.
- The named reviewer. One person who reads anything going out in the language they are strongest in, before it goes.
You can do all five on a Thursday afternoon with a document and no budget, and you should do them before anyone sells you a system. That includes us. A system laid over an undecided process automates the indecision.
Count three things for two weeks before you change anything
Do this by hand. It is dull and it takes ten minutes a day.
- How many enquiries came in.
- In which language, and through which channel, because email, the form and WhatsApp behave differently.
- How long the first reply took. Not the full answer. The first human acknowledgement.
Two weeks of that is a baseline. Without it you cannot tell whether anything you change afterwards worked, and you will end up arguing about impressions. With it, the argument is over in a minute.
Most owners who do this are surprised twice: by the split, which is rarely what they assumed, and by the reply times on the second language, which are usually worse than the first by more than they would have guessed.
READ
What a system adds, and what it does not
Once the five decisions exist, software has something to work with. Four things change, described by what they change for you.
The wait on the first reply disappears. Every enquiry gets a correct acknowledgement in the right language immediately, with what happens next and by when.
The second reply arrives as a draft, not a blank page. Written against your glossary and your previous answers, in the customer's language, for your reviewer to correct and send. The person still sends it. They no longer start from nothing at eight in the evening.
The record stays in one language, with the customer's original preserved next to it.
Sorting happens before a person reads it. An enquiry that is a supplier, a recruiter or a genuine buyer looks different, and the genuine buyer can reach a person first.
And what it does not do. It does not remove the reviewer, and any supplier who tells you it does is selling you the version that goes wrong in public. It does not make you good at a language you do not have. And it does not fix a business that is slow in its own first language, which is worth checking before you spend anything.
If that is the shape of your problem, it sits in operations systems, the half of our work that takes repetitive work off the desk rather than bringing customers in.
Why we are the ones writing this
We work in two languages by default. Every page on this site exists in English and in Spanish, written in each rather than translated from one, and neither version ships without the other. The thing we learned doing it is the sentence we now repeat to clients before they sign anything: two languages doubles the review, not the production.
Producing the second language is cheap. Checking that it says the same thing, in words a native speaker would use, is where the hours go. That cost is real, it lands on a person, and it belongs in the scope from the start rather than surfacing in month two.
We do not publish client results, here or anywhere. The reason is on the case studies page.
If the wait is the problem
Do the five decisions first. Then count for two weeks. If after that the numbers still say the wait is costing you work, that is a conversation worth having.
Bring the two weeks of counting if you have it. We take it from there.
Read next
- Operations systems, the family this sits in, and the paid pilot with a test signed before any build money is spent.
- What ChatGPT says about your business, on being found in each language before any of this starts.
- Why AI projects stall in month three, on what happens if you buy the system before making the five decisions above.
- The blog index, with the three strands and the questions we have not answered yet.
- Contact, to book a conversation or send a short message instead.