HighLevel in German: How to Give Clients a German Dashboard

A physiotherapy practice in Munich signs up for your platform. The office manager switches HighLevel to German, and most of the screen changes. Then a form error message appears in English, a sidebar label wraps onto two lines because the German word is twice as long, and the colors look exactly like the software another agency in town resells. The owner asks you two questions: “Ist das wirklich auf Deutsch?” and “Ist das wirklich Ihre Software?”

This guide answers both for HighLevel in German. It covers what HighLevel (also called GoHighLevel or GHL) shows in German natively today, where the native translation stops, what a branded German menu adds, whether to write Sie or du, how to handle long German compound words in a narrow sidebar, how Germany, Austria and Switzerland write numbers, dates and prices, what the data-protection conversation looks like in the DACH region (Germany, Austria and Switzerland), what happens to German SMS and WhatsApp messages, and a step-by-step setup. GHL Dashboard Builder is an independent design service and is not affiliated with HighLevel; where our product helps, we say exactly what it does and where it stops.

Can HighLevel be used in German today?

Yes. German (Deutsch) is one of HighLevel’s built-in platform languages. Each sub-account has a default language and each user can choose their own. Where a piece of the interface has not been translated yet, HighLevel shows English, so the result is mostly German rather than completely German, and the gap is largest in builders and automations.

Where the native setting lives

HighLevel’s help center article on internationalization describes two levels of language setting:

1. The sub-account default. In a client’s sub-account, open Settings, Business Profile and choose Platform Language. Everyone in that sub-account sees this language unless they pick another one.
2. The user’s own choice. Each user can open Settings, My Profile and choose their own Platform Language. The user’s choice takes priority over the sub-account default.

A sub-account is one client’s workspace in HighLevel; HighLevel also calls it a location. The article lists German alongside French, Spanish, Portuguese, Italian, Dutch, Swedish, Danish, Finnish and Norwegian at the time of writing, and it explains that text without a translation falls back to English. There is one German option, not separate versions for Austria or Switzerland.

What German-speaking users have reported

German-speaking agencies use HighLevel’s native translation every day, and their reports on HighLevel’s ideas board show where it is still thin. One user reported that the German translation of a membership course button says End Course instead of Start Course, which is exactly the kind of mistake a paying client notices on day one. Another bug report on form and survey error notifications describes a required-field alert that stays in English even when the sub-account language is set to German.

Those reports matter for one reason. German clients do not only want German; they want correct, consistent German that sounds like their trade and that their agency can fix. At the time of writing, HighLevel’s native setting does not let you rewrite its translated labels, so a wrong word stays wrong until HighLevel changes it.

Who reads German, and why it matters to your agency

German is the working language of three wealthy markets with very different habits. A trades business in Stuttgart, a law firm in Vienna and a clinic in Zurich all read German, but they write prices, dates and even the letter ß differently. A German dashboard that feels right in Hamburg can look slightly foreign in Basel.

German is also widely learned outside those countries. The Federal Foreign Office reported that about 15.4 million people were learning German as a foreign language worldwide in its 2020 survey. In Switzerland, Swissinfo, reporting Federal Statistical Office figures, says almost two-thirds of permanent residents name German as their main language, while 23% of the working population spoke English at work in 2023. Many Swiss teams are therefore bilingual, which shapes how you set up their dashboard.

Infographic

German and your HighLevel clientsby the numbers

15.4M

people learning German as a foreign language worldwide (2020 survey)

(Federal Foreign Office)

66%

of Swiss permanent residents name German as a main language

(Swiss FSO, via Swissinfo)

1

German option in HighLevel's Platform Language, for all German-speaking countries

(HighLevel Help Center)

15

dashboard languages in GHL Dashboard Builder, German among them

(GHL Dashboard Builder)

Sources: Federal Foreign Office, German as a foreign language worldwide (2020); Swiss Federal Statistical Office via Swissinfo; HighLevel Help Center; GHL Dashboard Builder, November 2026.

What does HighLevel show in German, and what stays in English?

HighLevel’s native German translates much of the web interface for users who choose it, with English wherever a translation is missing. Your clients’ customer-facing content, such as SMS, emails, forms and funnels, is German only if someone writes it in German. Branding and industry wording are not part of the language setting at all.

That split matters before a sale. A client who expects every screen in German will find English somewhere sooner or later, most often in builders, automations and validation messages. HighLevel ships changes often, so treat any list of untranslated screens as a snapshot and check the screens your client actually uses.

Why the two layers work together

The native setting and a theme do different jobs. HighLevel’s Platform Language decides the text inside HighLevel’s own pages, for each user. A theme decides how the dashboard looks and what the menu and navigation say, for each sub-account it covers. The best German setup for most clients uses both: German as the Platform Language, so inner pages read in German where HighLevel has translated them, and a branded German menu, so the screen the team opens every morning carries your brand and their words.

For German, as for French and Spanish, the value of a theme is not translation from nothing. It is control: your brand, your client’s words, and labels short enough for the sidebar. Our overview of GoHighLevel’s languages compares every language side by side, and our guide to HighLevel in French covers the closest comparable case, including regional variants.

How does GHL Dashboard Builder put GoHighLevel in German?

GHL Dashboard Builder translates GoHighLevel’s menu and navigation into German in your brand, lets you rename any menu item in your own German wording, can limit the German design to chosen sub-accounts, and installs as one CSS line and one JavaScript line in HighLevel’s custom code settings. Text inside HighLevel’s own pages keeps following each user’s Platform Language.

GHL Dashboard Builder is an independent design service that turns the standard HighLevel (GoHighLevel) dashboard into a branded platform: your colors, menu, login design, privacy mode and your clients’ language, installed with two lines of code. For German, the relevant pieces are the built-in German language pack, the menu editor, sub-account targeting, privacy mode, the templates and the install itself. It is the same approach as our GoHighLevel white label dashboard, with German as the working language.

What the German setup includes

• A German pack. The menu, the sidebar’s search and sub-account switcher (“Unterkonto wechseln”), the header search box (“Kontakte, Deals, Unterhaltungen suchen…”), notifications, the profile menu, common buttons and the tab names our theme shows are translated into German. Menu items read Dashboard, Unterhaltungen, Kontakte, Verkaufschancen, Kalender, Zahlungen, Marketing, Automatisierung, Websites, Mitgliedschaften, Reputation, Berichte and Einstellungen. German is one of 15 languages; 3 of them (Arabic, Urdu and Hebrew) read right to left, and German uses the normal left-to-right layout.
• The formal Sie. Where the pack addresses the user, for example in the setup guide’s greeting (“Hallo {name}, hier ist Ihre persönliche Einrichtungsliste…”), it uses Sie, which suits most business clients in the DACH region.
• Your own wording. Override any translated label, so a tax adviser’s team sees Mandanten instead of Kontakte, and a long label such as Mitgliedschaften becomes Kurse.
• Menu editor. Rename, reorder, hide and badge any of HighLevel’s 19 menu items, and add your own items.
• Privacy mode in German. The eye button in the header is labelled Datenschutzmodus and blurs names, emails, phone numbers, the conversation list and deal values before a screen share.
• Templates. Start from one of 27 templates, then set the language to German. For German clients we often suggest the Vertex template, an electric-blue primary on a dark slate sidebar, and for law firms and financial advisers the Counsel template, navy and oxblood with serif headings.
• No data access. The builder never connects to your HighLevel account and the installed code does not send data anywhere.

At a glance: features, what they do, which plan

All three plans are one-time payments with no monthly fee, plus a one-time $100 setup fee on every plan, for which we install and configure the design in your HighLevel. Starter ($280) gives one branded design from any template, without the language section. Pro ($480) adds up to 3 designs, the menu editor, the dashboard in German or any of the other 14 languages and the branded login page. Agency ($880) adds up to 100 designs, a look designed by our team, custom CSS and JavaScript and lifetime updates. Starter and Pro include 12 months of updates, then optional at $99 a year. The full list of what each feature does is on our features page.

What the client sees afterwards

After installation, a user in the German sub-account logs in on your white-label domain and sees the sidebar in your colors with labels such as Unterhaltungen, Kalender and Kontakte, or the renames you chose, such as Patienten. When they open a settings page or a builder, they see HighLevel’s own text in the Platform Language they chose, which is German for most of the interface and English on screens HighLevel has not translated yet. You can click through a live German preview on our German language page.

Should a German GoHighLevel dashboard say Sie or du?

Use Sie unless your client tells you otherwise. Most German-speaking businesses address customers and colleagues formally in software, and our German pack uses Sie. Young brands, gyms, creative studios and some start-ups prefer du. The mistake to avoid is mixing them: a menu in Sie, an SMS in du and an email in Sie looks careless.

Where the choice shows up

The menu itself rarely addresses anyone; nouns such as Kontakte and Kalender work with either form. The choice shows up in sentences: the welcome greeting, empty-state hints, button texts such as “Speichern Sie Ihre Änderungen”, and above all in everything your client’s customers read. Agree it once and write it into your onboarding checklist:

Gender-inclusive wording

Some German clients write gender-inclusive forms such as Kund:innen or Patient*innen; others avoid them, and a few are not allowed to use them. Bavaria, for example, has banned gender characters in schools and official correspondence. For menu labels the easiest answer is a neutral word where one exists: Kontakte, Mitglieder, Team or Termine work for everyone. Where a role noun is unavoidable, ask the client which form they use on their own website and copy it.

Which German words should the GoHighLevel menu use for each industry?

Use short, everyday office German and rename the items where your client’s trade has its own word. HighLevel calls every person a contact and every deal an opportunity in every language, while a practice thinks in Patienten, a tax adviser in Mandanten and a roofing company in Aufträge. When the menu matches the way the business talks, staff find things faster and training takes less time.

Industry renames in German

Here are renames agencies commonly choose, based on the industry wording in our templates:

• Dental and medical practices: Kontakte becomes Patienten, Verkaufschancen becomes Behandlungen.
• Tax advisers, accountants and law firms: Kontakte becomes Mandanten, Verkaufschancen becomes Mandate or Akten.
• Real estate: Verkaufschancen becomes Objekte or Exposés.
• Gyms and fitness: Kontakte becomes Mitglieder.
• Restaurants and hotels: Kalender becomes Reservierungen.
• Trades and home services (Handwerk): Verkaufschancen becomes Aufträge or Angebote.
• Beauty and spa: Kalender becomes Termine.
• Coaches and course providers: Mitgliedschaften becomes Kurse.

Why German labels need extra care

German builds long compound words, and a narrow sidebar has no room for them. We counted the characters in our own German pack: many labels are longer than their English originals, and a few of the tab names are almost twice as long. The chart shows the clearest cases.

Globale Workflow-Einstellungen (24)30 characters

Benutzerdefinierte Berichte (14)27 characters

Kalendereinstellungen (17)21 characters

Mitgliedschaften (11)16 characters

Automatisierung (10)15 characters

Einstellungen (8)13 characters

English character counts in brackets. Source: GHL Dashboard Builder German and English language packs, counted November 2026.

Three habits keep a German menu tidy. First, shorten where meaning allows: Automatisierung can become Workflows, a word German teams use anyway, and Mitgliedschaften can become Kurse for a coach. Second, hide the items a client never uses, so the menu shows six short words instead of nineteen long ones. Third, check the menu at the width your client actually uses, including a laptop at 125% zoom, where long labels wrap first.

How to choose the words with your client

1. List the items each role uses. A front desk may need only Unterhaltungen, Kalender and Kontakte. Hide the rest for that client so the menu stays short.
2. Ask what they call each thing today. If a firm says Mandanten in every meeting, the menu should too.
3. Check the country. Ask whether the team is in Germany, Austria or Switzerland, and whether they use English loanwords such as Leads, Deals or Pipeline at work. Many sales teams do.
4. Agree Sie or du once, and use it everywhere the client’s customers and staff read.
5. Review with a native speaker on the client’s team before launch, not after.

Our guide to renaming GoHighLevel menu items walks through the menu editor in detail, and the GHL sidebar and menu customization page shows everything you can change in the sidebar.

The menu editor writes the same wording into every sub-account the design covers, so the renames above appear for every user of that client. Users who prefer English inner pages can still set their own Platform Language; the menu keeps your German wording.

How should numbers, dates and prices appear for German-speaking clients?

It depends on the country. Germany writes 1.234,50 € with a point between thousands and a comma for decimals. Austria puts the euro sign first and calls January Jänner. Switzerland writes CHF 1’234.50 with an apostrophe and a decimal point. All three use day-first dates, the 24-hour clock and a week that starts on Monday.

What locale data says

Browsers and most software take number and date formats from the Unicode Common Locale Data Repository (CLDR), a shared database of how each language and country writes numbers, dates and currencies. We checked German locales in Node.js 22 with ICU 78.3, which ships CLDR version 48:

Four details matter in practice. First, a German reader sees 1.234 as one thousand two hundred and thirty-four, so an English-formatted price such as 1,234.50 reads to them like a typo. Second, CLDR’s Austrian data groups plain numbers with a non-breaking space but writes prices with points, and puts the euro sign before the amount; Austrian clients may use either style in their own documents, so copy theirs. Third, Swiss prices use a decimal point, not a comma, which surprises people used to Germany. Fourth, CLDR gives Jänner for January in Austrian German, and an Austrian client will notice “Januar” in a reminder.

Weeks, holidays and the letter ß

German-speaking offices plan in calendar weeks. “KW 46” (Kalenderwoche) on a project plan means the ISO week starting on Monday, so set each calendar’s week to start on Monday and use ISO week numbers in any report you build. Public holidays differ by German state, Austrian state and Swiss canton, so set each calendar’s availability for the client’s own region rather than for the country as a whole.

Swiss German spelling has one more trap. In Switzerland and Liechtenstein, ß is not used and is written as ss, so a Zurich client reads “Strasse” and “Grüsse”, not “Straße” and “Grüße”. Our German pack follows German spelling from Germany, so review labels and your own templates with a Swiss client and replace ß where it appears.

What follows HighLevel’s settings

Invoices, payment links, products, reports and calendar pages are generated by HighLevel, so their currency and formats follow HighLevel’s own settings for the sub-account. In each German-speaking client’s sub-account:

1. Set the business address and time zone under Settings, Business Profile. All three countries change their clocks in spring and autumn, so confirm that reminders fire at the right local time after each change.
2. Set the client’s currency (EUR or CHF) in the payment settings so invoices and payment links show the right one.
3. Check the date and price format on a sample invoice and a booking confirmation, and write dates out in full in your own templates where possible, such as “5. November 2026”, which reads correctly in every German-speaking country.

The language and format choices in our builder shape its live preview and the menu, but a theme does not change how HighLevel formats an invoice. Our market page lists the conventions and templates we suggest for clients in Germany, including euro formatting and a Monday week.

How do data protection rules in Germany, Austria and Switzerland affect your dashboard?

They affect how you show client data more than how the dashboard looks. Clients in Germany and Austria fall under the EU’s General Data Protection Regulation (GDPR, in German DSGVO), and Swiss clients under Switzerland’s revised data protection law. A theme that only restyles the browser does not change your legal position, but demos and support calls that show real customer data can. This section is background for a conversation with your client, not legal advice.

What German-speaking clients ask

Expect data protection questions early from German, Austrian and Swiss clients, often before anyone discusses colors or menus. Typical questions are: where is the data stored, who can see it, is there a data processing agreement (Auftragsverarbeitungsvertrag, AVV), and what happens during a screen share. Answer the first three from HighLevel’s own documentation and your contracts; GHL Dashboard Builder does not store, process or transmit your clients’ data, because the builder never connects to your HighLevel account and the installed code does not send data anywhere.

In Switzerland, the revised Federal Act on Data Protection took effect on 1 September 2023, according to the Federal Data Protection and Information Commissioner. Swiss clients may therefore have reviewed their tools recently and will ask the same questions in their own terms. If a client needs a formal opinion on what the GDPR or Swiss law requires of them, they should ask their own data protection officer or lawyer.

Screen shares are where data leaks

The everyday risk is simpler than any regulation. A sales demo, an onboarding call or a recorded training video can show real names, phone numbers, email addresses and deal values to people who should not see them. Many agencies record training videos for their clients’ staff, and every one of those recordings is a chance to capture a real patient’s or customer’s details.

Privacy mode handles that moment. An eye button in HighLevel’s header, labelled Datenschutzmodus in German, blurs contact names, emails, phone numbers, the conversation list and deal values with one click, and a second click shows them again. Our guide to hiding client data on screen shares explains when to use it and what it covers.

What happens to German SMS, WhatsApp and email messages?

They work well, with one cost trap. Umlauts and ß are part of the basic SMS alphabet, so umlauts do not raise the cost of a German SMS, but German typographic quotation marks are not, and one of them shortens every segment of the message. WhatsApp templates must be approved in German, and German emails need careful writing but no layout changes.

SMS: umlauts are fine, quotation marks are not

A normal SMS uses the GSM-7 character set, which covers Latin letters, digits, common symbols and some accented letters. According to Twilio’s guide to GSM-7 encoding and the GSM 03.38 character table it refers to, the basic set includes Ä, Ö, Ü, ä, ö, ü and ß. The euro sign € is in the extension table, so it counts as two characters. German’s low and high quotation marks („ and “), the curly apostrophe and the en dash are outside GSM-7.

When a message contains any character outside GSM-7, the whole message is sent as UCS-2. Twilio’s page on how long an SMS can be gives the limits: 160 characters for a single GSM-7 message and 153 per segment of a longer one, against 70 and 67 for UCS-2.

The practical effect: a 140-character German appointment reminder with umlauts fits in one GSM-7 segment, while the same reminder with the practice name in „typographic quotes“ needs three UCS-2 segments (67 + 67 + 6). If your SMS provider bills per segment, that triples the cost of each reminder. Word processors and phones in German often type „“ automatically, so templates pasted from a Word document are the usual culprit. Keep templates plain:

• Use straight quotes or none. “Praxis Müller” or simply Praxis Müller, never „Praxis Müller“.
• Write prices as EUR 45 or 45 Euro if you are close to the 160-character limit, since € costs two characters.
• Keep reminders short. A reminder needs the name, the time, the place and how to reschedule: “Ihr Termin morgen, 10:00 Uhr, Praxis Müller. Absagen: Antwort mit NEIN.”

Paste each German template into your provider’s segment calculator before you set a client’s monthly message budget.

WhatsApp: approved templates in German

Messages that start a WhatsApp conversation need pre-approved templates, and Meta’s list of supported languages for WhatsApp templates includes German with the code de. Each language version is its own template and is reviewed on its own, so a bilingual Swiss client needs a German and, often, a French or English version of each template. Store a preferred-language field on each contact and use it in workflows to choose the right one.

Email: write it, then test it

HighLevel’s email builder handles German text without special settings. The work is in the writing:

1. Build one German master template and have a native speaker from the client’s country read it before you copy it.
2. Keep Sie or du consistent with the menu and the SMS templates.
3. Check that umlauts in subject lines and the sender name display correctly in Gmail and Outlook on desktop and phone.
4. Translate the footer, unsubscribe text and any button labels you wrote yourself, and for Swiss clients replace ß with ss.

Can you give German to some clients and keep English for the rest?

Yes. Many agencies serve a mix: English-speaking clients, German-speaking clients and bilingual teams, which are common in Switzerland and in international companies in Germany. Give each client the menu language its team reads best, and remember that one design shows one menu wording for everyone in the sub-accounts it covers.

Bilingual teams in one sub-account

HighLevel’s native setting handles bilingual teams per user: the owner can keep English while the office team picks German in Settings, My Profile. A theme works per sub-account, so for a bilingual team, decide which menu everyone will share:

• German menu, Platform Language per user. The menu reads in German for everyone, and each user’s inner pages follow their own Platform Language. This suits a practice or trades business where most daily users work in German.
• English menu, German inner pages per user. The menu stays in English, and German-speaking users set their Platform Language to German for inner pages. This suits an international team in Berlin or Zurich whose working language is English.
• Words that work in both languages. Several menu items are the same or close in English and German: Dashboard, Marketing, Websites, Workflows, Pipelines, Team. For a bilingual team, favour those where you can.

Different clients, different designs

HighLevel’s Custom CSS and Custom JavaScript boxes sit at agency level, so whatever you paste applies across all sub-accounts by default. To give one client a German design, the theme must know which sub-accounts to target. GHL Dashboard Builder does this with an “Only these sub-accounts” option: you add the client’s sub-account by its link or Location ID, that sub-account gets the design, and every other sub-account and the agency view keep plain HighLevel. You still paste one install code.

Be precise about what one install covers. One design is shown in the chosen sub-accounts; Pro includes up to 3 designs and Agency up to 100. If you need different looks for different clients, for example a German variant with ß for a Munich client and a Swiss variant with ss for a Zurich client, contact us and we will plan how to set that up. Our guide to GoHighLevel sub-account branding explains the options in more depth.

How do you set up a German GoHighLevel dashboard, step by step?

Agree the scope, the country and Sie or du with the client, set HighLevel’s native language and sub-account basics, write the German content, design and install the theme, then test with the people who will use it. The steps assume agency admin access and that your agency’s logo and domain are already set; our guide to white-labeling HighLevel covers those first. Menu paths follow HighLevel’s help center at the time of writing.

Infographic

A German GoHighLevel dashboardin five steps

1. 1

   Agree the scope

   Country, Sie or du, and what will be German.

2. 2

   Set native German

   Platform Language, time zone and currency per sub-account.

3. 3

   Write the content

   Plain-quote SMS, approved WhatsApp templates, tested emails.

4. 4

   Design and install

   Template, colors, short German labels, two install lines.

5. 5

   Test like a user

   Daily screens, a language switch and SMS segments.

Step 1: Agree the scope and the country

1. Write down who logs in and which language each person reads best: German, English or both.
2. Agree the country conventions: Germany, Austria or Switzerland, including ß or ss and the currency. Agree Sie or du.
3. Agree in writing what will be German: the menu and navigation, HighLevel’s inner pages where HighLevel has translated them, and all customer messages, forms and booking pages. Name what may stay in English: some inner screens, parts of the builders, some validation messages, system emails and the mobile app, depending on HighLevel’s current translation.
4. Ask which words they use for their customers, appointments and deals, and whether they prefer German terms or English loanwords such as Leads and Deals.

Step 2: Set HighLevel’s native language and the sub-account basics

1. Open the client’s sub-account and go to Settings, Business Profile.
2. Set Platform Language to German as the sub-account default.
3. Ask English-preferring users to set their own language under Settings, My Profile.
4. Enter the business name and address the way the client writes them, including the legal form (GmbH, AG, e.K.), and set the correct time zone.
5. Set the currency, EUR or CHF, in the payment settings.
6. Set each calendar’s availability to the client’s real week, regional public holidays and opening hours.

Step 3: Write the German content

1. Create the German SMS templates with straight quotes only, and keep each one under 160 characters.
2. Submit German WhatsApp templates for approval with the code de.
3. Build one German email template and test it in two mail apps.
4. Translate forms, surveys and booking pages, including the confirmation and error messages you control. Write your own required-field hints in German where the form builder allows it, since some of HighLevel’s own validation messages may still appear in English.
5. Add a contact field for preferred language and use it in workflows to pick the German or English version.

Step 4: Design and install the theme

1. Open the free builder in German, choose a template, and set the client’s colors, logo and fonts.
2. Rename the menu items you agreed in Step 1, shorten long labels such as Automatisierung or Mitgliedschaften, replace ß for Swiss clients, and hide the items the client does not use.
3. If only this client should get the German design, limit the design to their sub-account.
4. In the agency view, open Settings, Company, Whitelabel and find the custom code area. Copy whatever is already in Custom CSS and Custom JavaScript into a text file as your rollback.
5. Paste the theme’s CSS line and JavaScript line and save. HighLevel warns about third-party scripts; confirm only if you trust the code. On every plan, we do this step for you as part of the setup.

Step 5: Test like an office user

1. Open the sub-account in a new tab and hard-refresh.
2. Walk through the dashboard, conversations, calendars, contacts and the opportunities board, on a laptop screen and at 125% browser zoom, and look for labels that wrap.
3. Switch a test user’s Platform Language between German and English and check that the menu keeps your wording.
4. Send yourself a German SMS reminder and check its segment count with your provider.
5. Ask two staff members to use it for a morning and tell you which labels confuse them.

What can go wrong, and what doesn’t a German theme solve?

Most problems come from unclear promises, long labels nobody tested, the wrong country’s conventions and SMS costs nobody planned for. A theme changes how HighLevel’s menu and main screens look and read; it does not translate HighLevel’s inner pages, it does not correct HighLevel’s own translation, and it does not write your clients’ content.

There are also limits no theme removes. HighLevel does not officially support custom code, so a platform update can require a theme refresh; Starter and Pro include 12 months of updates for this, and Agency includes lifetime updates. A theme works in the web browser; it does not change HighLevel’s mobile app, its system emails or its builders. One design shows one menu wording, so a bilingual team shares one menu. A German menu does not by itself answer a client’s data-protection questions; those depend on HighLevel, your contracts and how the client uses the platform. And no menu translation makes up for poorly written German content: budget for a native writer from the client’s country, and see our FAQ for questions about installing, removing and data.

What to do next

1. List your German-speaking clients and, for each one, who logs in, which country they are in, whether they write ß or ss, and whether they expect Sie or du.
2. Set HighLevel’s Platform Language to German in each of those sub-accounts today; it is free and covers the inner pages a theme never touches.
3. Fix the sub-account basics: time zone, currency, regional holidays and calendars that start the week on Monday.
4. Search your German SMS templates for „“, curly apostrophes and emoji, submit WhatsApp templates in German, and test one German email in two mail apps.
5. Try the client’s colors and a German menu in the builder, install on one sub-account first, and compare the plans when you are ready to roll it out.