Multilingual conversations: translate any conversation with one click

Multilingual conversations in Deskwoot let your team support customers in any of 29 languages without speaking each one. The customer writes in their language. You hit the Translate button at the top of the conversation. Deskwoot renders the transcript in your dashboard language, and any reply you send is automatically translated into the customer's language before it goes out.

Why on-demand, not automatic

We don't auto-translate every inbound message. Two reasons. First, short messages and one-liners often misclassify by automatic language detection ("ok" is technically English, French, Polish, and a dozen other things). Second, every translation costs you one AI conversation credit, and on a busy inbox that adds up fast even when half the conversations are already in your language. Translating only when you click puts the cost decision in your hands.

Supported languages

29 in total: English, German, French, Spanish, Portuguese, Italian, Dutch, Polish, Russian, Arabic, Turkish, Hindi, Thai, Vietnamese, Swedish, Danish, Norwegian, Finnish, Ukrainian, Czech, Romanian, Hungarian, Greek, Hebrew, Indonesian, Malay, Japanese, Korean, Chinese.

How it works

Open any conversation. If the customer is writing in a language different from your dashboard language, you'll see a Translate toggle at the top of the conversation panel. Click it. Deskwoot translates every message in the transcript into your language, and from that moment on, every reply you send goes back out in the customer's language. The original text stays in the database, so the audit trail is intact in both languages.

Where you'll see it

• Inbound message: after you hit Translate, the translation renders under the original. A small flag icon shows the detected source language; click it to flip back to the untranslated view.
• Outbound reply: you type in your dashboard language. Deskwoot translates the outgoing copy to the customer's language before send, and shows you a preview so you can verify before clicking Send.
• Per-conversation toggle: the Translate button at the top of the conversation is sticky for that thread. Other conversations on the same inbox stay untranslated unless you click Translate on them too.

What we don't translate

Private notes between agents stay in whatever language you wrote them. Macros and canned responses stay as you saved them; if you want a German version of a macro, save a separate macro in German. The chat widget intro copy can be configured per-locale in Settings → Inboxes.

Quality and brand voice

Translations run on Claude Haiku 4.5. The prompt includes your brand voice rules (no em-dashes, no marketing fluff, no filler openers) so the translated output reads like your team's actual tone, not generic machine translation. The model preserves product names, company names, and code blocks verbatim.

Billing

Each conversation you translate counts as exactly one AI conversation per calendar month. Translating ten messages inside the same conversation in the same month is still one charge, not ten. Help Center article translation is a separate feature, billed at $0.06 per article translation. See the AI usage billing article for the full breakdown.

Privacy and data residency

Translation calls run on Deskwoot's EU-resident AI infrastructure under our Data Processing Agreement with Anthropic. No message content leaves the EU. We don't retain the translation prompt or response beyond the request lifecycle. If your DPA requires zero LLM use, you can turn the multilingual feature off per-inbox.

Plan availability

Available on the Business plan and above. Startup plan customers see the Translate button locked with an upgrade prompt.

How to enable it

1. Open any conversation in your inbox.
2. If the customer is writing in a different language, you'll see a Translate toggle at the top of the conversation panel.
3. Click it. The transcript translates in place; replies you compose go out in the customer's language until you toggle it off.

That's it. No setup, no per-inbox configuration, no admin permissions needed.