Switching
Go to Settings, where your own profile sits at the top: email, role, your name, and Language. Pick one from the dropdown and the app changes immediately — no reload, no save button. It follows your account, not your browser, so signing in on a laptop and a phone gives you the same language on both. And it is yours alone: changing it moves nothing on a colleague’s screen.What changes, and what deliberately does not
The app’s own words change: menus, buttons, column headings, the tips behind the ⓘ icons, confirmation dialogs, empty states. Dates and numbers change with them — a German reading gets65.510, an English one 65,510.
Your own data stays exactly as you wrote it. Contact names, message bodies, template text, trigger names, your pipeline stages, and the labels on your contact fields are yours. Nudge never rewrites them, in any language.
That last one has a visible consequence worth knowing about. Contact field labels come from your own field setup, so if your workspace was set up in English, a colleague reading the app in German still sees First name on a contact card while the Add-contact form beside it says Vorname. The form is our word; the card is yours. If you want both in German, rename the fields in Workspace setup — and then they read German for everyone, including your English-speaking colleagues, which is the trade.
A few technical terms stay in English on purpose: WABA, Cloud API, E.164, access token, API key, and the names of the services Nudge connects to. Those are the words printed in the consoles you would go and look at, so translating them would leave you searching for something that isn’t there.
What people receive is a separate setting
Interface language and message language are two different things, and mixing them up is the easy mistake to make here.- Language (this page) decides what you read inside Nudge.
- A contact’s language decides which version of a template they receive. It comes from the owner assigned to that contact, and it is set in Contact owners.