Handling Enquiries in Five Languages Without Losing the Lead

Walk into the back office of almost any agency, hotel or clinic on the Montenegrin coast and you will find the same quiet problem: enquiries arrive in several languages, and the person best placed to answer is not always the person who sees the message first. A German family asks about a two-bedroom apartment in Tivat. A Russian-speaking buyer sends three voice notes on WhatsApp. A British couple fills in the website form at 23:40. A Serbian contractor emails about a partnership. All of it lands in the same inbox, and all of it is handled at whatever speed the available staff can manage.

Multilingual marketing gets plenty of attention — translated landing pages, localised ad copy, hreflang tags. Multilingual enquiry handling gets far less, and it is where most of the leakage actually happens. You can spend properly on campaigns in four languages and still lose the majority of those leads because the reply took two days and arrived in the wrong language.

This article sets out a workable system for small and mid-sized teams. It assumes you do not have a 24-hour multilingual call centre and never will.

Start by mapping what actually arrives

Before changing anything, spend two weeks logging every inbound enquiry against four fields: channel, language, topic, and time received. Most teams are surprised by the result. The language mix in the inbox rarely matches the language mix of website traffic, and the channel mix rarely matches what management assumes.

Typical findings along the Adriatic coast include:

• Messaging apps carry a disproportionate share of high-intent enquiries, while the website form carries more early-stage browsing
• Enquiries in one language cluster heavily in evenings or weekends because of the sending market's time zone and habits
• A language that barely registers in analytics can account for a meaningful share of enquiries, because those buyers browse in English but write in their own language
• Voice notes are common in some markets and almost absent in others

You cannot design routing rules sensibly without this map. Two weeks of manual logging is cheap and will shape every decision that follows.

Decide your language policy before your tooling

There is a difference between the languages you market in, the languages you reply in, and the languages you can hold a full sales conversation in. Confusing these three is the root of most multilingual failures.

A realistic policy for a coastal agency might be: market in English, Russian and German; reply in the language of the enquiry using prepared templates plus careful translation; hold full conversations in English, Russian and Montenegrin/Serbian, with German handled by a named colleague or partner. Write that down. Tell the whole team. It removes the paralysis that causes a German-language message to sit untouched for three days because nobody was sure whose job it was.

Be honest in your marketing about the conversation language

If you cannot sustain a full sales dialogue in a given language, do not imply otherwise. A short line on the contact page — "We reply in English, Russian and Montenegrin; for other languages please allow an extra day" — costs you almost nothing and prevents the far worse outcome of an enthusiastic first reply followed by silence.

Route first, translate second

Language detection is now good enough to be a routing signal rather than a manual step. The sequence that works:

1. Consolidate channels. Website forms, email, WhatsApp Business, Viber, Instagram and Facebook messages should all land in one shared inbox or CRM, not in five separate apps on five separate phones.
2. Tag by language automatically. Most shared-inbox and CRM tools can detect language or infer it from the form field, the campaign source, or the landing page the visitor used.
3. Route by tag to a named owner. Every language needs a primary owner and a backup. Not a team — a person.
4. Fire an immediate acknowledgement in the right language. This is the single highest-return change most teams can make.
5. Only then translate and compose the substantive reply.

The acknowledgement matters more than people expect. A buyer who submits a form at midnight and receives an instant, grammatically correct message in their own language confirming that a named colleague will respond by a stated time has already formed an impression of competence. The same buyer receiving nothing until Tuesday afternoon has, in many cases, already messaged two competitors.

Build a template library, not a translation habit

Machine translation is genuinely useful for understanding inbound messages and for drafting. It is less safe for outbound sales copy, particularly in property and healthcare where a mistranslated term about ownership structure, permits or clinical procedures creates real problems.

The efficient middle path is a library of pre-translated, human-reviewed templates covering the fifteen or twenty exchanges that make up most of your enquiry traffic:

• Acknowledgement and expected response time
• Request for qualifying details (budget, timing, purpose of purchase or stay)
• Availability confirmation and alternatives
• Viewing or consultation scheduling, including video call options
• Document and deposit requests
• Explanation of process steps specific to your sector and jurisdiction
• Polite follow-ups at defined intervals
• Graceful close when a lead goes cold

Have each template translated once by a competent native speaker, store them in the CRM, and let staff personalise the top and bottom lines. This gives you speed and accuracy simultaneously, and it means an English-speaking colleague can send a correct Russian holding reply without waiting for anyone.

Watch the register, not just the vocabulary

Formality norms differ sharply between markets. A German-language enquiry generally expects a more formal structure and clear factual detail. Russian-language property conversations often move to messaging apps and voice notes quickly and tolerate a warmer, more personal tone. British and Irish buyers frequently expect written confirmation of anything discussed verbally. Templates should reflect these differences rather than being literal translations of one original.

Make the CRM carry the language

Language should be a first-class field on the contact record, not a note buried in a comment. Once it is a field, several useful things become possible:

• Automated follow-up sequences send in the correct language without manual selection
• Reporting shows conversion rates by language, which often reveals that one market converts far better or worse than its lead volume suggests
• Ad spend can be reallocated between language markets on evidence rather than instinct
• Handovers between colleagues carry the context automatically

Add a second field for preferred channel. A contact who wrote via Viber usually wants to continue on Viber; replying by formal email often ends the thread.

Measure response time by language

Aggregate response-time averages hide the problem. Break the metric down by language and you will usually find one or two languages where the median reply time is several times the others. That gap is where your budget is quietly disappearing.

Track three numbers monthly: time to first acknowledgement, time to substantive reply, and reply rate within twenty-four hours — each split by language and channel. If a language market consistently underperforms on these, the honest options are to resource it properly, find a partner to cover it, or stop advertising in it. Continuing to buy traffic you cannot serve is the most expensive of the three.

Seasonal reality on the coast

Adriatic businesses face an additional wrinkle: the enquiry volume and the language mix both shift through the year. Summer brings a broader spread of nationalities and a higher share of short-notice, low-consideration enquiries. Shoulder and winter months skew towards serious buyers, investors and returning guests, often with longer, more detailed questions.

Plan staffing and templates around this. The templates that serve a busy July — fast, concise, availability-focused — are not the ones that serve a February investment enquiry requiring detail on ownership, taxation and timelines. Prepare both sets in each of your core languages before the season turns, not during it.

The minimum viable version

If the full system feels out of reach, start here:

1. One shared inbox covering every channel
2. A language field on every contact record
3. An automatic acknowledgement in each core language
4. Five reviewed templates per language
5. A named owner and backup per language
6. Monthly response-time reporting split by language

None of this requires expensive software or new headcount. It requires a decision about which languages you genuinely serve and a small amount of preparatory work. The return shows up quickly, because the leads were always arriving — they were simply waiting longer than they were willing to wait.