Multilingual

Six languages,
one shared queue.

The Leodesk agent interface ships in English, Spanish, French, German, Japanese and Italian. Each agent picks their own — so a team spread across three countries can work the same inbox, each in the language they think in.

The short version

Support teams stopped being monolingual long before their tools caught up. Most help desks treat language as a workspace-wide switch: someone picks one, everyone else works in a second language all day. Leodesk does not. Language is an individual preference, the queue underneath it is shared, and nobody has to agree on which language the team runs in.

That is the part we have finished. The customer-facing side we have not — the widget your customers type into and the emails they receive are still English-only. Everything below separates the two clearly.

Language is a per-agent setting, not a workspace one

Every agent sets their own language in Preferences, and the choice applies only to them. It is not an admin decision, not locked to the workspace, and needs no migration or separate instance.

The practical effect is that one ticket queue can be read in several languages at once. A ticket assigned by an agent working in German is picked up by an agent working in Japanese, and each sees the same ticket in their own interface. The data does not change — only the labels around it do.

What localises with the interface

Translating an application badly usually means doing the buttons and leaving the data looking foreign. What follows the agent's language in Leodesk:

Ticket status, priority and channel labels — the values agents read and filter on all day, not just the menus around them.
Dates and times, formatted for the chosen language rather than a single fixed format.
Relative timestamps — how long a ticket has been waiting, written the way that language writes it.
The application surfaces: inbox and ticket views, reports, the knowledge base editor, contacts and settings.

What is not translated yet

The customer-facing side of Leodesk is not localised. To be specific:

The chat widget your customers type into renders in English.
The customer portal renders in English.
Outbound email templates are English-only.

None of these follow the agent's language setting, because they are not shown to agents. So a Spanish-speaking agent can work the queue entirely in Spanish today, but the widget their customer wrote in and the notification email that customer receives are still English.

Why we are saying this out loud

Customer-facing localisation is the obvious next step, and it is not shipped. We would rather you read that while evaluating than discover it in week two of a rollout. If English-only customer surfaces are a blocker, tell us before you commit.

AI assist can translate chat in real time

There is one place where language crosses between your team and your customers today: live chat. With AI assistance in live chat enabled, Leodesk translates a visitor's messages inline as they arrive, and offers translate-before-send in the composer, so an agent writes in their own language and sends in the visitor's.

It is off by default. The toggle is admin-gated, switched on deliberately at the workspace level rather than appearing on its own. See pricing for which plans include AI assist.

The six languages

The agent interface and this marketing site are both published in all six:

EnglishEspañolFrançaisDeutsch日本語Italiano

Surface	Localised today	Who sees it
Agent interface	Six languages	Your team
Status, priority & channel labels	Six languages	Your team
Dates & relative times	Six languages	Your team
Marketing site	Six languages	Anyone
Chat widget	English only	Your customers
Customer portal	English only	Your customers
Outbound email templates	English only	Your customers
Live chat translation (AI assist)	Opt-in, off by default	Both

FAQ

Working in six languages.

What is translated, and what is not.

Read the docs

Which languages is the Leodesk agent UI available in?

Six: English, Spanish, French, German, Japanese and Italian — across the agent-facing application, including inbox, reports, the knowledge base editor and settings.

Is language set per agent or per workspace?

Per agent. Every agent chooses their own in Preferences, and it only affects what they see. There is a workspace default for new agents, but any agent can override it — so one queue can be worked in three languages at once.

Does the chat widget or the customer portal appear in my customer's language?

Not yet. The chat widget, the customer portal and outbound email templates are not localised, and render in English whichever language your agents use.

Can Leodesk translate a conversation for me?

AI assist can translate live chat in real time — visitor messages inline, plus translate-before-send in the chat composer. It is admin-gated and opt-in, and off by default.

Do ticket statuses, dates and times localise too?

Yes. Status, priority and channel labels are translated with the rest of the interface, and dates, times and relative timestamps follow the agent's language rather than one fixed format.

Is the Leodesk website available in these languages as well?

Yes — this marketing site is published in the same six languages, switchable from the language menu in the navigation.

Give every agent their own language.

Start free for up to 3 agents. No card, no sales call to get started.

Try Leodesk

Six languages,one shared queue.