The honest starting point
Visitors will write to you in their language regardless of what your team speaks — the only question is whether the experience is planned or improvised. A small team cannot staff five languages; it CAN localize the surfaces, run translation-assisted conversations with candor, and let the data show which language deserves real investment.
Layer 1: localize the widget surfaces
The launcher label, pre-chat form, and system messages are the first impression, and they are static strings — translating them is a settings task, not a staffing one. A widget that greets in the visitor's language and then says, honestly, "our team replies in English" outperforms one that pretends: expectations set beat expectations broken.
Layer 2: translation-assisted conversations, with candor
Machine translation is now good enough for support logistics — order status, how-tos, policy questions — and still risky for nuance, anger, and legal precision. The workable pattern: translate to read, reply simply, and be candid ("I'm using translation — tell me if anything reads wrong"). Short sentences, no idioms, no sarcasm; the same discipline that makes good chat writing also makes it translate cleanly.
Layer 3: translate the knowledge base by demand, not ambition
Do not translate 200 articles into four languages; translate the top ten into ONE — the language your transcripts and visitor locations actually show. Ten well-translated articles absorb most of that audience's repetitive tier (and give an AI assistant trained on them a real corpus to answer from). Expand only when the next language's demand shows up in the same data.
Layer 4: schedule the bilinguals you have
One bilingual teammate is a scheduling asset, not a translation department. Route their language's conversations to them when online (departments or routing rules do this mechanically), and let the offline form set honest expectations the rest of the day: "Spanish support replies within one business day." Protect them from becoming the permanent translator for every colleague — that road burns out your only speaker.
When to actually hire for a language
The trigger is in your transcripts: a language whose volume keeps growing, whose conversations convert or churn measurably worse than your primary language, and whose top questions are already translated — meaning the remaining gap IS the human. That is a hiring case a founder can read from the transcript history, not a guess.
Measure the gap you cannot see
The silent number: visitors from non-primary-language countries who open the widget and never type. Watch chat starts by visitor country before and after localizing the widget strings — the delta is the audience you were turning away at the door.