GoHighLevel sub-account setup: the step-by-step order we use

The best GoHighLevel sub-account setup starts before you open the software: write down how the business sells, and how that might change as it grows. Then work in this order: business details and users, the phone number and A2P registration, the email sending domain, pipelines and custom fields, calendars, forms, workflows, integrations, and last a full test with a test contact.

The order matters because each step leans on the one before it. Forms write to fields that need to exist. Workflows text from a number that needs A2P approval. We’ve set up a lot of sub-accounts, and most of the broken ones we get asked to fix were built out of order.

What is a GoHighLevel sub-account?

A sub-account is one business’s workspace inside a HighLevel agency account. It holds that business’s contacts, pipelines, calendars, phone numbers, sending domain and workflows, kept apart from every other sub-account. An agency gives each client its own sub-account. A single business on HighLevel usually works in one.

Step 0: Map the sales process and plan for scale

Before anything is created, write down how the business actually sells: how leads arrive, who handles them, every step from enquiry to paid, and what happens after. Then ask how that will change. What happens when you add two sales reps, open a second location, or change the offer?

Most people skip this step, and it’s the biggest mistake we see. A sub-account built only for how the business works today can’t grow with it. The sales process changes, or two reps join, and suddenly the owner is rebuilding from scratch. Built around the sales process with growth in mind, the same change takes a few small tweaks.

You don’t need anything fancy here. A page of notes or a simple flowchart is enough. Every later step in this guide depends on it.

Should you load a snapshot?

For a single business, almost never. A snapshot is someone else’s sales process, and every company does things its own way. You’ll spend as long undoing it as you would building from scratch, so we build each business’s sub-account around its own process. (Agencies deploying the same niche build to many clients are different; that’s covered in GoHighLevel agency setup.)

Step 1: Create the sub-account

Create the sub-account from the agency view. On supported plans, HighLevel asks which type of account it is: a client’s account, or your own agency account used for internal work, SaaS plans and rebilling (checked Nov 8, 2026 on help.gohighlevel.com). Pick the client type for a client business.

Enter the business name, address, phone, website and time zone exactly as they appear on the business’s legal and tax records. The time zone controls when every reminder and workflow fires, and the business details feed A2P registration later.

Step 2: Add users and permissions

Add each person who will work in the account and give them only what they need. A front-desk user might need conversations and calendars but not settings or billing. Assign calendars and pipeline opportunities to real users now, because round-robin booking and lead assignment depend on it.

Step 3: Get a phone number and start A2P registration

Buy or port the business’s number, then start A2P 10DLC registration straight away. In the sub-account, go to Settings, then Phone System under Business Services, open the Trust Center tab and click Start Registration under A2P Messaging (SMS) (checked Nov 8, 2026 on help.gohighlevel.com).

A business with a Tax ID registers as a Standard Brand. Sole Proprietor brands are for one-person businesses with no Tax ID and come with lower messaging limits and one number per campaign. HighLevel notes that EINs issued in the last 15 days may be rejected.

What gets brands approved, in our experience: a working website with a privacy policy and terms of service, an EIN, business details that match the registration exactly, and no stray contact forms on the site. If you’ve already been rejected, see A2P 10DLC registration.

Step 4: Connect a dedicated email sending domain

Set up a dedicated sending domain before any email goes out. In the sub-account, go to Settings, then Email Services, then Dedicated Domain, and click Add Domain (checked Nov 8, 2026 on help.gohighlevel.com). HighLevel then gives you DNS records to add: SPF and DKIM TXT records, MX records and a CNAME.

Use a subdomain such as mail.yourbusiness.com. HighLevel requires one if the root domain already runs Google Workspace email, and a subdomain keeps marketing email from affecting the reputation of your everyday inbox. The domain is live once every record shows a green check.

Step 5: Build pipelines and custom fields

Map the sales process before building anything here. Each pipeline stage should be a real step a lead goes through, such as new lead, contacted, booked, showed and won. Add lost reasons, so you can see why deals die.

Then create the custom fields the business needs: lead source, service of interest, budget, and anything a workflow will branch on. Fields come before forms and workflows because both write to them.

Step 6: Set up calendars

Create one calendar per service or team member, with real availability, buffers between appointments and the right meeting location or video link. Connect each calendar to the pipeline so a booking moves the opportunity to the booked stage.

Step 7: Build forms and surveys

Build the forms the website, ads and landing pages will use. Map every question to a custom field, add consent text for SMS and email, and tag submissions by source so reports show where leads came from.

Step 8: Build the first workflows

Start with the workflows that protect revenue:

1. Speed-to-lead: an instant reply and a call task or power-dialer queue when a lead arrives.
2. Appointment confirmations and reminders: better still, ones that send short videos to pre-sell the call.
3. Nurture for leads who don’t book: testimonials, case studies and education, not “just checking in”.
4. Missed-call text back: so a missed call still gets a reply.

Name each workflow by what it does and number them in order. More on what to build is in GoHighLevel automation.

Step 9: Connect integrations

Connect the tools the business already uses: payment processor, booking or practice software, accounting, ad platforms. Use native integrations first. If there isn’t one, a webhook or a custom code step inside a workflow is usually cheaper and more reliable than a middleman. Zapier, Make or n8n come in when neither of those can do the job. In healthcare accounts, every tool that touches patient data needs its own BAA; see the GoHighLevel HIPAA compliance guide.

Step 10: Test with a test contact, then go live

Before launch, run a test contact through the whole journey: submit the form, receive the reply, book the calendar, get each reminder, move through every pipeline stage and trigger every workflow branch. Check that texts send, emails land in the inbox, and internal alerts reach the right person. Then delete or tag the test contact so it doesn’t skew reports.

Go-live checklist:

• A2P brand and campaign approved
• Sending domain records all verified
• Every form tested and mapped to fields
• Every workflow published, named and tested
• Users trained on what they’ll use day to day

Common mistakes in GoHighLevel sub-account setup

These are the problems we see most often in sub-accounts that need fixing. The first one causes most of the others:

• Not building for future scale. The setup works for today’s process, then breaks the moment the process changes, reps are added or the business grows. A well-planned account absorbs those changes with small tweaks. A rushed one usually has to be started again.
• No account structure: pipelines, fields and tags added as needed, so nothing lines up.
• Pipelines that don’t match the sales process: stages nobody uses, and lost deals left open.
• Deprecated workflow actions still running inside live workflows.
• Workflows far more complex than they need to be, with branches nobody can follow.
• No naming system, so finding what sent a wrong message means opening every workflow.
• No lead source tracking or reporting, so nobody knows which channel or sales rep is working.

Should you set it up yourself?

You can, and this guide gives you the order to do it in. Our honest view: DIY makes the most sense when there’s no budget for help. If there is some budget, a proper setup tends to pay for itself, for three reasons:

1. It works the way it should. A DIY setup can usually be taped together, but it often breaks under real volume, and when one piece fails, others follow.
2. Your time is better spent on the business. A GoHighLevel build is complex, and every hour learning it is an hour away from customers.
3. It’s built for later. Someone who has set up around 200 accounts knows the problems you’ll hit with new reps, new locations or a changed offer, and can plan for them now.

If you’d rather hand it over, our GoHighLevel setup page explains how that works; our builds take about 23 days on average. If you’re doing it yourself, follow the steps above in order and don’t skip step 0.

Sources

• HighLevel, “What is an agency sub-account in HighLevel?”: https://help.gohighlevel.com/support/solutions/articles/155000007979-what-is-an-agency-sub-account-in-highlevel- (checked 2026-11-08)
• HighLevel, “Registering your A2P brand”: https://help.gohighlevel.com/support/solutions/articles/155000008140-registering-your-a2p-brand (checked 2026-11-08)
• HighLevel, “Google dedicated sending domain setup (LC Email)”: https://help.gohighlevel.com/support/solutions/articles/48001240481 (checked 2026-11-08)