Translations and multi-language inbox

Inbox translation in Arino One shows inbound messages in your own language automatically, so a support team can handle conversations in French, Arabic or Chinese without every agent needing to speak the language. Each agent turns it on individually from Settings → Translations, choosing a display language; there is no workspace-wide toggle that forces one language on everyone, because the point is that different agents can each read the same inbox in the language they're comfortable in.

Turning it on

1. Go to Settings → Translations.
2. Under Inbox translation, pick a display language from the dropdown — the list covers English, Romanian, Russian, Ukrainian, Spanish, French, German, Italian, Portuguese, Polish, Dutch, Turkish, Arabic and Chinese.
3. Switch on Translate inbound messages into my language.
4. The setting saves instantly — no separate save button, no page reload required.

From that point, an inbound message arriving in a language other than your chosen display language shows translated text in the conversation view, with a small control to reveal the original wording if you need to check the source text — for example, to confirm a term was translated the way you'd expect, or to copy an exact phrase for a template.

How it's scoped

Translation preference is stored on the individual agent's profile, not at the workspace or instance level. That means:

• Two agents in the same inbox can each have a different display language and both see translated conversations correctly in their own view.
• Turning translation on for yourself doesn't change what any other agent sees.
• Contacts are never shown a translated version of what they sent — translation only affects how an inbound message is displayed to your team, not what's stored or what's sent back to the contact (composing a reply is a separate action, not automatically translated outbound unless you write it in the target language yourself or use a template).

Cost and metering

Translation is AI work, and Arino One meters it the same way as other AI-assisted features: each message translated draws from the shared AI credit bucket for your instance, whether that bucket is funded by the managed Lovable AI option or your own bring-your-own API key. There is no separate Arino markup layered on top of the underlying AI provider cost — you pay for the AI usage itself, and the $50/month instance connection and management fee is unrelated to translation volume.

Settings → Translations shows a running usage panel for the current month:

Use this to sanity-check that translation volume matches your expectations, particularly after onboarding a team handling a new language, before that shows up as a line on the AI usage bill. See usage and message costs for how AI metering is billed alongside per-message Infobip pass-through costs, and AI and API keys for the difference between managed AI and bringing your own key.

When translation isn't the right fix

Translation solves reading comprehension for an agent handling one-off conversations in a language they don't know — it doesn't replace hiring native-speaking agents for high-volume languages where nuance, tone and cultural context matter, particularly for sensitive topics like complaints or compliance-adjacent conversations. Treat it as a coverage tool for occasional messages in a long tail of languages, not as a substitute for language coverage in your core support languages.

Troubleshooting

• Translation isn't appearing — confirm the toggle is on for your own profile in Settings → Translations, not assumed on because a colleague enabled theirs; the preference is per agent.
• Usage looks unexpectedly high — check whether multiple agents on the same team all have translation enabled independently and are viewing overlapping conversations; each agent's view is translated independently, so the same inbound message can be counted once per agent who reads it with translation on, depending on how usage is aggregated for your plan.
• A specific phrase reads oddly translated — use "show original" to confirm the source text, and consider whether a quick reply or template in the target language would be clearer for outbound replies on that topic; see quick replies for building a library per language if you serve a recurring non-English audience.

Billing

Inbox translation itself carries no separate Arino fee beyond the metered AI cost described above. It's available on any instance regardless of plan tier, since it's a per-message AI cost rather than a feature gate. See billing and plans for the full fee structure.

Steps at a glance

1. Open translation settingsGo to Settings → Translations to configure inbox translation for your own account.
2. Choose your display languagePick the language you want inbound messages shown in from the supported list, covering major European, Middle Eastern and Asian languages.
3. Enable inbound translationSwitch on 'Translate inbound messages into my language.' This is a per-agent preference — each agent sets their own display language independently.
4. Read translated messages in the inboxInbound messages in a different language now appear translated automatically, with a one-click option to view the original text.
5. Monitor usageCheck the usage panel in Settings → Translations for the count of messages translated and tokens consumed this month, drawn from the shared AI credit bucket.
6. Adjust or turn off as neededChange your display language or turn translation off at any time; the setting saves instantly and takes effect on the next inbound message.

Frequently asked