Translation

Set up Translation so members and staff can talk in different languages inside tickets and ModMail

Translation translates ticket messages between the member's language and your staff's language, so a Spanish-speaking member and an English-speaking helper can work through a ticket without either of them switching language. It works with every language your members write in. This page is for the admin who runs a multilingual community.

Translation inside tickets (Translate tickets) is an Enterprise feature and needs the Atlas switch at the top of AI assistant → Atlas. Translate ModMail and Polish staff replies are available on Pro and higher, on the same page while your server uses ModMail (see ModMail translation). Upgrade your plan

Go to AI assistant → Atlas → Translate tickets

Setup

Open the card

Go to AI assistant → Atlas → Translate tickets. It is in the Languages section of the What Atlas does tab.

Turn it on

Switch on the Translate tickets card.

Check your staff's language

Your staff's language starts as Same as bot language, the language set under General → Bot language. Pick another language if your team reads a different one.

Choose what to translate and save

Choose Both ways or Member messages only under Translate, then click Save changes in the bar at the bottom of the page.

Settings

Translate tickets

SettingValuesDefaultWhat it does
Translate tickets (card switch)On, OffOffTurns ticket translation on for this server
Your staff's languageSame as bot language, or one of 20 languages: Arabic, Chinese, Czech, Danish, Dutch, English, Finnish, French, German, Hindi, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Russian, Spanish, Swedish, TurkishSame as bot languageMember messages are translated into this language. Same as bot language follows the bot language (English when it cannot be used)
TranslateBoth ways, Member messages onlyBoth waysBoth ways translates member messages for staff and staff replies for the member. Member messages only translates only what members write, into your staff's language

A server that chose Staff replies only earlier sees it as a third option until it picks another one.

Staff replies are translated into the language the member most recently wrote in, so they start once the member has written in their language. The ticket remembers that language however long the member takes to answer, and switches when the member writes in another one.

Languages

There is no language list to manage: Atlas recognizes the language of every member message and translates any language that differs from your staff's language. Messages already in your staff's language are left as they are.

Translation limit

Go to AI assistant → Atlas → Translation limit

The AI assistant → Atlas → Translation limit card, in the Limits and who Atlas skips section, caps how many characters are translated each month.

SettingValuesDefault
Translation limit5,000, 10,000, 25,000, 50,000, 100,000, 250,000, or 1,000,000 characters a month10,000

The card shows how many characters were translated this month. Translation pauses for the rest of the month (it restarts on the 1st, UTC) once the limit is used. Ticket and ModMail translations share the limit. The card is Enterprise; on Pro, ModMail translation uses the default of 10,000 characters a month. Translations also draw AI tokens from the bot owner's monthly allowance.

How Atlas translates

Atlas handles the details for you:

  • It waits about 5 seconds before translating, so a member can fix or delete a message first. ModMail member messages are translated at once instead, and translated again if the member edits them.
  • In ticket channels, a text-only message is replaced by a translation card, and a message with files gets the translation as a reply instead, so the files stay. ModMail works differently: see What staff and members see.
  • Messages over 2,000 characters are not translated at all: there is no card, no reply, and no note in the alerts channel, and staff see only the original. This applies to member and staff messages in ticket channels and to ModMail member messages. Messages up to 2,000 characters are translated.
  • When Atlas is not sure enough of a translation, it posts nothing in the ticket and leaves a Low-confidence translation note in your alerts channel instead (at most once a day per ticket).

Messages Atlas skips

Atlas skips messages that have nothing to translate: messages that are only code, bot commands, messages that are only emoji, messages that are only links, and repeated phrases. Short messages are translated, so danke or merci reach your staff too.

What happens

  1. A message arrives in a ticket.
  2. Atlas recognizes its language. Messages already in your staff's language are left alone, and Translate decides whether messages from that sender are translated at all.
  3. After a short wait, the translation is produced.
  4. The translation is posted in the ticket:
    • A text-only message is replaced by a 🌐 Message Translation card that shows the author and time, then the original text under its language flag and code (for example 🇪🇸 ES), then the translation under your staff language's flag and code.
    • A message with files gets a reply with the translation, so the files stay.
  5. With Both ways, staff replies are translated into the language the member most recently wrote in.

The cards show language codes and text only; no confidence score is shown to members. Notes about translations post in the AI alerts channel set under General → Where the bot posts (your logs channel when it is not set).

Per-ticket control

Staff can pause or resume translation in one ticket with /translation enabled:<True|False>. The command only works inside a ticket channel, only for staff, and only when the Atlas switch and Translate tickets are both on.

Atlas does not translate tickets from members on AI assistant → Atlas → Keep Atlas away from, or tickets opened from a panel button that turns Atlas off, in either direction.

ModMail translation

Go to AI assistant → Atlas → Translate ModMail

ModMail conversations have their own card, available from Pro: AI assistant → Atlas → Translate ModMail, in the Languages section. It is shown while your server uses ModMail, and needs the Atlas switch.

SettingValuesDefaultWhat it does
Translate ModMail (card switch)On, OffOff (until you change it, member messages follow Translate tickets)Turning it on or off turns both switches below on or off. The card shows as on while either of them is on
Translate member messagesOn, OffFollows Translate tickets until you change itShown while the card is on. Staff see a translation in the ModMail ticket channel when a member writes in another language
Translate staff repliesOn, OffOffShown while the card is on. Staff replies are translated before they reach the member's DMs, into the language the member last wrote in, however long ago that was
Your staff's languageSame as on Translate ticketsSame as bot languageShown on this card while it is on and Translate tickets is not in use; one setting serves both cards
Polish staff repliesNone, Light, Medium, HighNoneTidies up staff replies before they are sent to the member. Light fixes grammar, punctuation, and filler words; Medium edits for clarity and conciseness; High rewrites for brevity and polish; None sends exactly what staff wrote. Works with or without translation. The original text is kept

What staff and members see

  • ModMail member messages: in ModMail, the translation is added to the member's message in the ModMail ticket channel, a few seconds after it arrives, under the original text, with a small line naming both languages (for example 🇧🇷 PT → 🇺🇸 EN), so one card holds both. If the member edits a ModMail message, it is translated again. A ModMail member message over 2,000 characters is not translated at all, the same as in ticket channels. In ModMail only, when the member's card cannot hold the translation (the message was relayed across more than one card, or the card has no room left), the translation is posted as a separate reply to it instead. This fallback never applies to ticket channels, where messages over 2,000 characters are simply not translated.
  • Staff replies: the member gets only the reply in their language, translated and polished in one step, so Polish staff replies also applies to the translated text. When a reply is translated, its card in the ticket channel shows the reply in your staff's language with what the member got under it. With Polish staff replies on, both versions are polished (if the polished version in your staff's language fails a check, the top one shows what the staff member wrote); with it off, the top one is exactly what the staff member wrote. A reply over 1,500 characters shows only what the member got. If a translation is not reliable enough to send, the member gets the reply in your staff's language instead, polished when that is on and the reply is up to 1,500 characters.
  • Closing a ticket while a staff reply is still on its way to the member waits for it, for up to 45 seconds: a ModMail reply being translated, polished or sent, or the translation of a staff message in a ticket channel. The member gets it first, then the ticket closes, and the closing message (or your private /close reply) says it is waiting for the last reply. In ModMail, a reply that could not be sent before the close gets a ❌ reaction.
  • The transcript keeps each member message with its translation, and each staff reply as the member got it.

Worked example: a bilingual community

A German gaming community has English-speaking moderators and a large Spanish-speaking player base. The bot language is English. These are this community's choices, not the defaults, which are in the Settings tables above.

  • Your staff's language: Same as bot language (English)
  • Translate: Both ways, so moderators' replies reach Spanish speakers in Spanish
  • Translation limit: 50,000 characters a month, raised from the default of 10,000

A player writes no puedo entrar al servidor desde la actualización. A few seconds later a 🌐 Message Translation card shows the Spanish original and I can't join the server since the update. The moderator replies in English, and the bot posts the Spanish translation for the player. When a player posts a screenshot with a German caption, the translation arrives as a reply, so the screenshot stays.

Limits and gotchas

Translation is billed twice: characters against the Translation limit and tokens against the owner's AI allowance. Every member message in a language other than your staff's costs a translation, short ones included.

  • Messages longer than 2,000 characters are never translated, in ticket channels or from ModMail members. There is no separate reply for them.
  • Members on Keep Atlas away from are never translated.
  • Translation needs the Atlas switch. Turning Atlas off stops ticket and ModMail translation alike.
  • In tickets opened by email, staff replies are not translated automatically. With Translate tickets on, the draft card offers a Translate button when the reply is in another language than the customer writes in, and staff pick which version is emailed. See Email Inbox.

Troubleshooting

SymptomCauseFix
Nothing is translatedTranslate tickets or the Atlas switch is off, the owner's plan is not Enterprise, or the monthly limit is used upCheck both switches, the plan, and the Translation limit card
One member is never translatedThey are on Keep Atlas away from, or their ticket came from a panel button that turns Atlas offRemove them from the list, or check the panel button
Staff replies are not translatedTranslate is Member messages only, or the member has not written in their language yetChoose Both ways, and wait for the member's first message
ModMail staff replies reach the member untranslatedTranslate staff replies is off on the Translate ModMail card, or the member has not written in their language yetTurn it on, and wait for the member's first message
Translations go into the wrong language for staffSame as bot language follows the bot languagePick Your staff's language explicitly
Translations are sometimes missingAtlas was not sure enough of themCheck your alerts channel for Low-confidence translation notes
/translation replies with TC017It was used outside a ticket channelRun it inside the ticket
/translation replies with TC002The user is not staffGive them a configured staff role
/translation replies with TC018The Atlas switch or Translate tickets is off, or translation is already off for that ticketTurn both on first
/translation replies with TC012The enabled option was left outRun /translation enabled:True or enabled:False

Common questions

Which plan do I need? Enterprise for translation in tickets. ModMail translation and Polish staff replies start at Pro.

Which languages are supported? Every language your members write in. Your staff can read translations in one of 20 languages: Arabic, Chinese, Czech, Danish, Dutch, English, Finnish, French, German, Hindi, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Russian, Spanish, Swedish, and Turkish.

Does the member see the translation? Yes. Translations are posted in the ticket channel, as a card or a reply, where both the member and staff can read them.

Can staff turn it off for one ticket? Yes, with /translation enabled:False, and back on with /translation enabled:True.

Does it translate my bot's own messages? The bot's interface language is a separate setting, General → Bot language. Translation handles what members and staff write. By default your staff's language follows it.

Can it clean up staff replies without translating them? In ModMail, yes: set Polish staff replies to Light, Medium, or High and leave Translate ModMail off.

Can ModMail translate only what members write? Yes. Turn on Translate ModMail, then turn off Translate staff replies. Staff see translations of member messages, and members get staff replies exactly as written (polished, if Polish staff replies is not None).

Are short messages like "thanks" translated? Yes. Only messages with nothing to translate (code, commands, emoji, links) are skipped.

Last updated on

On this page