Dixa AI conversation translation: how Copilot translates both ways, and where it slips

Kira
Written by

Kira

Katelin Teen
Reviewed by

Katelin Teen

Last edited November 21, 2026

Expert Verified
Hand-drawn illustration of a customer holding a phone and a support agent with a headset at a laptop, exchanging speech bubbles with shopping bag and globe icons, arrows going both ways, and the Dixa logo on an orange blob in the corner
TL;DR

Dixa's AI conversation translation is part of Copilot, an add-on Dixa lists at €39 per agent per month on every plan. An agent can translate a whole conversation into their own language, turn on auto-translation of incoming messages for each channel, and press Translate reply to send their answer in the customer's language. It covers 53 languages, and it works well for a team that gets conversations in languages nobody on shift speaks. The part to understand before you rely on it is the conversation language: on email, Dixa sets it from the first text message, inbound or outbound, and never checks it again, and that language decides what Translate reply translates into.

On Zendesk, Freshdesk, Gorgias or Help Scout, an AI helpdesk agent such as eesel writes the reply in the customer's language from the start; it doesn't connect to Dixa. With the eesel CLI, an AI coding agent can upload approved help articles and ask test questions in each language before anything goes live, though an admin still has to approve the helpdesk connection.

What is Dixa AI conversation translation?

It is the translation built into Dixa's agent workspace, so an agent can read and answer a customer in a language they don't speak without copying text into another tool. Dixa ships it inside Copilot, its add-on for human agents (an agent assist tool), next to AI drafts, summaries and suggested tags. Dixa's pitch is short: "Customers write in their language. Agents respond in theirs. Copilot translates both ways, instantly." The customer-facing side is Mim, Dixa's AI agent, which handles languages its own way (below).

I build features and AI agents at eesel, so I read a translation feature by asking what triggers it, which language it translates into, and what is left for a person. Dixa's AI translations article splits it into four pieces.

  • Translate the conversation. From the Translate menu at the top of a conversation, the agent picks a language, and every message, existing and new, inbound and outbound, shows translated with a "Translated from" label. Show original reverts it.
  • Translate one message. Each message has its own translate icon, which forces a translation even when auto-translate refuses with "conversation is already in ". That happens when one message mixes languages.
  • Auto-translate inbound. Each agent can turn on automatic translation of incoming messages per channel.
  • Translate the reply. The agent writes in their own language and presses Translate reply in the AI toolbar, or the one-click Quick Translate, which translates into the conversation's language.
A Dixa conversation in Danish between a customer named Adriene and an agent, with the Translate menu open at the top showing a search box and recently used languages English, Danish, Dutch (Flemish) and Italian
Translate sits at the top of a conversation, as shown in Dixa's AI translations article.
A Dixa conversation shown in Italian, where every message from the system user, the customer Petra and the agent Kenneth carries a Translated from English label
Every translated message says so, so nobody mistakes a translation for what the customer typed. From Dixa's help center.

How to set up AI translation in Dixa

Translation needs Copilot on the account; after that, most of the setup is per agent.

  1. Add Copilot. It is a paid add-on on the Team, Professional and Enterprise plans, billed per agent (pricing below). Dixa's Copilot bundle article lists AI translations among its tools.
  2. Each agent picks their language. Under Settings > Preferences > Agent Co-pilot, set Language for summaries and auto-translation. This sits under the Personal settings, so it is one setting per agent, not one for the team.
  3. Each agent chooses auto or on demand per channel. In the same screen, the Translation table sets email, chat and messaging to Automatically or On demand.
  4. Show agents the reply flow. Read the translated thread, write the answer in your own language, then press Translate reply or Quick Translate before sending. Agents in Dixa's keyboard shortcuts beta can assign a shortcut to Translate reply.
  5. Check the language on test conversations. Send a test email in each language you get most and look at what Dixa set as the conversation language before agents rely on Quick Translate (next section).
Dixa's Preferences page with the Agent Co-pilot tab open, showing Language for summaries and auto-translation set to Danish, and a Translation table where email is set to Automatically and chat and messaging to On demand
Auto-translate lives in each agent's own preferences, per channel, from Dixa's help center.

Then have someone who reads the language check five translated replies against your support translation glossary. I'd do that before trusting it on refunds or anything with a policy number in it.

How does Dixa pick the conversation language?

Dixa sets a language on every conversation, and the rules differ by channel. Per Dixa's language detection article:

  • Email: the language is set from the first text-based message, "whether inbound or outbound", reading the beginning of the body so signatures and quoted replies don't weigh too much. "Language detection is done solely on the first text-based message of the conversation and not re-analyzed on every back-and-forth message." Very short messages are ignored.
  • Chat and Dixa Messenger: the customer's browser language sets both the widget and the conversation language, and you can override the widget language.
  • Facebook Messenger, Instagram and WhatsApp: detected from the inbound text, and when confidence is low, "we'll fall back to English".
  • Forms and the API: Dixa doesn't detect it; you set the language when you create the conversation. An email or contact form conversation created without one gets detected on its next message.
Hand-drawn chart titled When Dixa sets the conversation language: email uses the first text message, inbound or outbound, never re-checked; chat uses the browser language, not what the customer types; WhatsApp and social read the message and fall back to English when unsure; forms and API: you set it, or none is set; that language picks the Quick Translate target, the CSAT survey, the quick reply set and language routing
One field, and four things follow it.

That field matters because other features read it. Dixa says the conversation language sets the CSAT survey localisation, the quick reply template set and routing on a global email address, and Quick Translate translates into it. So the cases to plan for are the ones where it is set wrong:

  • An outbound email in English. If an agent opens the email conversation, the first message is theirs, so the conversation can be set to English before the customer replies in Spanish.
  • A chat from an English browser. A customer on an English-language browser who types in Portuguese gets an English conversation.
  • A short WhatsApp message. A one-word "Hola" may be too short to detect, and when confidence is low Dixa falls back to English.

For a message that doesn't match, the per-message translate icon is the fix Dixa gives: it always forces the translation. Dixa's article doesn't say Translate reply can target a different language, so check the conversation language before you send.

Where does Dixa translation fall short?

It falls short where it leaves work to each agent: per-agent settings, a manual step on every reply, and an email language that is set once.

  • Settings are per agent. Auto-translation and the target language live in each agent's own preferences, so each new hire has to set it; Dixa doesn't describe a team-wide default.
  • Every reply is a manual step. Outbound translation is write, Translate reply, check, send. That keeps a person in control, which is right for most teams, and a busy agent who skips the step sends their own language.
  • Email language is set once. As above, a first message in the wrong language sticks for the life of the conversation.
  • Phone calls aren't translated as a whole. Dixa's article says it doesn't allow "the full translation of the entire phone call, as these can often consist of 100s of messages."
  • Translated knowledge articles go stale on new sections. Copilot's article auto-translation can re-translate a changed block, but "this does not work if you add any new sections to the default language article", so you re-translate the whole article.

None of this is a reason to skip it. It is a reason to put the Agent Co-pilot settings in onboarding and test how Dixa sets the language on each channel you use.

What are the other ways to handle languages in Dixa?

Besides Copilot translation there are four options: routing by language, Mim, a multilingual knowledge base, and an AI agent that writes in the customer's language. They solve different problems.

Route by language

If you have agents who speak the language, routing beats translating. Dixa's routing by language uses a Filters node in an email or Messenger flow to send each language to its own queue, and Dixa recommends filtering out lower-volume languages first and leaving your main language last. Dixa conversation routing covers flows and queues.

Mim, the customer-facing AI agent

Mim answers customers directly. Dixa's Mim page says it "detects the customer's language and replies in it, including the handoff message to your team", and the default instructions in Dixa's Mim getting started guide say "Always respond in the same language the customer is writing in." Mim is on every plan at €0.40 per conversation, whether it resolves it or hands it over. Dixa's AI agent covers what it answers.

A multilingual knowledge base

For self-service, enable more languages in Knowledge settings, add a language to an article and choose Auto-translate from its menu. This is also a Copilot feature. Multilingual knowledge base software compares the wider field.

An AI agent that writes in the customer's language

An AI agent connected to the helpdesk can draft the reply in the customer's language from the start, so nobody translates at the last step. eesel does that on the helpdesks it connects to (below); best AI for multilingual support lists other options.

What does your team need from translation?
Copilot's AI translationsEach agent sets their language and auto-translate per channel under Preferences, Agent Co-pilot. They read the thread translated, then press Translate reply before each send. Check what language Dixa set on email conversations.Copilot: €39 per agent per month, on every plan. 53 languages.
Route by languageAdd a Filters node to your email or Messenger flow and send each language to its own queue, lower-volume languages first. Forms and API conversations need the language set when they are created.Language detection is built in. No translation needed.
MimDixa's customer-facing AI agent detects the customer's language and replies in it, handoff message included.On every plan, €0.40 per conversation.
A multilingual knowledge baseEnable languages in Knowledge settings, then Auto-translate each article. Re-translate the whole article after you add a new section.Article auto-translation is part of Copilot.
An AI agent that drafts in the customer's languageOn Zendesk, Freshdesk, Gorgias or Help Scout, eesel drafts or sends each reply in the language the customer wrote in, with a note for your team in yours. It doesn't connect to Dixa.eesel from $299 a month.

Pick what your team needs to see which Dixa setup handles it.

What does Dixa translation cost?

AI translations come with Copilot, which Dixa's pricing page lists at €39 per agent per month as an add-on to the Team, Professional and Enterprise plans. Copilot also covers AI drafts, conversation summaries, suggested tags and the writing assistant.

WhatTeamProfessionalEnterprise
Platform, per agent / month, billed annually€49€139Custom
Language detectionIncludedIncludedIncluded
Copilot (AI translations, drafts, summaries)€39 per agent / month€39 per agent / month€39 per agent / month
Mim AI agent (replies in the customer's language)€0.40 per conversation€0.40 per conversation€0.40 per conversation

For 20 agents on Team, the platform is 20 x €49 = €980 a month and Copilot adds 20 x €39 = €780, so €1,760 a month before any Mim conversations. Judge the €780 on everything Copilot does, including Dixa AI drafts and conversation summaries, and against what non-English AI support costs elsewhere. Dixa pricing covers the platform side.

Where does eesel fit?

eesel fits a team weighing a move off Dixa, or one running a second helpdesk next to it. eesel is an AI teammate that joins the tools a team already uses; on support it works in the helpdesk queue, learns from past tickets and is tested against them before it replies. On Zendesk, Freshdesk, Gorgias and Help Scout it writes the reply in the language the customer wrote in, so the translation step disappears rather than moving to a button.

Two published stories show the shape. Innr runs eesel on Freshdesk: when a customer writes in Dutch, German, English or French, eesel leaves a draft reply in that language as an internal note, and a person sends it. Koffer.ch gets a draft reply (a draft, not an internal note) in German, French, English or Italian, with Swiss spelling in German, and a person sends it.

eesel doesn't connect to Dixa: Dixa is not in eesel's helpdesk docs, so I can't tell you to connect it to your Dixa account. If you are staying on Dixa, Copilot's translations are the native answer, and my advice is the setup above: Agent Co-pilot settings in onboarding, and a test of how each channel sets the language.

Try eesel for replies in your customer's language

If you're comparing helpdesks partly on how they handle languages, try eesel on a trial of Zendesk, Freshdesk, Gorgias or Help Scout next to your Dixa evaluation. Start with drafts as internal notes in the customer's language, read a week of them, then decide what it may send on its own: what eesel does alone and what waits for a person's yes is set per action in actions and approvals. The free trial lets you watch it draft on real tickets before you pay.

The eesel helpdesk dashboard showing an overview of AI agent activity across connected support channels
Every draft and reply eesel made, in one place.

Try eesel on one language first, or compare options in best AI for Dixa.

Frequently Asked Questions

Does Dixa translate conversations automatically?
It can. Each agent sets a language under Settings, Preferences, Agent Co-pilot and can turn on auto-translation of incoming messages per channel (email, chat, messaging). Outgoing replies are still translated one at a time with Translate reply. Multilingual customer support covers the wider setup.
Which Dixa plan includes AI translation?
AI translations are part of Copilot, an add-on Dixa's pricing page lists at €39 per agent per month on the Team, Professional and Enterprise plans. Copilot also includes AI drafts and conversation summaries. Dixa pricing covers the plans.
How many languages does Dixa translation support?
Dixa's AI translations article lists 53 languages, from Afrikaans to Welsh, and says more are being added. Dixa's language detection, which sets the conversation language, recognises about 60. Best AI for multilingual support compares other tools.
How does Dixa detect the language of a conversation?
It depends on the channel. Email uses the first text message, inbound or outbound, and is never re-checked; chat uses the customer's browser language; WhatsApp and social read the message and fall back to English when unsure; forms and API conversations need the language set. Dixa conversation routing shows how to route on it.
Can Dixa translate phone calls?
Not as a whole. Dixa's translations article says it doesn't allow full translation of a phone call, since one call can be hundreds of messages. Mim on Voice, Dixa's AI phone agent in beta, speaks 16 languages. Dixa's AI agent covers Mim.
Can Dixa's AI agent answer customers in their own language?
Yes. Dixa says Mim detects the customer's language and replies in it, including the handoff message to your team, and its default instructions tell it to respond in the language the customer writes in. Mim is billed at €0.40 per conversation. Dixa AI deflection works through that cost.
Can eesel translate Dixa conversations?
No: eesel doesn't connect to Dixa. On the helpdesks it connects to, such as Zendesk, Freshdesk, Gorgias and Help Scout, it drafts or sends replies in the language the customer wrote in, which matters if you are weighing a move (see Dixa alternatives).

Share this article