GoHighLevel Agency in Pakistan: White-Label Guide With Urdu

A clinic in Lahore signs up for the platform you sold them. The receptionist logs in and sees an English menu built for an American marketing agency, amounts in dollars, appointment times an hour off because the account was copied from a Dubai client, and a payment link that cannot take a local card. Nothing is broken, yet the software feels like it was made for somewhere else and rented to them.

This guide is for anyone running a GoHighLevel agency in Pakistan or for Pakistani clients: agencies in Karachi, Lahore and Islamabad that serve local businesses, Pakistani agencies that serve clients abroad, and overseas agencies with Pakistani customers. It covers what is specific to this market in HighLevel (also called GoHighLevel or GHL): Urdu, Roman Urdu and English, right-to-left layout and Nastaliq fonts, rupee and date formats, payments, PTA’s SMS rules, data law 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.

What is different about running a GoHighLevel agency in Pakistan?

The technical route is the same as anywhere: HighLevel’s built-in white-label settings for your identity, then custom code for the look and the menu language. What changes in Pakistan is the language mix on a client’s team, the way people pay, and the rules on promotional SMS. Each of those affects what you set up in a sub-account and what you promise in a sales call.

If you have not set up the identity layer yet, start with our guide on how to white-label HighLevel. It covers the logo, custom domain and legal links under Settings, Company, Whitelabel, and explains why those settings do not change colors, menu wording or language. Everything below assumes that layer is done.

The table compares a default English HighLevel with what a typical Pakistani client team expects.

Two kinds of Pakistani agency

Pakistan has two quite different GoHighLevel agency models, and this guide serves both. The first sells HighLevel to Pakistani businesses: clinics, schools, academies, restaurants, real estate offices and retailers. For them, the Urdu menu, rupee amounts and local payments matter most.

The second runs from Pakistan but sells to clients in the United States, the United Kingdom, the Gulf or Australia. For that model, the client-facing dashboard follows the client’s market, and the Pakistani side shows up in your own team: support staff in Asia/Karachi time, demos given across time zones, and screen-shares that must not expose an overseas client’s contacts. Both models benefit from treating each client’s sub-account as its own market rather than copying one setup everywhere.

Should a Pakistani client’s dashboard be in Urdu, English or Roman Urdu?

Ask who logs in. Urdu script with a right-to-left layout suits front-desk, sales and operations staff who read Urdu comfortably. English suits teams who already use English software every day. Roman Urdu, Urdu typed in Latin letters, is common in messages and can appear in menu labels if the team prefers it. Many clients need two of the three.

Pakistan’s constitution makes Urdu the national language and allows English to continue for official purposes until Urdu replaces it, under Article 251. In 2015 the Supreme Court ordered that article to be implemented, as Business Recorder reported, yet English remains common in business software, banking apps and office email. That is why Pakistani teams are often comfortable with an English interface while speaking and texting in Urdu.

Roman Urdu is how many people type

Many Pakistanis write Urdu in Latin letters on their phones. In a nationwide 2009 survey by Gilani Research Foundation and Gallup Pakistan, 37 percent of respondents said they send SMS in Urdu typed in the English alphabet, 17 percent typed SMS in English and 15 percent in the Urdu alphabet. The survey is old and predates smartphones being everywhere, so treat it as a sign of a habit, not a current measurement.

Urdu in Latin letters (Roman Urdu)37%

English17%

Urdu script15%

An older survey: use it as a sign of the Roman Urdu habit, not as a current figure. Source: Gilani Research Foundation and Gallup Pakistan survey, as reported by ProPakistani, December 2009. Remaining respondents gave other answers or did not send SMS.

For a HighLevel setup, this has a practical consequence. The menu your client’s team reads every day can be English or Urdu script, but the SMS and WhatsApp messages their customers receive are often best in Roman Urdu or a short mix, because that is how the customers write back. Ask your client to show you a few real messages from their phone before you write any templates.

What HighLevel offers natively

HighLevel has started translating its interface. HighLevel’s help center article on internationalization explains that a sub-account’s default language is set under Settings, Business Profile, Platform Language, and each user can override it under Settings, My Profile. A sub-account is one client’s workspace in HighLevel, which HighLevel also calls a location. The languages listed at the time of writing are European ones. Urdu is not among them.

HighLevel is also not right-to-left aware as a whole. A public request on HighLevel’s ideas board for right-to-left text direction support names Urdu alongside Arabic, Hebrew and Persian, without a release date. Check both pages before you tell a client what will or will not appear in Urdu, because HighLevel ships changes often.

What a theme adds, and what stays in English

Until HighLevel supports Urdu natively, agencies add it to HighLevel’s menu and navigation with custom code. A theme can translate the menu labels, switch the page direction to right-to-left, move the sidebar to the right and use a font designed for Urdu. It cannot translate text inside HighLevel’s own pages, builders, system emails or mobile app; those follow HighLevel’s language settings.

So the honest promise to a Pakistani client is: “Your team’s menu and navigation will be in Urdu and the main screens will read right to left. Some inner settings pages and the builders stay in English.” Most Pakistani office teams already work in English software, so this split is usually acceptable, as long as you say it before the sale. Our guide to giving clients an Arabic HighLevel dashboard explains in more detail how a mirrored layout behaves, because Urdu uses the same right-to-left mechanics.

Nastaliq or Naskh?

Urdu is usually printed in Nastaliq, a flowing, sloped style of the Arabic script, while Arabic is usually printed in the more upright Naskh. A menu set in an Arabic Naskh font is readable to Urdu speakers but looks foreign to many of them, much as an English menu set in a German blackletter font would. Nastaliq is also taller, so it needs more line height than Latin text. When you test an Urdu menu, check that dots and descenders are not cut off in buttons and narrow menu rows.

How does GHL Dashboard Builder handle a Pakistan setup?

GHL Dashboard Builder translates HighLevel’s menu and navigation into Urdu, switches the layout to right-to-left, lets you rename any menu item in Urdu, Roman Urdu or English, limits a design to the clients who need it, and installs as one CSS line and one JavaScript line. It does not translate HighLevel’s inner pages.

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 a Pakistani agency, the relevant pieces are the Urdu language pack, the menu editor, Urdu fonts, sub-account targeting, privacy mode and the three templates we suggest for this market. Everything below comes from our features page.

What the Pakistan setup includes

• An Urdu language pack. The menu, the sidebar’s search and sub-account switcher, the header’s search box, notifications and profile menu, and common buttons are translated into Urdu. Urdu is one of 15 languages, and one of 3 that read right to left, alongside Arabic and Hebrew.
• Automatic right-to-left. When the language is Urdu and direction is automatic, the sidebar moves to the right and the page direction switches.
• Urdu fonts. Noto Nastaliq Urdu and Gulzar for Nastaliq, and Noto Naskh Arabic if a client prefers the upright style.
• Menu editor. Rename, reorder and hide any of HighLevel’s 19 menu items, with New and Beta labels and your own custom items, so a school sees Courses and a clinic sees Patients, in Urdu, Roman Urdu or English.
• One sub-account or a few. Limit a design to chosen sub-accounts, by link or Location ID, while the rest keep their current look.
• Privacy mode. An eye button in HighLevel’s header that blurs contact names, emails, phone numbers, the conversation list and deal values.
• 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

What it costs

All three plans are one-time payments with no monthly fee, billed in US dollars. Starter ($180) gives you one branded design from any of the 27 templates, without the language section or the menu editor. Pro ($280) adds up to 3 designs, the menu editor, the dashboard in Urdu or any of the other 14 languages, the branded login page and installation by us. Agency ($880) adds up to 100 designs, a look designed by our team, custom code and lifetime updates. Starter and Pro include 12 months of updates, then optional at $99 a year. Current details are on the pricing page.

Starter (one-time, no Urdu)$180

Pro (one-time, Urdu included)$280

Agency (one-time, Urdu included)$880

Urdu with right-to-left layout is included from Pro. Source: GHL Dashboard Builder pricing, October 2026. All three plans are one-time payments in US dollars with no monthly fee.

We do not convert these prices into rupees here, because the rupee floats against the dollar and any figure would be out of date quickly. Check your bank’s rate on the day you pay, and expect your card issuer to add its own foreign transaction charges.

What the client sees afterwards

After installation, a user in an Urdu sub-account logs in on your white-label domain and sees the sidebar on the right, in your colors, with Urdu labels such as گفتگو (Conversations), رابطے (Contacts), مواقع (Opportunities) and ترتیبات (Settings), set in a Nastaliq font. The header search box reads in Urdu. When they open a deep settings page or a builder, they see HighLevel’s own English text. A user in an English sub-account of the same agency sees English, because the design is limited to the sub-accounts you chose.

How should rupees, dates and times appear for Pakistani clients?

Set each sub-account to PKR and the Asia/Karachi time zone, write dates day before month, and use the 12-hour clock most Pakistanis read. Browser defaults for Pakistan are close to what clients expect, so most of the work is changing settings that were copied from another market.

What browsers do by default

Browsers format numbers and dates using the Unicode Common Locale Data Repository (CLDR). We formatted the same amount and date in Node.js 22 with ICU 77.1, which ships CLDR version 47. Browsers use the same data, though versions vary.

Four practical points follow from this table.

1. Western digits are the default for Urdu in Pakistan. Unlike Arabic for Saudi Arabia, ur-PK writes 1, 2, 3 by default. Eastern Arabic-Indic digits (۱، ۲، ۳) exist for Urdu, but most business software in Pakistan uses Western digits, and phone numbers are always typed that way. Keep Western digits unless a client asks otherwise.
2. A copied US setup writes the month first. In en-US, 12 October becomes 10/12/26, which a Pakistani receptionist reads as 10 December. If a sub-account or user was created with US settings, change it, or write the month as a word in templates.
3. The 12-hour clock is normal. Both Pakistani locales show 2:30 PM, not 14:30. Appointment confirmations should match: “Tuesday 14 October, 4:30 PM” reads naturally.
4. Rs, not PKR, in front of amounts. The locale data shows the rupee as Rs. Use the same form in invoices, payment links and message templates so the amount looks the same everywhere.

Lakh and crore

Pakistanis often talk about money in lakh (100,000) and crore (10 million) rather than in hundreds of thousands and millions. A property dealer will say a plot costs “85 lakh”, not 8.5 million. The CLDR data above groups digits in thousands (1,250,000), so HighLevel and browsers will not show 12,50,000. That is fine for invoices, but in messages and opportunity names, write amounts the way the client’s customers say them, such as “Rs 85 lakh”.

Time zone and the working week

Pakistan uses one time zone, Pakistan Standard Time (UTC+5), and has not observed daylight saving time since 2009, as the Wikipedia article on time in Pakistan records. Set each sub-account’s time zone to Asia/Karachi in Settings, Business Profile. The offset never changes, which makes scheduling simpler than for clients in the UK or US.

The working week varies more than in the Gulf. Banks and many offices close on Saturday and Sunday: the State Bank of Pakistan moved banks to a five-day week in 2010, as its 2010 circular on banking hours shows, and many offices take a longer break at Friday midday for prayers. Shops, clinics, schools and restaurants often open on Saturday and into the evening. Ask each client for their real hours instead of assuming.

1. Calendars. Set booking hours per calendar, with the client’s real Saturday hours and a gap around Friday prayers if they close for them.
2. Workflows. Where a workflow waits for business hours before sending or creating a task, set the window to the client’s days, not a copied Monday-to-Friday.
3. Ramadan. Office hours change during Ramadan, and the federal government announces its own timings each year, as in this Press Information Department notice on Ramzan office timings. Save a Ramadan version of each client’s hours, and move customer-facing messages away from iftar time.
4. Eid. Block Eid al-Fitr and Eid al-Adha in calendars once dates are announced, and pause promotional campaigns during them unless the campaign is about the holiday.

How do you take payments for Pakistani clients through HighLevel?

Confirm early which payment provider your client can actually use. HighLevel’s checkout features work best with Stripe, which is generally not open to Pakistan-registered businesses, so many Pakistani setups use another supported provider, manual payment methods for bank transfers and wallets, or payment links from a local gateway outside HighLevel.

What HighLevel supports

HighLevel’s help article on where payment providers work lists Stripe, PayPal, Square, NMI, Authorize.net and Razorpay, and shows which product areas each one covers: order forms, invoices, payment links, subscriptions and so on. Coverage differs by provider, so check the table for the exact feature your client needs before you choose.

At the time of writing, Pakistan is not among the countries where businesses can open a Stripe account, according to Stripe’s global availability page. Some agencies use a company registered abroad for their own billing, but that is a legal and tax decision for your client’s accountant, not a workaround to suggest casually.

Manual payments for local methods

HighLevel lets a sub-account record payments that happen outside an online gateway. HighLevel’s help article on manual payment methods explains that you set them up under Payments, Integrations, Manual Payment Methods, either as Cash on Delivery or as a custom method, and staff then mark the order as paid. For Pakistani clients, typical custom methods are bank transfer, Raast and mobile wallets.

Raast is the State Bank of Pakistan’s instant payment system. In September 2023 the SBP added person-to-merchant payments, which let merchants and small businesses receive customer payments in real time, as ProPakistani reported. A clinic can send a HighLevel invoice with its Raast ID and bank details in the notes, then mark it paid when the transfer arrives.

Your own costs are in dollars

HighLevel bills agencies in US dollars, and its main plans are listed at $97, $297 and $497 a month at the time of writing on HighLevel’s pricing page. A Pakistani agency that charges clients in rupees carries the exchange-rate risk. Two common ways to manage it are pricing retainers in dollars for overseas clients, and reviewing rupee prices for local clients at a fixed point each year rather than absorbing every move.

What are the SMS and WhatsApp rules for Pakistani clients?

Promotional SMS in Pakistan needs consent, an approved sender ID and a way to unsubscribe, under rules enforced by the Pakistan Telecommunication Authority (PTA). Urdu-script messages fit fewer characters per segment than English or Roman Urdu. WhatsApp templates need approval in each language you send.

PTA’s spam rules and the Do Not Call Register

PTA’s Protection from Spam, Unsolicited, Fraudulent and Obnoxious Communication Regulations, 2009 govern marketing messages. In 2021 PTA directed all four mobile operators to implement its Do Not Call Register (DNCR) in letter and spirit and to stop messages to subscribers who had not opted in, messages from unapproved sender IDs or short codes, and unapproved content, as ProPakistani reported. Any subscriber can block telemarketing by texting REG to 3627.

For a HighLevel setup, this means four habits:

1. Record consent. Every form that collects a phone number for marketing needs a consent line, and every imported list needs a known source.
2. Keep opt-out working. Leave STOP handling on and honor opt-outs in workflows.
3. Separate reminders from promotions. Appointment confirmations and payment reminders are different traffic from offers; build them as separate workflows.
4. Register the sender. Ask an SMS provider that serves Pakistan how your client’s sender name is registered. According to Twilio’s Pakistan SMS guidelines, sender IDs may be replaced by carriers to ensure delivery, so recipients may not see the name you set.

Urdu SMS is shorter per segment

An SMS that contains any Urdu letter is encoded as UCS-2. One segment then holds 70 characters, and a longer message is split into segments of 67 characters each, as Twilio explains in its UCS-2 guide. Plain English or Roman Urdu without special characters fits 160 characters in one segment. Each segment is billed.

English or Roman Urdu (GSM-7)160 characters

Urdu script, single message (UCS-2)70 characters

Urdu script, each part of a long message67 characters

Roman Urdu typed in plain Latin letters uses GSM-7, like English. Source: Twilio: What is UCS-2 character encoding? (GSM-7 160 characters in one segment; UCS-2, used for Urdu script, 70 in one segment and 67 per segment in a longer message).

This is one more reason Roman Urdu is common in Pakistani business texts: a 150-character reminder in Roman Urdu fits one segment, while the same message in Urdu script uses three. Use Urdu script where the client’s customers clearly prefer it, and keep those messages short: the date, the time, the place and one instruction.

WhatsApp templates

Many Pakistani businesses talk to customers on WhatsApp more than by SMS. WhatsApp templates are approved per language, and Urdu uses the code ur in Meta’s list of supported template languages. There is no separate code for Roman Urdu; a Roman Urdu template is usually submitted under English or Urdu, so ask your WhatsApp provider which they recommend. Create each template your workflows send in every language you use, and get them approved before launch.

What does Pakistani data law mean for your HighLevel setup?

At the time of writing, Pakistan has no comprehensive data protection law in force. The Prevention of Electronic Crimes Act 2016 (PECA) punishes misuse of personal information, and a Personal Data Protection Bill has been drafted but not enacted. Good practice still applies, and your overseas clients bring their own laws. This section is an overview, not legal advice.

DLA Piper’s guide to data protection in Pakistan states that Pakistan has not enacted specific data protection legislation, that PECA 2016 sets out penal sanctions against misuse of personal information, and that the Personal Data Protection Bill is yet to become law. PECA was amended again in 2025. Because a new law could pass at any time, check the bill’s status before you sign a large client, especially in healthcare or finance.

Why it still matters

The absence of a single law does not mean anything goes. PTA’s spam rules already require consent for marketing messages. Clinics hold sensitive health details in notes and conversations. And a Pakistani agency serving clients in the UK, the EU or the Gulf handles their contacts under those clients’ laws, not Pakistan’s.

Screen-shares are where data leaks

Pakistani agencies give a lot of demos: sales calls to new local prospects, support sessions with clients abroad, and recorded training for new staff. Each one can show real names, phone numbers and deal values to people who should not see them. A recorded walkthrough full of an American client’s leads, shared with a new hire in Lahore, is exactly the kind of exposure a client’s contract usually forbids. Blur client data before you share, every time.

Which industries and templates fit Pakistani clients?

Education, healthcare and restaurants are three client types a Pakistani agency is likely to meet, and each expects different words in the menu and a different look. The three templates we suggest for this market on our Pakistan page are built for them: Scholar, Clinic and Saffron.

We do not publish sector sizes or HighLevel adoption figures for Pakistan, because we have not found a reliable source that measures them. The table below is about fit, not market share.

Education and coaching

Academies and tuition centers run admissions, fee reminders and parent messages, often in a mix of Urdu and English. Scholar’s Courses wording fits them, and the welcome banner and live counts help a busy admissions desk see new enquiries at a glance. Admissions staff often prefer an Urdu menu; teachers and owners often prefer English. That is a good case for limiting the Urdu design to the admissions team’s sub-account, or for English labels in the school’s own words.

Clinics

Clinics need a calm interface a receptionist learns in a day, and reminders that reach patients the day before. Ask the clinic which word they use for patients and treatments in their own registers, in Urdu or English, and put that word in the menu. Our guide to HighLevel for dental and medical practices covers the clinic setup in detail, including reminders and privacy.

Restaurants

Restaurants live in reservations and WhatsApp. Saffron renames Calendars to Reservations, and its Urdu font is Gulzar, a Nastaliq face, so an Urdu menu keeps the warm, traditional feel of the brand. Evening hours and Ramadan iftar bookings matter more here than in any other client type, so set calendars accordingly.

Whatever template you start from, change the colors to your brand or your client’s, and check contrast. The W3C’s accessibility guidance sets a minimum contrast ratio of 4.5 to 1 for normal text; that matters even more for Nastaliq labels, whose fine strokes fade quickly on pale backgrounds.

How do you set up a white-label GoHighLevel for a Pakistani client, step by step?

Finish the identity layer, agree the language and payment choices with the client, prepare the sub-account for Pakistani conventions, then install and test the theme on one sub-account before rolling it out. The steps assume you have agency access and HighLevel’s white-label domain and logo are already set.

Step 1: Agree the basics with the client

1. List the people who will log in and the language each one reads best: Urdu, English or both.
2. Choose the menu language for the team, and whether labels should be in Urdu script, English or Roman Urdu.
3. Ask for the words they use for customers, deals and appointments, and for their real working days, Friday hours and Ramadan hours.
4. Ask how their customers pay today: card, bank transfer, Raast, wallet or cash.
5. Ask for a few real customer messages, to see whether customers write in Urdu script, Roman Urdu or English.

Step 2: Prepare the sub-account

1. Open the client’s sub-account and go to Settings, Business Profile.
2. Check the business name, address and phone number, with the +92 country code.
3. Set the time zone to Asia/Karachi.
4. Set the currency to PKR in the payment settings.
5. Under Payments, Integrations, connect the provider the client qualifies for, or add manual payment methods for bank transfer, Raast and cash.

Step 3: Prepare messages and consent

1. Write the key SMS, WhatsApp and email templates in the language the client’s customers use, keeping Urdu-script SMS short.
2. Add a consent line and a privacy policy link to every form that collects phone numbers.
3. Separate reminder workflows from promotional ones, and set send windows to the client’s working hours.
4. Confirm sender ID registration with the SMS provider and submit WhatsApp templates for approval.

Step 4: Install the theme on one sub-account

1. In the agency view, open Settings, Company, Whitelabel and scroll to Custom Code.
2. Copy anything already in the Custom CSS and Custom JavaScript boxes into a text file. That is your rollback.
3. Paste the theme’s CSS into Custom CSS and its JavaScript into Custom JavaScript, then save. HighLevel warns about third-party scripts; confirm only if you trust the code.
4. If the theme targets chosen sub-accounts, confirm the test sub-account is on the list.
5. Open the test sub-account in a new tab and hard-refresh.

If you want to understand what the CSS part can and cannot change before you paste anything, our guide to HighLevel custom CSS explains selectors, updates and safe practice. For the full list of what to brand before a client’s first login, use our GoHighLevel white-label checklist.

Step 5: Test like a Pakistani user

1. Ask an Urdu-reading team member to read every menu label and the sub-account switcher.
2. Walk through the dashboard, conversations, calendars, contacts, opportunities and payments.
3. Create a contact with an Urdu name, an English email and a +92 mobile number, and check alignment.
4. Check that Nastaliq labels are not clipped in buttons, the collapsed sidebar and narrow menus.
5. Check an amount in rupees and a date in day-first format.
6. Narrow the window to phone width and open the menu.
7. Turn on privacy mode and record a short test video to confirm names and numbers are blurred.

When the test sub-account looks right, add the next Pakistani client or apply the design more widely.

How is a Pakistan setup different from a Gulf setup?

Many Pakistani agencies serve Gulf clients too, and Gulf businesses often employ Urdu-speaking staff. The theme mechanics are the same for Urdu and Arabic, but the locale, week, currency and payment details differ enough that copying a Dubai or Riyadh sub-account to a Lahore client causes small, daily irritations.

Our guide to white-labeling HighLevel in the UAE covers the Emirates, including when an Urdu menu helps teams there. If your agency works in both markets, keep one design per market and target each at the right sub-accounts, instead of switching one design back and forth.

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

Most problems in Pakistani setups come from settings copied from another market, payment gateways chosen before checking eligibility, unregistered SMS senders and the expectation that translating the menu translates everything. Plan for them and tell clients in advance.

There are also limits no theme removes. HighLevel does not officially support custom code, so a platform update can require a theme refresh; that is what the 12 months of updates on Starter and Pro, and lifetime updates on Agency, are for. A theme changes how HighLevel looks in the browser; it does not translate your content, HighLevel’s builders, its system emails or its mobile app. Our theme does not change HighLevel’s login page code either: from Pro, we design the branded login page with you for your white-label sign-in screen. And a theme does not solve payments, sender registration or consent; those remain your responsibility and your client’s. Our FAQ answers questions about installation, removal and data.

What to do next

1. List your Pakistani clients and, for each, who logs in, which language they read best, and whether their customers text in Urdu script, Roman Urdu or English.
2. Fix the basics in every Pakistani sub-account: Asia/Karachi time zone, PKR currency, day-first dates, real working hours and a saved Ramadan schedule.
3. Check payment eligibility before you build checkout, and set up manual payment methods for bank transfer and Raast where a gateway is not available.
4. Add consent text to every form, separate reminders from promotions, and confirm SMS sender registration and WhatsApp template approvals before launch.
5. Try the Urdu preview in the free builder with your client’s colors, then install on one sub-account and test it with an Urdu reader before rolling it out.