Answering customers in 50 languages without hiring for it
Language is the cheapest expansion lever most stores never pull. What actually changes when your support answers in the customer's own language, and what to watch out for.
Growth · 27 June 2026 · 6 min read
Most online stores are already international whether they planned it or not. Traffic arrives from countries the founder has never visited, and a percentage of it bounces for a reason nobody measures: the shop only speaks one language, and the visitor does not.
Hiring for this has always been the blocker. A native speaker per market is a real salary, and you cannot justify one until the market is already producing revenue, which it will not do until someone can answer questions in that language.
What changes when the agent detects and matches language
The mechanic is simple. The customer writes in their own language, the agent detects it and replies in the same one, using the same product data and policies it uses for everyone else. No separate knowledge base per market, no translated FAQ to maintain.
The effect is larger than it sounds, because language does not just affect comprehension. It affects whether someone trusts you enough to pay you.
- Customers ask more questions, because asking feels less effortful
- Pre purchase objections surface where you can answer them instead of silently losing the sale
- Fewer returns caused by misread specifications
- Markets you were not targeting start showing up in the numbers
The parts that still need care
Automatic language handling is not a licence to stop thinking about the market. A few things do not translate on their own.
- Product names and brand terms should usually stay untranslated, not become something unrecognisable
- Sizing, units and dates differ by region, and a technically accurate translation of the wrong unit is still wrong
- Legal text, returns rights and consumer protection differ by country, and those answers should come from written policy
- Formality matters. Several languages encode politeness in ways English does not, and the default register should be deliberate
Translate the conversation, not the commitments. Anything that is a legal or financial promise should be written down per market, not generated on the fly.
How to check it is actually working
Do not take the language count on the pricing page as evidence. Test it the way a customer would.
Pick your three largest non English markets. Ask a real question in each language, including a specific product question and an awkward policy question. Read the replies, ideally with someone who speaks it. You are checking that the answer is correct, that it sounds like a person rather than a translation, and that it did not quietly drop a detail the English version includes.
The economics
The reason this is worth doing early is that the cost does not scale with the number of languages. One agent covers all of them at the same price, so the decision is not which markets can justify a hire, it is simply whether you want to answer people who are already visiting.
For most stores the honest answer is that a handful of markets were always there, quietly bouncing, and nobody had a way to see it.
Start your free trial · More guides