The messenger has two kinds of text in it: the wording Gleap provides — buttons, labels, system messages — and the wording you wrote, such as your welcome message and menu items. They're translated in different places.
In the localisation settings, set your primary language and add the others you support. The primary language is the fallback: anything not translated into a customer's language is shown in it, so a partly translated messenger degrades to your main language rather than to blanks.
Which language a customer gets follows their own language setting, so someone browsing in French sees your French version if you have one.
Fields you fill in yourself — the welcome message, menu item titles and descriptions, form questions — have a language picker beside them. Switch language and enter that version; the settings look the same, you're just editing a different one.
The trap here is forgetting. Adding a menu item while your editor sits on English fills in only English, and customers on other languages see it in English without any warning that something is missing. When you add something, add every language before you move on.
Everything else — “Send”, “Start a conversation”, the text under an AI answer — lives under static translations. It's already translated into the supported languages, so you only go there to change wording, not to fill blanks.
It's worth a visit anyway. This is where you adjust a form of address that doesn't match your product's voice, or replace a term with the one your customers actually use.
The static translations editor can translate for you rather than making you fill each field by hand. Useful for a language nobody on your team speaks, and for getting a complete set quickly.
Read the result for the short strings. Buttons and labels are the hardest thing to translate without context — a single word can come back grammatically fine and completely wrong for what the button does — and they're also the most visible.
