Client Onboarding Ghl

Standard Operating Procedure: Client Onboarding - GoHighLevel (GHL)

1. Document Control Block

• Document ID: TR-SOP-GHL-ONB-001
• Effective Date: 2023-10-27
• Version: 1.0
• Review Cadence: Annually (last review: N/A)

2. Executive Summary & Scope

This Standard Operating Procedure (SOP) outlines the standardized process for onboarding new clients to the GoHighLevel (GHL) marketing and sales automation platform. The objective is to ensure a consistent, efficient, and secure transition of new clients from signed agreement to fully functional GHL sub-account, enabling immediate operational capability.

Scope: This SOP covers all activities from initial client agreement confirmation and internal sales-to-onboarding handoff, through GHL sub-account provisioning, initial configuration, integrations, client access provisioning, and basic system orientation. It concludes with the formal internal handoff to the Client Success / Account Management team.

Out of Scope: This SOP explicitly excludes pre-sales activities, advanced GHL customization (e.g., custom coding, complex API integrations beyond standard connectors), comprehensive client training beyond initial setup, ongoing client support, or advanced campaign development.

3. Prerequisites & Required Tools

3.1. Prerequisites

• Signed Client Service Agreement (CSA) or Master Service Agreement (MSA) with GHL services defined.
• Confirmed client payment details and initial invoice processing.
• Completion of initial client data collection form (e.g., business details, domain access, integration credentials).
• Internal Sales-to-Onboarding Handoff form completed and approved.
• Confirmation of client's GHL snapshot requirements (if applicable).

3.2. Required Tools & Systems

• GHL Agency Account: Administrative access to the Template Registry GHL Agency dashboard.
• Client Relationship Management (CRM) System: For tracking client interactions and status (e.g., Salesforce, HubSpot).
• Project Management (PM) System: For task tracking and workflow management (e.g., Asana, Jira).
• Secure Password Manager: For managing client credentials (e.g., LastPass Enterprise, 1Password).
• Communication Platform: For internal team coordination (e.g., Slack, Microsoft Teams).
• Email Communication System: For client communication (e.g., Google Workspace, Outlook).
• Domain Registrar/DNS Management Access: Client-provided access or direct instructions for DNS modification.
• Integrated Services Access: Client-provided credentials for services like Facebook, Google My Business, Stripe, Twilio, Mailgun/LeadConnector Email.
• Internal Knowledge Base: Access to GHL best practices, snapshots, and common configuration guides.
• Video Conferencing Software: For client kickoff and training sessions (e.g., Zoom, Google Meet).

3.3. Compliance & Security

• Adherence to internal data privacy policies (e.g., GDPR, CCPA).
• Strict credential handling via secure password manager.
• Utilize multi-factor authentication (MFA) on all accessed client accounts where available.

4. Roles & Responsibilities (RACI Matrix)

R: Responsible (Performs the task) A: Accountable (Ultimately answerable for task completion) C: Consulted (Provides input before decisions/actions) I: Informed (Kept up-to-date on progress)

5. Step-by-Step Procedure

Phase 1: Pre-Onboarding & Information Gathering

• 1.1. Internal Handoff & Project Initiation
  • Receive Sales-to-Onboarding Handoff Form from Sales Executive.
  • Verify completeness of Handoff Form (client details, agreed services, specific GHL requirements).
  • Create new client project in PM System, assign Onboarding Specialist.
  • Schedule internal kickoff meeting with relevant stakeholders (Sales, Onboarding, Technical Lead, Account Management).
• 1.2. Client Information & Access Credential Collection
  • Initiate client welcome email, confirming next steps and requesting required access credentials (e.g., DNS access, social media logins, API keys) via secure portal/form.
  • Securely store all client-provided credentials in the designated Secure Password Manager.
  • Confirm receipt of any required assets (logos, branding guidelines, content examples).
• 1.3. Service Agreement Verification
  • Review Client Service Agreement (CSA) to confirm scope of GHL services purchased.
  • Identify any specific customizations or integrations explicitly stated in the CSA.
• 1.4. Initial Billing Setup Confirmation
  • Confirm with Billing Specialist that initial payment has been processed and recurring billing is configured.
  • Verify client subscription level aligns with purchased services in GHL (if applicable to agency model).

Phase 2: GHL Sub-Account Creation & Configuration

• 2.1. GHL Sub-Account Provisioning
  • Log into GHL Agency Dashboard.
  • Navigate to 'Accounts' and select 'Create New Account'.
  • Select appropriate 'Snapshot' based on client's industry/service package (or 'Blank Account' if fully custom).
  • Enter client's business name, contact information, and desired sub-account URL.
  • Confirm account creation and verify sub-account appears in the agency dashboard.
• 2.2. Snapshot Application & Customization (if applicable)
  • If not applied during creation, apply the designated industry/service snapshot.
  • Review and adjust snapshot-provided funnels, websites, forms, surveys, and automation workflows to align with client-specific branding and initial requirements.
  • Update all placeholder content with client's actual information.
• 2.3. Domain & DNS Configuration
  • Request client to add CNAME record for www (pointing to flash.builderall.com or GHL's current CDN host) and an A record for the root domain (@) (pointing to GHL's designated IP, typically 34.64.6.98 or current).
  • Verify DNS propagation using an online DNS checker tool (e.g., dnschecker.org).
  • Connect the domain within the GHL sub-account under 'Settings' > 'Domains'.
  • Install SSL certificate for the domain within GHL settings.
• 2.4. Lead Connector & Third-Party Integrations
  • Integrate Google My Business (GMB) by connecting client's Google account under 'Settings' > 'Integrations'.
  • Integrate Facebook (Page & Ad Account) under 'Settings' > 'Integrations'.
  • Integrate Stripe for payment processing under 'Settings' > 'Integrations'.
  • Configure other required integrations (e.g., QuickBooks, Shopify) as per CSA.
• 2.5. Email/SMS Gateway Setup
  • Configure LeadConnector Email for transactional and marketing emails (default for most GHL accounts).
  • Verify domain verification for LeadConnector Email.
  • Configure Twilio for SMS/MMS messaging, purchasing a local number if required, under 'Settings' > 'Phone Numbers'.
• 2.6. Business Profile & Custom Values
  • Update client's 'Business Profile' under 'Settings' with accurate contact info, address, and logo.
  • Populate relevant 'Custom Values' in GHL with client-specific data (e.g., company phone, address, website URL).

Phase 3: Client Access & Handoff

• 3.1. Client User Creation & Permissions
  • Create primary client user account(s) under 'Settings' > 'Team Management'.
  • Assign appropriate user roles and permissions (e.g., 'Admin' for primary contact, 'User' for staff).
  • Provide client with instructions for logging in and resetting their password.
• 3.2. Initial Walkthrough & Training Preparation
  • Schedule an initial GHL orientation session with the client (typically 60-90 minutes).
  • Prepare a personalized agenda covering key configured areas and basic navigation.
  • Gather relevant introductory resources (GHL quick-start guides, FAQs) for the client.
• 3.3. Resource Sharing
  • Share links to Template Registry's GHL knowledge base, support channels, and relevant GHL documentation.
  • Provide contact information for their dedicated Account Manager.

Phase 4: Post-Onboarding & Verification

• 4.1. Internal Handoff to Account Management
  • Complete and submit internal 'Client Handoff' document to the assigned Account Manager.
  • Schedule internal handoff meeting to review client's GHL setup, agreed scope, and any outstanding items.
  • Ensure Account Manager has access to all client documentation and credentials.
• 4.2. Final Configuration Review
  • Perform a final system audit to confirm all steps in Phase 2 are complete and functional.
  • Test key functionalities: form submission, automation trigger, email/SMS send, domain access.
• 4.3. Documentation Archival
  • Archive all onboarding documentation, client communications, and configuration details in the designated client folder within the PM System and CRM.
  • Update client status in CRM to 'Onboarded'.

6. Quality Assurance & Verification

6.1. Key Performance Indicators (KPIs) & Thresholds

• Onboarding Completion Rate: 100% of all assigned onboarding tasks completed within the PM System.
• Time-to-Live (TTL): Client's GHL sub-account fully configured and accessible within 5 business days post-information receipt (unless custom development extends this).
• Initial Client Satisfaction Score: >4.0 on a 5-point scale for onboarding experience survey (sent post-handoff).
• DNS Propagation Time: Domain fully propagated and SSL active within 24 hours of client DNS update.

6.2. Common Pitfalls & Mitigation

• Incomplete Client Data/Credentials:
  • Mitigation: Pre-onboarding checklist with mandatory fields; structured client information request form; clear escalation path for missing data.
• Incorrect DNS Configuration:
  • Mitigation: Provide explicit, step-by-step instructions (screenshots/video) to clients; offer to perform DNS updates directly with client's permission and access; immediate verification via DNS checker.
• Integration Failures:
  • Mitigation: Verify API keys and connection permissions during setup; consult GHL documentation and integration-specific troubleshooting guides; escalate to Technical Lead for complex issues.
• Scope Creep During Onboarding:
  • Mitigation: Adhere strictly to CSA; document any new requests for future quoting/project phases; politely defer out-of-scope requests to Account Manager.
• Client Communication Gaps:
  • Mitigation: Regular updates via PM system or email; clear expectations set during kickoff; dedicated communication channel (e.g., Slack Connect) for real-time needs.

6.3. Audit Checklist

• Client Sub-Account created with correct snapshot.
• Business Profile fully populated and accurate.
• Domain connected and SSL active.
• All required third-party integrations (GMB, FB, Stripe) connected and tested.
• LeadConnector Email/Twilio configured and test emails/SMS sent.
• Client user(s) created with appropriate permissions.
• Initial automation workflows/funnels reviewed for client branding and accuracy.
• All client credentials securely stored.
• Client Handoff document submitted to Account Manager.
• Onboarding project marked 'Complete' in PM system.

7. Troubleshooting FAQ

Q1: Domain/Website not connecting after DNS updates, or SSL certificate not activating.

• Scenario: Client reports their custom domain website or funnel in GHL is not loading, or shows a security warning about SSL.
• Solution:
  1. Verify DNS Records: Use a tool like dnschecker.org to confirm that the CNAME record (www pointing to GHL CDN host) and A record (@ pointing to GHL IP) have propagated globally. DNS propagation can take up to 24-48 hours.
  2. Check GHL Domain Settings: In the GHL sub-account, navigate to Settings > Domains. Ensure the domain is correctly added and appears "Connected." If not, re-add.
  3. Force SSL Update: Within GHL domain settings, locate the domain and click the "Check Status" or "Refresh SSL" button. Wait 5-10 minutes and re-check.
  4. Clear Browser Cache: Advise the client to clear their browser cache or test in an incognito window.
  5. ISP DNS Cache: Rarely, local ISP DNS cache can cause issues. Advise client to try a different network or device.

Q2: Integrations (e.g., Facebook Leads, Stripe payments) are failing or not syncing data.

• Scenario: Client reports Facebook leads aren't appearing in GHL, or Stripe payments aren't processing/recording.
• Solution:
  1. Re-authenticate Integration: In the GHL sub-account, navigate to Settings > Integrations. Disconnect and then reconnect the failing integration. Ensure the correct page/account is selected during re-authentication (for Facebook).
  2. Verify API Keys/Credentials: For integrations requiring API keys (e.g., Stripe, Twilio), double-check that the keys entered in GHL are correct and active in the third-party service.
  3. Check Permissions: Ensure the connected user account (e.g., Facebook user) has the necessary administrative permissions on the integrated assets (e.g., Facebook Page, Ad Account).
  4. Review GHL Automation: For lead capture issues, check the relevant GHL workflow/trigger. Ensure it's active and correctly configured to process the incoming data.
  5. Test Transaction/Lead: Perform a test transaction (Stripe) or submit a test lead (Facebook Form) to verify data flow.
  6. GHL Status Page: Check status.gohighlevel.com for any platform-wide outages affecting integrations.

Q3: Client cannot access their GHL sub-account despite being provided credentials.

• Scenario: Client reports "invalid username/password" or inability to log in to their GHL sub-account.
• Solution:
  1. Verify Login URL: Confirm the client is attempting to log in at the correct GHL sub-account URL (e.g., app.gohighlevel.com/v2/login or a custom white-labeled domain if configured). They should not be using the agency-level login.
  2. Check User Status: In the GHL sub-account, navigate to Settings > Team Management. Verify the client's user account exists, is active, and has the correct email associated.
  3. Initiate Password Reset: As an Onboarding Specialist (with appropriate permissions), trigger a password reset for the client from Team Management. Advise the client to check their spam/junk folder for the reset email.
  4. Confirm Email Address: Double-check the email address used for the client's login against the internal records. Typos are common.
  5. Browser Cache/Cookies: Advise the client to clear their browser cache and cookies, or try logging in from an incognito/private browser window.