HighLevel in Arabic: How to Give Clients an Arabic Dashboard

A clinic owner in Riyadh signs up for your platform, logs in, and sees an English menu on the left of the screen. Her front-desk team reads Arabic all day, types patient names in Arabic and expects the page to run from right to left. She asks the obvious question: “Can it be in Arabic?” If your honest answer is “partly, and here is exactly which part,” you keep her trust. If you promise a fully Arabic HighLevel and she finds English screens a week later, you lose it.

This guide gives you that honest answer. It covers what HighLevel (also called GoHighLevel) shows in Arabic today, what a theme can add, how right-to-left layout behaves, which kind of Arabic to use in the menu, how digits, dates and currency appear in different Arab countries, what happens to Arabic SMS, WhatsApp and email, which fonts work, and a step-by-step setup. It is a language guide, so it applies whether your client is in Riyadh, Cairo, Doha or Amman. GHL Dashboard Builder is an independent design service and is not affiliated with HighLevel; where our product helps, we say what it does and where it stops.

Can HighLevel be used in Arabic today?

Partly. HighLevel’s built-in language setting does not include Arabic at the time of writing, and its interface is not designed for right-to-left reading. You can still give clients an Arabic menu and navigation with a mirrored layout through custom code, and you can write all customer-facing content in Arabic yourself.

What HighLevel offers natively

HighLevel has begun translating its interface. HighLevel’s help center article on internationalization explains that each sub-account has a default language under Settings, Business Profile, Platform Language, and that each user can override it in Settings, My Profile. A sub-account is one client’s workspace in HighLevel; HighLevel also calls it a location. At the time of writing, the languages in that list are mostly European, and Arabic is not one of them.

Demand is clearly there. A request titled Arabic language support on HighLevel’s ideas board asks for Arabic as a native language with right-to-left support, and at the time of writing it is marked as under review, with a HighLevel team member inviting agencies to short calls about how they would use an Arabic HighLevel day to day. That is a good sign, but it is not a release date. Do not sell a client on a feature that is still being researched.

What agencies do in the meantime

Agencies serving Arabic-speaking clients use three layers:

1. Interface layer. A theme in HighLevel’s agency-level Custom CSS and Custom JavaScript boxes translates the menu and navigation and sets the page direction to right-to-left. This is the part your client sees first, every time they log in.
2. Content layer. Everything the client’s customers see, such as SMS, WhatsApp templates, emails, forms, surveys, funnels, booking pages and invoices, is written in Arabic by your team or the client’s team inside HighLevel’s normal editors.
3. Settings layer. Time zone, currency, date preferences and business details are set per sub-account so that what HighLevel itself generates looks right for the country.

The rest of this guide goes through each layer. If you are new to branding HighLevel at all, start with our guide to white-labeling HighLevel, which explains the logo, domain and custom code settings this article builds on.

What can be shown in Arabic, and what stays in English?

The menu, the navigation and the parts of the interface a theme restyles can be shown in Arabic. HighLevel’s own page content, its builders, its system emails and its mobile app keep following HighLevel’s language settings. Your clients’ customer-facing content can be fully Arabic because you write it.

This is the single most important thing to explain to a client before they buy. A clinic owner who expects every word on every screen to be Arabic will be disappointed. A clinic owner who knows that the menu, the main navigation and every message their patients receive will be Arabic, while some inner settings screens stay in English, can make an informed choice. Most front-desk teams spend their day in the same five or six places: conversations, calendars, contacts, the opportunities board and the dashboard. Those are where an Arabic menu and right-to-left layout make the biggest difference.

Why the inner pages stay in English

A theme works by changing how the browser displays HighLevel’s pages. It can replace the visible text of known elements, such as the menu labels, because those elements are stable and predictable. It cannot safely rewrite every sentence, tooltip, error message and setting description inside every HighLevel module, because those change with HighLevel’s releases and are generated by HighLevel’s own code. A theme that tried would break often and could show wrong text in places where accuracy matters, such as billing or compliance settings.

So the honest promise is: “Your team’s menu and navigation will be in Arabic and the screen will read right to left. Some inner settings pages are still in English, and so are the builders.” If a client needs every screen in Arabic, HighLevel’s native support is what will deliver that, and the ideas-board request is the place to follow it.

How does right-to-left layout work in the HighLevel dashboard?

A right-to-left (RTL) layout mirrors the page: the menu moves to the right, text aligns to the right, and the reading order runs from right to left. A theme switches this on by setting the page’s direction to RTL and restyling the parts it controls. Parts that HighLevel draws without RTL support may keep some left-to-right behavior.

What mirrors and what does not

When the page direction is set to right-to-left, the browser itself flips a lot: text alignment, the order of items in rows, and the side that scrollbars and indents sit on. A theme then fixes the parts that HighLevel positions explicitly, such as the sidebar, the header and the sub-account switcher. Our own install notes state plainly that HighLevel’s interface is not RTL-aware, so only the parts the theme restyles (the sidebar, header, buttons and inputs) mirror correctly. Complex inner screens such as large tables, the calendar grid and the builders may still read left to right in places.

The same limit shows up in HighLevel’s customer-facing tools. A request on HighLevel’s ideas board asks to add full RTL support for forms, surveys and sites, which tells you that at the time of writing there is no built-in right-to-left switch there either. Arabic text you type into a form or funnel displays as Arabic, but alignment, field order and icons may need manual adjustment in each element’s settings or with page-level custom CSS.

Mixed Arabic and English text

Arabic business text is rarely pure Arabic. A message contains a brand name in Latin letters, an email address, a phone number, a price or a booking reference. Browsers handle this with the Unicode bidirectional algorithm, which decides the order of mixed runs of text. Most of the time it works. When it does not, punctuation lands at the wrong end of a sentence, a phone number appears with its plus sign on the wrong side, or a product code reads backwards.

The W3C’s guide to inline markup and bidirectional text in HTML explains the cause and the fix: text whose direction is unknown, such as a name from a database, should be isolated so it cannot disturb the text around it, using the bdi element or dir="auto". You cannot change how HighLevel builds its pages, but you can use the same idea in your own content:

• Put phone numbers, emails and codes on their own line in Arabic SMS and email templates rather than in the middle of a sentence.
• In funnel and email builders, check whether a text block has a direction setting before you add custom code.
• End Arabic sentences with Arabic punctuation and read the message on a phone before you approve the template.

HighLevel users have reported this exact problem. A request about RTL Arabic and Hebrew text in HighLevel’s email builder notes that right-aligning text only does half the job, because periods can still appear at the start of a sentence. Plan time for checking every Arabic template visually, not just for translating it.

For a deeper look at how right-to-left behaves on HighLevel’s main screens, including tables, pop-ups and date pickers, see the right-to-left section of our guide to white-labeling HighLevel in the UAE. You can also click through an Arabic preview on our Arabic language page.

Which Arabic should the menu use: Modern Standard Arabic or a dialect?

Use Modern Standard Arabic (MSA) for the menu by default, then rename the few items where your client’s industry or local habit uses a different word. MSA is the formal written Arabic used in business, news and government across the Arab world, so a receptionist in Casablanca and a sales manager in Riyadh both read it without effort.

Spoken Arabic varies a lot between countries. Gulf, Egyptian, Levantine and Maghrebi Arabic differ in everyday words, and a client may joke that the formal menu “sounds like a newspaper.” That is usually fine for a menu: short nouns such as Conversations, Calendars and Settings have standard MSA forms that nobody finds strange. Dialect becomes useful in customer-facing messages, where a warmer local tone can help, and that is content your team writes per client.

Arabic is also the language of a very large audience. It has been one of the six official languages of the United Nations since the General Assembly adopted it on 18 December 1973, the date now marked as UN Arabic Language Day. An Arabic setup you build well for one client is reusable across many countries, as long as you leave room for local wording.

The menu in Modern Standard Arabic

Here is how GHL Dashboard Builder’s built-in Arabic pack names the main HighLevel menu items, with examples of industry renames you might choose instead. The pack uses Modern Standard Arabic.

How to choose the words with your client

1. List the items each role uses. A front desk may need only Conversations, Calendars and Contacts. Hide the rest for that client so the menu is short.
2. Ask what they call each thing today. If the clinic says “patients” in Arabic in every meeting, the menu should too.
3. Keep labels to one or two words. Long Arabic labels wrap in a narrow sidebar and look cramped.
4. Keep your support team in mind. If your staff do not read Arabic, keep a simple English and Arabic map of the menu so they can guide the client on calls.
5. Review with a native speaker on the client’s team before launch, not after.

The industry wording in our templates follows the same idea. The Clinic template, for example, renames Contacts to Patients and Opportunities to Treatments, and you can give those renames Arabic wording. Our guide to HighLevel for dental and medical practices covers the clinic menu in more detail.

How should numbers, dates and currency appear for Arabic users?

Ask each client whether they expect Western digits (0 to 9) or Arabic-Indic digits (٠ to ٩), use day-before-month dates, and show prices in the client’s own currency. The right answer differs by country, and it is not the same across the Arab world.

Digits differ by country

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 current Arabic locales in Node.js 22 with ICU 77.1, which ships CLDR version 47. The same number and date come out differently depending on the country code:

Two details in that table often surprise agencies. First, Moroccan Arabic writes thousands with a period and decimals with a comma, the opposite of the UAE. Second, month names differ: the long date for Jordan uses the Levantine month name تشرين الأول for October, while Saudi Arabia, the UAE and Egypt use أكتوبر. If you copy a setup from a Saudi client to a Jordanian one, the dates change wording as well as digits.

Locale data is a default, not a rule. Many businesses in countries whose locale uses Arabic-Indic digits still prefer Western digits on screens, especially for phone numbers and prices. Ask the client, and record the answer in your onboarding notes.

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 client’s sub-account:

1. Set the business address and time zone under Settings, Business Profile. Check whether the country changes its clocks during the year, so reminders keep firing at the right local time.
2. Set the currency in the payment settings so invoices and payment links show riyals, dirhams, pounds or dinars rather than US dollars.
3. Check the date format on a sample invoice and a booking confirmation, and adjust your templates if the client wants day-before-month dates written out.

The digit and date choices in our builder shape its live preview, but a theme does not change how HighLevel formats an invoice.

The Hijri calendar

Business software in Arab countries mostly uses the Gregorian calendar for appointments and invoices. The Hijri (Islamic lunar) calendar still matters, because religious holidays, Ramadan working hours and some official dates follow it, and its dates move earlier each Gregorian year. Browsers can show Hijri dates: in our Node.js check, 5 October 2026 in the Umm al-Qura calendar used in Saudi Arabia formats as ٢٤ ربيع الآخر ١٤٤٨ هـ. HighLevel’s calendars use Gregorian dates, so if a client wants Hijri dates in confirmation messages, add them as text in the template and double-check them against an official calendar.

What happens to Arabic SMS, WhatsApp and email messages?

They work, but each channel has its own catch. Arabic SMS uses a different encoding that fits fewer characters per segment, WhatsApp templates must be approved in Arabic, and Arabic emails need a right-to-left check because HighLevel’s email builder does not handle direction fully on its own.

SMS: fewer characters per segment

A normal SMS uses the GSM-7 character set, which covers Latin letters, digits and common symbols. Arabic letters are not in it. As Twilio explains in its guide to UCS-2 encoding, a message containing any character outside GSM-7 is sent as UCS-2, which uses two bytes per character. A single UCS-2 segment holds 70 characters instead of 160. When a message is longer than one segment, part of each segment carries a header that tells the phone how to join them, which leaves 67 UCS-2 characters per segment, compared with 153 for GSM-7, according to Twilio’s guide to SMS length.

GSM-7, single message160 characters

GSM-7, per segment of a long message153 characters

UCS-2 (Arabic), single message70 characters

UCS-2 (Arabic), per segment of a long message67 characters

Any Arabic letter, and most emoji, switch the whole message to UCS-2. Source: Twilio Docs: What is UCS-2 character encoding? and How long can an SMS message be? (checked October 2026).

The practical effect: an Arabic appointment reminder of 200 characters needs three segments (67 + 67 + 66), while 200 characters of plain English need two. If your SMS provider bills per segment, Arabic reminders cost more. Two habits keep costs down:

• Write short Arabic templates. A reminder needs the name, the time, the place and how to reschedule. Cut greetings that add length without information.
• Avoid unnecessary emoji and special symbols in English messages. One emoji switches an otherwise English message to UCS-2 too.

Check how many segments your provider counts before you set a client’s monthly message budget.

WhatsApp: approved templates per language

WhatsApp is the main messaging channel for many businesses in the Arab world. For messages that start a conversation, WhatsApp requires pre-approved templates. Meta’s list of supported languages for WhatsApp templates includes Arabic with the code ar, plus regional codes for Egypt, the UAE, Lebanon, Morocco and Qatar. Each language version is its own template and is reviewed on its own.

For a bilingual client, create an Arabic and an English version of each template, name them so your team can tell them apart, and choose the right one in each workflow based on a contact field such as preferred language. Do not rely on translating a message at send time; an unapproved wording will not go out.

Email: direction is your job

HighLevel’s email builder accepts Arabic text, but as the ideas-board request above shows, aligning text to the right is not the same as setting its direction. For Arabic emails:

1. Build one Arabic email template as a master and test it before copying it.
2. Set text alignment to right on every text block, and check the builder’s options for a direction setting.
3. If you add custom HTML, set dir="rtl" and lang="ar" on the outer element.
4. Send a test to Gmail and Outlook on desktop and phone, and read the punctuation, links and numbers.

Which fonts work for Arabic in a branded HighLevel?

Choose a font family that includes Arabic letters, or pair an Arabic font with your Latin brand font. Most Latin brand fonts do not include Arabic, so without a deliberate choice the browser falls back to a system font for every Arabic word, and the menu looks inconsistent next to English labels.

Arabic type has its own styles. Naskh styles look like traditional book text and stay readable at small sizes; Kufi styles are more geometric and work better in headings and logos; modern sans-serif Arabic designs sit between the two and match clean Latin interface fonts. For a dashboard menu, a modern sans-serif or a Naskh-based face at a comfortable size is usually the most readable.

GHL Dashboard Builder offers these Arabic-capable Google Fonts in the builder: Noto Sans Arabic, IBM Plex Sans Arabic, Cairo, Tajawal, Almarai, Readex Pro, Noto Kufi Arabic and Noto Naskh Arabic, plus Rubik, which covers Latin, Hebrew and Arabic. Several of them include Latin letters too, which keeps English brand names and Arabic labels in one visual family.

Three checks before you approve a font:

• Size. Arabic letters often look smaller than Latin letters at the same font size. Increase the menu size slightly if labels look cramped.
• Weight. Thin weights lose the dots that distinguish Arabic letters. Avoid very light weights in the menu.
• Contrast. Arabic letterforms have fine details, so contrast matters even more. The W3C’s contrast guidance in WCAG 2.2 sets a minimum ratio of 4.5 to 1 for normal text. Check your sidebar text color against the sidebar background.

Our guide to HighLevel custom CSS explains how fonts are loaded into HighLevel and how to keep a stylesheet maintainable if you write your own.

How do you set up an Arabic HighLevel dashboard, step by step?

Prepare the client’s sub-account settings, write the Arabic content, design and install the theme, then test with the people who will use it. The steps below assume you have agency admin access and that your agency’s logo and domain are already set. Menu paths follow HighLevel’s help center at the time of writing.

Step 1: Agree the scope with the client

1. Write down who logs in and which language each person reads best.
2. Agree in writing what will be Arabic: the menu and navigation, all customer messages, forms and booking pages. Name what stays in English: some inner settings pages, the builders, system emails and the mobile app.
3. Ask which digits, date style and currency they expect, and which words they use for their customers and deals.

Step 2: Set up the sub-account

1. Open the client’s sub-account and go to Settings, Business Profile.
2. Enter the business name and address the way the client writes them, in Arabic and English if they use both.
3. Set the correct time zone, for example Asia/Riyadh, Asia/Qatar or Africa/Cairo.
4. Set the currency in the payment settings.
5. For users who also work in another HighLevel-supported language, set their Platform Language in Settings, My Profile.

Step 3: Write the Arabic content

1. Create the Arabic SMS templates and keep each one as short as possible.
2. Submit Arabic WhatsApp templates for approval with the ar language code or the client’s regional code.
3. Build one Arabic email template and test it in two mail apps.
4. Translate forms, surveys and booking pages, and adjust alignment on each element.
5. Add a contact field for preferred language and use it in workflows to pick the Arabic or English version.

Step 4: Design and install the theme

1. Open the free builder, choose a template, and set the client’s colors, logo and an Arabic-capable font.
2. Set the language to Arabic and the direction to automatic, so the layout switches to right-to-left.
3. Rename the menu items you agreed in Step 1 and hide the ones the client does not use.
4. If only this client should get the Arabic design, limit the design to their sub-account.
5. In the agency view, open Settings, Company, Whitelabel and find the custom code area. Copy what is already in Custom CSS and Custom JavaScript into a text file as your rollback.
6. Paste the theme’s CSS line and JavaScript line and save. HighLevel warns about third-party scripts; confirm only if you trust the code.

Step 5: Test like a front-desk 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.
3. Type an Arabic name with an English email address into a contact and look at how it displays.
4. Open a pop-up, a date picker and a large table, and note anything that overlaps.
5. Ask two staff members to use it for a morning and tell you which labels confuse them.

Should every client get Arabic, or only some?

Usually only some. Most agencies serving Arabic-speaking markets have a mixed client list: some teams work entirely in Arabic, some in English, and many switch between the two. Give each client the language their team reads best, and pilot right-to-left on one friendly client before you roll it out.

Reasons to treat clients differently:

• Team language. A Saudi clinic’s front desk may want Arabic, while a Dubai agency’s English-speaking sales team does not.
• Bilingual teams. Some clients prefer an English menu with Arabic content, because their staff learned software in English. Ask rather than assume.
• Pilots. Right-to-left changes how every screen looks. Test it with one client for a few weeks, collect the problems, and fix them before you offer it widely.
• Different wording. A clinic needs Patients and a broker needs Deals; one Arabic menu cannot say both.

HighLevel’s Custom CSS and Custom JavaScript boxes sit at agency level, so by default whatever you paste applies across all sub-accounts. To give one client an Arabic 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. The details are on our single sub-account page.

One limit applies: the login page comes before anyone opens a sub-account, so a design limited to certain sub-accounts cannot change it. Brand the login through HighLevel’s own white-label settings.

What can go wrong, and what doesn’t an Arabic theme solve?

Most problems come from mixed-direction text, untested inner screens and promises that went further than the setup. A theme changes how HighLevel’s menu and main screens look and read; it does not translate HighLevel’s own pages or your clients’ content, and it does not make HighLevel fully right-to-left.

There are also limits no theme removes. HighLevel does not officially support custom code, so a platform update can require a theme refresh. A theme works in the web browser; it does not change HighLevel’s mobile app, its system emails or its builders. And no menu translation makes up for poorly written Arabic content: if the messages your client’s customers receive read like machine translation, the polished dashboard will not save the relationship. Budget for a native Arabic writer.

How does GHL Dashboard Builder handle Arabic?

GHL Dashboard Builder translates HighLevel’s menu and navigation into Arabic, switches the layout to right-to-left, lets you rename any menu item in your own Arabic or English wording, and installs as one CSS line and one JavaScript line in HighLevel’s custom code settings. Here is what it does today, from our own feature list.

• Arabic menu and navigation. A built-in Modern Standard Arabic pack for the menu and navigation, with right-to-left switched on automatically. Arabic is one of 15 languages, alongside Urdu and Hebrew, which also read right to left.
• Your own wording. Override any translated label, so a clinic sees Patients in Arabic and a broker sees Deals.
• Menu editor. Rename, reorder, hide and badge any of HighLevel’s 19 menu items.
• Arabic fonts. Arabic-capable Google Fonts such as Noto Sans Arabic, IBM Plex Sans Arabic, Cairo and Tajawal.
• One sub-account or a few. Limit the Arabic design to the clients who need it, from one install.
• 27 templates as starting points, including Executive, Clinic, Estate and Monarch, which our market pages suggest for Gulf clients. Browse them on the templates page.
• Privacy mode. An eye button in HighLevel’s header that blurs contact names, emails, phone numbers, the conversation list and deal values on screen-shares.
• No data access. The builder never connects to your HighLevel account and the installed code does not send data anywhere.

The language settings are part of the Pro and Agency plans. Starter gives you one branded dashboard from a template with colors, fonts, sidebar, header, menu, privacy mode and sub-account targeting, without the language section. Pro adds a fully custom design, menu renames, the dashboard in Arabic or any of our other languages, a login page design mockup and installation by us. The Agency plan adds new themes whenever you need them and re-checks after HighLevel releases, which matters when you run several Arabic clients with different wording. Current details are on the pricing page, and the features page separates what installs into HighLevel from what is preview only.

Starter (one-time, no Arabic)$149

Pro (one-time, Arabic included)$349

Agency (12 months, Arabic included)$1,188 a year

Arabic with right-to-left layout is included from Pro. The Agency figure is twelve monthly payments. Source: GHL Dashboard Builder pricing, October 2026 (Starter $149 one-time, Pro $349 one-time, Agency $99 per month).

What it does not do: Arabic mirrors the parts our theme restyles, not every inner screen of HighLevel. The installed code does not change HighLevel’s login page yet; we design the login screen with you, and login styling is being added where we have verified HighLevel’s login layout. Number and date formats in invoices and reports follow HighLevel’s own settings. Our FAQ answers questions about installing, removing and data.

If you serve a specific Arabic-speaking country, our market pages list the conventions we apply there, for example the Saudi Arabia market page and the Egypt market page.

What to do next

1. List your Arabic-speaking clients and, for each one, who logs in and which language they read best. Decide between an Arabic menu, an English menu with Arabic content, or both.
2. Write a one-paragraph scope for each client that says what will be Arabic and what stays in English, and send it before you start.
3. Ask each client about digits, date style, currency and the words they use for customers and deals, and record the answers.
4. Shorten your Arabic SMS templates, submit Arabic WhatsApp templates, and test one Arabic email in two mail apps.
5. Try the client’s colors and an Arabic menu in the builder, install on one sub-account first, and contact us if a client needs wording or a design no template covers.