Webly Studio · GoHighLevel
The GoHighLevel Client Onboarding Checklist
The 30 steps we run on every new client sub-account, in the order that works. Tick them off; each one names the screen it lives on. Companion to weblystudio.com/blog/gohighlevel-client-onboarding-checklist/ (September 2026).
Before the kickoff (collect once, use everywhere)
- Signed agreement and the go-live date agreedYour contract, not GoHighLevel
- Legal company name exactly as it appears on the IRS CP 575 letter, plus the EINNeeded for A2P brand registration; a mismatch is the top rejection
- Business address, website, hours, time zone, industry and legal entity typeBusiness Profile fields
- Owner or Manager access to the Google Business ProfileThe Google account that holds it
- Admin on the Facebook Page and its Business ManagerFor the Facebook and Instagram connection
- Domain registrar login, or a person who can add DNS recordsFor the sending subdomain and the funnel domain
- Logo, brand colors, and any existing contact list with proof of consentMedia and import
Day 1: the account
- Create the sub-account as “This is my client’s account”Agency View > Sub-Accounts > Create
- Load the snapshot; remember funnels and websites arrive as draftsAccount Snapshots > Create Sub-Account
- Complete the Business Profile, every fieldSub-account Settings > Business Profile
- Fill the custom values the snapshot expects (name, phone, hours, links)Settings > Custom Values
- Add the client’s people: Admin for the owner, User with Only Assigned Data for staffSettings > My Staff
Week 1: phone and texting
- Buy one local number; forward it to the client’s cell with Call Connect onSettings > Phone Numbers
- Register the A2P brand: Standard if the business has an EIN, Sole Proprietor only if it doesn’tSettings > Phone System > Trust Center
- Register the campaign with real sample messages and the consent languageTrust Center > Campaigns
- For SaaS sub-accounts, clear 2FA before number purchaseManage Client page, or the client’s own code
- Missed call text back on, tested from your own phone (no texts send until the campaign is approved)Settings > Phone System > Voice
Week 1: email
- Add a dedicated sending subdomain, for example mg.clientdomain.comSettings > Email Services > Dedicated Domain and IP
- Add the SPF, DKIM, CNAME, MX and DMARC records; verify (minutes, up to 48 hours)Registrar DNS + Email Services
- From address on the same root domain as the sending domainEmail Services
- DMARC record present, starting with p=noneRegistrar DNS
- Unsubscribe link in every marketing template; watch the 0.30% spam lineEmail templates + Google Postmaster Tools
Week 1: integrations
- Connect Google Business Profile; turn on review syncSettings > Integrations
- Connect the Facebook Page and Business Manager; map lead form fieldsSettings > Integrations
- Each user connects their own Google or Outlook calendarCalendars > Calendar Settings > Connections
- Connect Stripe if the client takes paymentsPayments > Integrations
Weeks 2 and 3: build, test, hand over
- Pipeline stages named for the client’s real process; calendars with availability, buffers and remindersOpportunities, Calendars
- Workflows live: new lead reply, review request, appointment remindersAutomation > Workflows
- Publish funnels and websites on the client’s domain (snapshot drafts are not live)Sites > Domains
- One live lead from every source, end to end; then the training session and the handover documentConversations, LaunchPad
The order matters. Phone registration first because nothing texts until the carriers approve, email next because verification can take a day, integrations before the workflows that depend on them, and the live test before the training. Track it per client in Project Management (Sub-account > Project Management) so each step is assigned and dated.