Skip to content

Blog · Business automation

Supporting customers in several languages with an agent: what changes and what does not

What a multilingual agent really solves in support, what still comes from the same system in any language, and where not to translate on its own.

Equipo editorial de Meteor Published 2 min read

Can an AI agent support my customers in several languages?

It can answer in the language it was written to, and that solves a real problem in tourism, export and any business with customers abroad. What does not change with the language is the source: availability, price and order status come from the same system in Spanish or in German, so a multilingual agent with disconnected data gets it wrong just as precisely in five languages. And some text is better left untranslated: anything legal, anything fiscal, and product names.

In a beach hotel, in a company that exports, or in any business selling abroad, language always shows up at the same moment: somebody writes in English on a Sunday and the person who speaks English comes in on Monday.

A multilingual agent solves something concrete there. But it is worth being precise about what, because the language is the easy part.

What changes

That the answer arrives at the moment, in the language it was asked in. Nothing more, and that is not nothing: somebody who writes in their language and gets an answer in their language stops wondering whether this business can look after them.

In hospitality it shows most, because the alternative is having one speaker per language on every shift, which does not exist.

What does not change

The source. Availability, price, order status and the cancellation policy come from the same system in Spanish as in German.

That is the part usually left out of the conversation about languages, and it is the part that decides whether this is useful: a multilingual agent with disconnected data is wrong with the same precision in five languages. Which is why the integrations catalogue matters more than the list of languages.

Where not to translate

Three things: anything legal, anything fiscal, and product names.

The first two because an approximate translation of a contractual condition is a different condition, and nobody reviewed it. The third for a more practical reason: a translated product stops being searchable, and the customer will not find it later in the store or on the invoice.

The limit stays the same

It does not move with the language. A query gets answered; a complaint, an exception or a negotiation gets handed over. The support Met makes that distinction by the kind of question, not by the language it arrived in.

One thing worth settling first: who receives a case in Portuguese when it has to be escalated. If the answer is “not sure”, the multilingual agent brought the problem forward instead of solving it.

And internally too

The first use is often the team rather than the customer: whoever works with suppliers abroad asks the same repeated questions, only in another language. The full journey is in the WhatsApp support solution.

The limits

What this article does NOT answer

We would rather say it here than leave you hunting for something that is not there.

Keep going

What this article mentions, in detail

The integrations, the Mets and the automations named above, each with its own page.

Frequently asked

Questions on this topic

No: what you configure once is what it answers, where the data comes from and what it hands over. Language is how it is said, and that does not multiply the setup work.

Best left as they are. A translated product stops being searchable and the customer will not find it later in the store or on the invoice.

It is, and that is often the first use: a team working with suppliers abroad asks the same repeated questions, only in another language.

Keep reading

Other articles on the same thing

Want to see it running on your operation?

We show it with your own accounts connected, not with a canned demo.