Localization

Autopilot > Localization is where you enable a locale, translate every text a visitor reads, and set the agent's reply language. It applies to every environment of the Product.

Before you start

Adding or deleting a locale, changing the agent language and typing translations take an organization admin. A member can read every card.

BETA supports two locales: English (US) and Turkish (Türkiye). English (US) is on for every Product and is the language you write your content in. Ask us for any other language.

Setting it up

1. Press New locale, pick the locale and press Create locale. The Product now accepts translations for it.
2. Tell ARCY which locale each visitor is in. Send locale_code as an attribute in identify(), or pass contentLocale to arcy.init() when you know the region before the visitor signs in. The most recent one wins. See Reference.
3. Under Agent language, set Language, the language the agent replies in by default, and Reply language policy: Match the user replies in the visitor's language when it is clear, Always use the set language replies in the chosen language whatever the visitor writes.
4. In the Translation editor, pick the language and type a translation beside each English string. Edited rows are marked Unsaved. Save the page. Each string saves on its own, so one refusal never blocks the rest; a refused string keeps your text and its reason under the field.

Clear a field and save to remove a translation. You cannot switch language while you have unsaved changes.

What it changes

A visitor reads your content in their locale where a translation exists and in English where it does not. Without locale_code or contentLocale, ARCY uses the browser language, then the agent language. With two locales enabled, the chat panel's Settings sheet offers a language choice, and that choice outranks everything your Product sends. See Customization.

Translation progress shows, per language, how many strings are Translated, how many are Missing and how many are Out of date, which means the English changed after the translation was written. An out-of-date translation is still served. Press Still correct on its row to clear the flag without retyping it.

The editor's Not completed view shows what is left. Rows are grouped by area, and texts the widget shows to identified and anonymous visitors separately appear twice, so translate both. See Flows for who counts as which. A row whose English uses a variable the translation does not says so and still saves.

A flow cannot be published while an enabled language is missing its public name or summary. The refusal names the language and the field. Flows published before you added the language keep running untranslated until you translate them.

Delete locale stops serving every translation for that locale, and its visitors fall back to the agent language. This cannot be undone. English (US) has no delete action.

When it goes wrong

A visitor reads English on a translated page. Their locale never reached ARCY. Check that identify() sends locale_code with the exact code shown in the Code column, tr-TR and not tr, or that the visitor has not picked English themselves in the chat panel.

Publishing a flow is refused for a missing translation. Open the editor, filter to Not completed, fill the flow's public name and summary for the named language, save, and publish again.

See also

• Customization
• Flows
• Reference