All posts
InsightsApril 20264 min read

Multilingual support as a competitive advantage in Europe

The EU has 24 official languages. Here's what it costs to cover them by hiring, and what changes when the agent already on shift can answer in all of them.

Tim de RooijVenture Lead

The language problem in European support

The EU has 24 official languages. Add the ones spoken outside it and any support team serving the continent is looking at a list it can't staff one-to-one.

The queue doesn't arrive evenly, either. Dutch and German come in all day. Finnish might arrive twice a week, at an hour when the one person who reads it is asleep.

What the usual fixes cost

Hiring a native speaker for each language works, and it's expensive. It also leaves gaps that have nothing to do with budget: one Finnish speaker is one person's working hours, one person's holiday, and one person's notice period.

English-only support is the other common answer. It serves the customers who write English comfortably. The rest tend to leave quietly rather than complain, which is why it looks cheaper than it is.

What translation changes

Support text is short, transactional and full of phrasing the same team has already used a thousand times. Machine translation handles that kind of text well. It isn't the tool for a contract or a brand campaign, and nobody should sell it as one.

The agent already on shift takes the Finnish ticket, reads it in English, writes the reply in English, and sends it in Finnish. Coverage stops being a hiring question and becomes a tooling one.

Two things decide whether that holds up in front of a customer.

The first is terminology. A support reply is full of words an engine must not improvise on — the name of the item, the currency, the label on the button in the settings menu. A glossary pins those, so the reply reads as though it came from someone who has played the game.

The second is register. German, Japanese, Korean and Chinese all mark formality, and an engine left to guess will eventually guess wrong in front of a customer.

What it doesn't fix

Translation doesn't give an agent cultural knowledge. It won't tell them that a phrase they use freely in English lands badly in Japanese, and it doesn't handle the escalation that needs someone who knows the market. Those still need people.

What it removes is the wait that exists only because the person who could answer doesn't read the language it arrived in.

See it on your own tickets.

Book a demo and bring a week of real messages. We load your terminology and run them while you watch.

Book a demo