GoHighLevel Client Onboarding Checklist: The 2026 Agency SOP (Free Download)

What goes on a GoHighLevel client onboarding checklist?

Thirty steps in six groups, which is the whole client onboarding process. What you collect before kickoff, the account on day one, phone and texting, email, integrations, and the build-test-handover stretch. The order isn't cosmetic. Texting waits on carrier approval, email waits on DNS, and every workflow depends on the integrations under it. Run them out of order and the client's first month is spent waiting.

HighLevel's own in-app LaunchPad, updated 11 September 2026, is an onboarding workspace grouped by outcome: setup, marketing, sales, website. It's useful for the client, but it isn't an ordered SOP, and there is no official numbered client onboarding article on the help site.

This is ours.

What do you collect before the kickoff call?

Seven things, and one of them decides whether texting works on time: the legal company name written exactly as the IRS printed it. HighLevel's brand approval guide, updated 1 September 2026, says to "Enter your Legal Company Name exactly as registered with the IRS." It adds: "An exact match between the Legal Company Name and the EIN as displayed on CP 575 is required." The DBA, the trade name and your agency's name all fail the match.

1. 01Signed agreement and a go-live date. The date drives the order below; the carriers won't move faster because the client is impatient.
2. 02Legal company name from the CP 575 letter, plus the EIN. Ask for a photo of the letter. If the business has no EIN, it registers as a sole proprietor with lower limits.
3. 03Business address, website, hours, time zone, industry and legal entity type. These are the Business Profile fields, and the profile applies across the whole sub-account.
4. 04Owner or Manager access on the Google Business Profile. The GBP connection needs the Google account that holds it.
5. 05Admin on the Facebook Page and its Business Manager. The Facebook connection requires both.
6. 06Domain access, or a person who can add DNS records. You need it twice: the email sending subdomain and the funnel domain.
7. 07Logo, brand colors, and any contact list with its consent proof. A list without consent records is a list you can't text.

What does a GoHighLevel snapshot copy into the new account?

Configuration, not activity. HighLevel's snapshots overview, updated 7 May 2026, calls them "reusable templates that capture selected configuration assets from a HighLevel sub-account" for copying into new or existing sub-accounts. The principle is stated plainly: "Snapshots are designed to transfer configuration and selected reusable assets, not live account activity or customer records." The full snapshot guide covers sharing, updates and the QA pass.

Two consequences for the checklist. First, the snapshot's funnels and websites arrive as drafts. They "won't be live until you connect a custom domain and publish them," per HighLevel's create-from-snapshot guide, which is why domain access sits in the kickoff list. Second, every integration and every phone number is set up fresh, per client, every time. That's most of week one.

The new client onboarding checklist, in order

Day one is the account itself. Create the sub-account with the "This is my client's account" option, which HighLevel's sub-account guide reserves for a client's business as opposed to your agency's own workspace. Load the snapshot, complete the Business Profile, fill the custom values the snapshot expects, and add the client's people.

Day one: the account

On people, the user roles page (4 September 2026) draws the line we follow. An Admin has "full access to all modules and settings in the sub-account"; a User has "restricted access; granular permissions apply." Staff who should only see their own leads get the Only Assigned Data setting. It limits them to contacts assigned to them, opportunities they own, and their own appointments and tasks. The owner is the Admin. Nobody else needs to be.

Week one: phone and texting

1. 01Buy one local number and forward it to the client's cell with Call Connect on, so a cell voicemail can't answer the call and mark it complete.
2. 02Register the A2P brand in the client's entity. The brand registration guide (24 August 2026) is explicit. "If your business has an EIN, Tax ID, Business Number, or other accepted business registration number, you must register as a Standard Brand." Sole proprietor brands are for businesses without one and are "limited to 1 phone number per campaign."
3. 03Register the campaign with the real sample messages and the consent language from the client's forms. Our A2P registration guide has the rejection codes and fixes.
4. 04On SaaS sub-accounts, clear two-factor first. HighLevel can require 2FA before a new SaaS sub-account buys a number; agency admins can verify it manually from the Manage Client page.
5. 05Turn on missed call text back and test it from your own phone. Nothing sends until the campaign is approved, so set it up now and test again the day approval lands. The missed call text back setup guide covers the timeouts.

One agency-specific trap. Twilio's error 30898 fires for one cause. "You registered multiple Brands with the same EIN, and the number of Brand registrations exceeded what campaign vetting allows without a clear and valid business reason." Register each client once, in their own sub-account, under their own EIN.

Never register a client under the agency's EIN to save a step.

Email, integrations and the build: weeks one to three

Thirteen steps across weeks one to three, and none of them can start early. DNS has to verify before a single email goes out, the workflows read from the integrations, and training waits for a live test. The three workflows, and the nine that follow them, are laid out in our twelve GoHighLevel automations.

Week one: email

Give every client a dedicated sending subdomain. Per HighLevel's sending domains guide (17 April 2026): "Use a unique subdomain not used for any other purpose. For example, if your root domain is yourbrand.com, create a subdomain like mg.yourbrand.com." Add the SPF, DKIM, CNAME, MX and DMARC records it generates. Verification, per the DNS guide, takes "Typically within 1–10 minutes, but in rare cases DNS propagation can take up to 24–48 hours."

Week one: integrations

Google Business Profile, the Facebook Page, calendars and Stripe. Two details from the docs change who has to be on the call. Calendars connect per person, not per account: HighLevel's Google calendar guide says "Calendar integrations are tied to individual user profiles, not global company settings. Each user should connect their own Google Calendar." And the Facebook connection needs someone who is "an Admin of the Facebook Page and the associated Business Manager," which is often not the owner.

Weeks two and three: build, test, hand over

Pipeline stages named for the client's real process, and calendars with availability and buffers. The three workflows every account gets: new lead reply, review request, appointment reminders. Then the funnels, published on the client's domain, and one live lead from every source, end to end, before anyone is trained on anything. We run the training as two sessions, Admin and User, because the screens differ. The handover document lists every login, every number, every domain and the date each registration was approved.

How does GoHighLevel SaaS mode change onboarding?

It automates day one and leaves the rest. On the Agency Pro plan, the SaaS Configurator (updated 12 September 2026) packages access into subscription plans. After checkout, per the same page, "The sub-account is created or linked to the customer as applicable." Then "The configured snapshot is applied when a snapshot is attached to the SaaS plan." HighLevel's bulk-activation page states the plan requirement as the "$497/mo Pro plan," and the pricing page lists SaaS Mode under Agency Pro only.

What SaaS mode doesn't do is the part that takes the time. The snapshot lands, but the A2P registration, the sending domain, the Google and Facebook connections and the calendar links are still per client and still manual. Our checklist for a SaaS client skips two boxes on day one and keeps the other 28. Budget the same three weeks, and read our white label and SaaS mode explainer before you price the plan.

What does a client onboarding process cost, and how long does it take?

Three weeks of calendar time and under $40 in registration fees per client, on top of the platform fee in our GoHighLevel pricing breakdown. The time is mostly waiting: the 10-to-15-day campaign review in our A2P registration guide, DNS propagation, and the client finding their logins. The fees are the A2P lines above: $24.50 one-time for most single-location clients and $2 to $10 a month after. Add $1.15 a month for the local number, per HighLevel's phone pricing guide.

Tenure is the reason to get it right the first time. The 4A's and ANA published their 2025 client-agency tenure report on 30 April 2025. It found "the average client-agency relationship tenure now stands at approximately seven years, more than double the 3.2-year average reported in 2016." That study covers large-brand agency-of-record relationships, not small GoHighLevel resellers, so treat it as direction rather than a benchmark. Our read, not the study's: relationships last when the first month works.

How we run this for clients

We run this new client onboarding checklist inside each sub-account's Project Management module, one task per step. HighLevel's introduction (16 September 2026) names this use exactly: "Run a repeatable onboarding checklist per customer, with each step assigned and dated." The kickoff call ends with the seven collection items assigned to the client with dates. Day one happens the same day the CP 575 photo arrives.

The two steps that slip most are the ones outside GoHighLevel: the Facebook Business Manager admin and the DNS records. We ask for both on the kickoff call and again in the day-one email, and we don't schedule training until the live-lead test has passed on every source. The complete setup guide is the long version of the build steps; this client onboarding checklist is the order and the paperwork around them. If the account is already half-built by someone else, start with the 12-point audit instead.