3 min read
How to onboard a client into a GoHighLevel sub-account without surprises
The first two weeks decide whether a client is profitable or a permanent support burden. This is the sequence, including the compliance items that block go-live if left late.
Quick answer
How should an agency onboard a client into GoHighLevel?
Onboard by collecting access and legal details first, starting number porting and messaging registration immediately because both are externally gated, then deploying the snapshot, connecting integrations, testing with real data, and finishing with a recorded handover that defines what the client owns.
Onboarding is where agency margin is made or lost, and almost all of the loss happens in the first two weeks through things that were not asked for early enough.
The two items that gate everything
Messaging registration and number porting are both controlled by third parties on their own timelines. Nothing you do speeds them up.
Every other task can be compressed by working harder. These two cannot. So they go first, before discovery, before the build, before anything — and the rest of the project is sequenced around them.
Teams that treat them as the last step ship a finished system that cannot send a text, and then spend two weeks explaining why.
The economics of consistency
A bespoke account is more satisfying to build and considerably more expensive to run. When a platform change breaks something across thirty identical accounts, you diagnose once and fix everywhere. When it breaks across thirty bespoke ones, you diagnose thirty times.
That is the real argument for snapshots, and it is stronger than the setup-time saving people usually cite. More on where the line sits in snapshot vs custom build.
The handover is not a formality
An hour spent recording a walkthrough and writing a one-page workflow map reduces ongoing support volume more than any other single hour in the project.
Clients who do not understand their system raise tickets for things that are working correctly. Clients who do understand it raise tickets for things that are actually broken, which are the ones you want to hear about.
The steps, in order
- Step
Collect access and legal details before anything else
Legal entity name, registered address, tax ID, domain and DNS access, existing phone numbers and carrier, ad platform access, and the current CRM if one exists. Chasing these later is what turns a two-week onboarding into a six-week one.
- Step
Start messaging registration on day one
For US clients, A2P 10DLC brand and campaign registration is externally vetted and cannot be rushed. Submit it before you build anything. A finished system that cannot send messages is not a finished system, and this is the most common cause of a delayed launch.
- Step
Start number porting on day one too
Porting is carrier-controlled and is the longest-lead item in most onboardings. Submit immediately and sequence the rest of the build around the porting date rather than the other way round.
- Step
Run a discovery session on the actual process
How leads arrive, who works them, what the stages really are, what happens out of hours, and what the client believes is broken. Record it. Half of what you learn will contradict what was said during the sale, and it is better to find that out now.
- Step
Deploy the snapshot, then adjust rather than rebuild
Load the core snapshot for consistency, then apply the client-specific layer — their stages, their messaging, their booking rules. Resist rebuilding from scratch for a client who is only slightly different; the support cost of a bespoke account is paid every month afterwards.
- Step
Connect integrations and verify each one both ways
Ad platforms, calendars, payments, the client's own systems. Test that data flows in and that conversions flow back out. One-way testing is why attribution silently breaks two months in.
- Step
Configure email and domain authentication
SPF, DKIM and DMARC on the sending domain, plus a branded link domain for SMS. Both are DNS changes that require client access, and both materially affect whether messages arrive at all.
- Step
Test with real data before going live
Submit a real enquiry through every live channel. Confirm the contact is created with correct field mapping, the first-response automation fires, the message is genuinely delivered rather than merely sent, and the booking lands on the right calendar with the right owner.
- Step
Hand over with a recording and a one-page map
A recorded walkthrough plus a page listing every workflow, its trigger, its exit condition and its owner. This is the single highest-leverage thing you can do to reduce ongoing support load, and it takes an hour.
- Step
Define the support boundary in writing
What is included, what is billable, response times, and who the client contacts. Ambiguity here is what turns a profitable retainer into an unprofitable one, and it is much harder to introduce later than to state up front.
Questions
Related questions
How long should GoHighLevel onboarding take?
Two to three weeks for a standard build using an existing snapshot, assuming access is supplied promptly. The variable is almost never the build — it is messaging registration and number porting, both of which are externally gated and cannot be compressed by working harder.
What blocks go-live most often?
Messaging registration. A2P 10DLC brand and campaign approval is vetted externally and frequently rejected for mismatched business details or a missing consent mechanism. Starting it on day one rather than at build completion removes most of the risk.
Should every client get the same snapshot?
Use a core snapshot for what is genuinely universal — naming conventions, tagging, standard sequences, compliance plumbing — and a short custom layer for what is not. Roughly 80% loaded and 20% built keeps onboarding fast without forcing clients into a process that does not match how they sell.
What should the handover include?
A recorded walkthrough, a one-page map of every workflow with its trigger and exit condition, the list of connected integrations, and a written support boundary. Clients who understand their own system raise far fewer tickets, and the ones they do raise are better ones.
Services mentioned here
Client sub-accounts configured to the same standard every time
Sub-account setup covers provisioning a client location — deploying the snapshot, configuring branding, adding users with correct permissions, provisioning phone numbers, connecting the sending domain, submitting messaging compliance registration, and connecting the client's own integrations.
Snapshots that deploy cleanly instead of carrying mess
A GoHighLevel snapshot is a reusable template of a sub-account containing its pipelines, workflows, funnels, calendars, custom fields, forms and campaigns. Loading it into a new sub-account recreates that configuration in minutes, making client delivery repeatable rather than rebuilt each time.
Run GoHighLevel as your own platform
GoHighLevel white labeling replaces the platform's branding with the agency's own — a custom login domain, agency logo and colours throughout the interface, branded system emails, and optionally a branded mobile app. Clients log into what appears to be the agency's own software.