Language

Nudge speaks English, German and Turkish. The choice is yours alone — it changes what you see, and nobody else’s screen moves.

​

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 gets 65.510, an English one 65,510. Your own data stays exactly as you wrote it. Contact names, message bodies, template text, automation 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. Every contact has a Language field of their own. A contact who books on a booking page or fills in a form gets the language they used. A contact you add by hand starts on your workspace’s Default language, and you can change it on the contact. When Nudge only guessed a contact’s language, the first WhatsApp reply they type or the first call where they talk to your agent replaces the guess with the language they actually used. A language someone on your team set by hand is never changed. On a HubSpot workspace this field lives only in Nudge and is never sent to HubSpot. Your team members have no language of their own for messages. If a contact has no language, Nudge uses the Default language from Workspace setup → Languages.

So you can read the app in German while your Turkish colleague reads it in Turkish, and both of you send the same contact the same Turkish message. Changing your own language never changes a single thing that goes out.

​

Still in English

Two screens do not follow the setting, because they appear before you are signed in and Nudge does not yet know who you are: the sign-in page and the message you get if a web address isn’t linked to a workspace. Emails and bell notifications Nudge sends you — a sync failure, a budget alert, a task reminder — are also still English for now.

​

Something reading oddly?

The translations are ours, not a machine’s, but three languages across a whole CRM leaves room for a clumsy phrase. Tell us through Help & feedback in the same menu as the language picker, and say which screen it was on — we fix wording in place, and it reaches you on the next update.