GHL 101: The Button-to-Button Manual

1. Log in at app.gohighlevel.com (agency owners). Clients use their sub-account link or the LeadConnector app. Enable 2FA immediately on all admin logins.
2. Create a sub-account: Agency View → Accounts → + Add Account → choose template or Start From Scratch → fill Business Name, Contact Info, Time Zone (wrong timezone = every scheduled send fires at the wrong hour), Currency → Save. Never build in the Agency account directly.
3. Connect your domain: Settings → Domains → Add New Domain. GHL can also register a domain natively (2025) — no need to leave the platform.
4. Set up email: Settings → Email Services → LC Email for quick start, or Mailgun for deliverability control. Verify SPF, DKIM, and DMARC before any send.
5. Set up phone: Settings → Phone Numbers → LC Phone (fastest, recommended) or Twilio if you need direct number ownership. Enable STOP keyword handling here too.
6. Build a calendar: Settings → Calendars → + New Calendar → pick type (User / Round-Robin / Unassigned — see M6) → set availability and buffer times.
7. Create a pipeline: Opportunities → Pipelines → + Create Pipeline → stages that describe events, not hopes: New Lead → Contacted → Booked → Showed → Won/Lost.
8. Build a form: Sites → Forms → + Add Form → 2 visible fields max above the fold + hidden UTM fields (M7) + consent checkbox (not pre-ticked).
9. Build the workflow: Automation → Workflows → + Create Workflow → Trigger: Form Submitted → Actions: Add Tag src:website → Send SMS (instant) → Send Email → Create Opportunity → Internal Notification. Name it properly: WF Lead Capture v1.
10. Set reentry: in workflow settings, choose Once every X days for nurture flows so a re-submitting contact doesn't get double-enrolled.
11. Test with a dummy contact: submit the form yourself → watch it execute in Workflow → History tab → confirm tag, SMS, email, opportunity, and notification all fired. Use 1–3 min delays during testing only.
12. Go live: extend delays to production values → Publish → submit one more real test → check History again. You now have a working system. Everything after this page is depth.

GoHighLevel (GHL — officially "GoHighLevel" or "HighLevel"; same platform) is an all-in-one CRM, marketing automation, and sales platform built for agencies and service businesses. It replaces 5–10 separate tools — funnels, email, SMS, calendar, pipelines, reporting — with one account.

Use Cases by Industry

Team Roles & Module Map

Assign this manual by role. Each role's priority modules:

Common Automation Wins (what to build first)

Auto-response to new leads within seconds (SMS + email), drip nurture over days, booking reminders, lost-lead reactivation, post-service review requests, auto-advancing pipeline stages, and a Voice AI agent catching missed calls 24/7. Blueprints for all of these are in the Deployment Blueprints section.

GHL has two layers: the Agency account (your master login — billing, white-label, user permissions) and Sub-accounts (one per client or brand — all CRM data, workflows, funnels, calendars). Sub-accounts are fully isolated from each other by design.

Create a Sub-Account

1. Agency View → Accounts → + Add Account
2. Choose a template or Start From Scratch
3. Fill in: Business Name, Contact Info, Time Zone, Currency
4. Click Save

Snapshots — Productize Your Builds

Snapshots export a sub-account's entire configuration and import it into a new one. This is how one good build becomes every client's starting point.

1. Agency View → Snapshots → Import Snapshot
2. Paste the shared snapshot URL
3. Assign the imported snapshot to a sub-account

Snapshot includes:                    Snapshot excludes:
  ✓ Workflows (trigger logic intact)     ✗ Contacts and CRM data (by design)
  ✓ Funnels and websites                 ✗ Active campaign enrollments
  ✓ Email / SMS templates                ✗ API keys, third-party credentials
  ✓ Custom fields and values             ✗ Reviews / reputation data
  ✓ Pipelines and calendars

Domain & Email Options

Deliverability — Do This Before Any Send

DNS Records:
  ☑ SPF record added to sending domain
  ☑ DKIM configured (GHL provides the DNS record)
  ☑ DMARC policy set (start p=none → monitor → enforce)
GHL Settings:
  ☑ Unsubscribe link element in all email templates
  ☑ Physical business address in footer (CAN-SPAM / GDPR)
  ☑ Reply-to is a real, monitored inbox
// Bounce rate above 3–5%? Stop sending. Clean the list first.
// Sender reputation damage outlasts any single campaign.

Phone: LC Phone vs Twilio

Every automation, workflow, and pipeline stage anchors to a Contact record. The contact data model is the most important structural decision in any GHL build.

The Contact Profile (Updated 2025)

Contacts → select a contact — each profile contains: General Info (name, phone, email, tags, assigned user), Opportunities (pipeline status + deal value), Activity Timeline (forms, page visits, messages, calls), Notes, Tasks, Appointments, and AI Summary 2026 — one-click summary of all conversations: Contact Profile → Activity tab → Generate AI Summary.

Custom Fields vs Custom Values vs Custom Objects

Tag Taxonomy — The Segmentation Engine

Tags are the most flexible tool in GHL and the most abused. Without a naming convention you'll have 200 uninterpretable tags within six months.

// Prefix by function. Document every tag in your SOP hub.
SOURCE: src:facebook | src:google | src:referral | src:website
STATUS: status:hot-lead | status:warm | status:cold | status:suppressed
ACTION: action:booked | action:replied | action:clicked | action:converted
SEQ:    seq:active | seq:completed | seq:paused
AUDIT:  review:needed | duplicate:flagged | archive:unqualified

Rules: tags are for logic and filtering, never decoration. Clean unused tags monthly. Smart Lists + tags = custom CRM views per team role.

CRM Contact Lifecycle

Duplicates & GDPR Deletion

GHL deduplicates by email and phone by default. A repeat submission merges to the existing record — or creates a duplicate if the phone doesn't match. Always gate Day-0 enrollment on a seq:active tag check (M9, Rule 3).

1. Stop all active workflows for the contact
2. Remove them from all active broadcasts
3. Search contact → open profile → Trash icon → confirm

An Opportunity is a deal entry in a pipeline — tracking value, stage, assigned user, and status (Open / Won / Lost). Contacts sit in the CRM; Opportunities are what actually move. One contact can hold multiple opportunities in multiple pipelines simultaneously.

Pipeline Views

Stage Triggers (pipeline-driven automation)

1. Create workflow with trigger: Opportunity Status Changed
2. Filter by pipeline and specific stage
3. Add actions: email, SMS, task, internal notification

Lead Scoring (custom-field pattern)

Custom field: Lead Score (Number)
  Clicked email   → +10
  Booked call     → +25
  No show         → −10
Routing: If/Else on Lead Score → high scores to senior reps, low to nurture

Won / Lost Tracking

1. Open the opportunity card
2. Change Status dropdown to Won or Lost
3. Add a note with the reason — required for meaningful reporting

Calendar Types (2025–2026)

The Reminder Sequence Template

Trigger: Appointment Booked
  Immediate:   Email + SMS confirmation
  24h before:  SMS reminder + reschedule link
  1h before:   SMS: "Your call is in 1 hour — here's the link: {{meeting_link}}"
  Post-appt:   Status = Showed → tag action:showed → 6h delay → review request
  No-show:     Status = No Show → 2h delay → tag status:no-show → rebooking link

Forms capture lead data and fire automations. Built inside Sites → Forms — drag-and-drop builder with conditional field logic. Embed on external sites via code snippet. Submissions live in Sites → Forms → Submissions.

The Form Standard (use on every form)

MOBILE-FIRST ORDERING:
  Above fold: 2 fields max (name + phone, or email + city)
  Below fold: qualification fields
  // Micro-forms reduce abandonment 30–50% on cold traffic
HIDDEN FIELDS (mandatory for attribution):
  utm_source / utm_medium / utm_campaign → map to contact custom fields
  // Auto-populate from URL params. Without these, paid and organic look identical.
COMPLIANCE:
  Consent checkbox — NOT pre-ticked (GDPR/TCPA)
  Privacy policy link — visible, not buried
BACKUP:
  Form Settings → notification email to your own inbox
  // Fires independently of workflows — your lead alert survives a GHL outage

Surveys & Branching Logic

1. Sites → Surveys → Create New
2. Add questions → click the logic icon on each question
3. Set: If answer is [X] → go to step [Y], or skip to end

Use surveys for appointment qualification, lead-scoring intake, onboarding flows, and post-service feedback — anywhere the next question depends on the last answer.

Funnels (single-path, conversion-focused) and Sites (multi-page, navigation-based) share the same editor. A landing page driving one action = funnel. A multi-page website = site.

Build Paths

CTA Button Actions

Buttons can: go to Next Step in Funnel, Open URL, Submit Form, or Trigger a Workflow via Trigger Link.

Test Before Launch

1. Test every page link before going live
2. Fill the form yourself → confirm contact entry in CRM
3. Check tag application and pipeline stage creation
4. Monitor: Funnels → Open Funnel → Stats tab — run A/B split tests on CTAs, headlines, layouts

GHL Funnel vs External Page

Workflows are GHL's automation engine: a trigger (what starts it), conditions (if/else logic), actions (what happens), and wait/delay steps. The interface: left column = Triggers · center canvas = Steps & Logic · top bar = Publish, Save, Test · right panel = Action settings.

The Five Architecture Rules

RULE 1: One workflow, one job.
  No 40-step mega-workflows covering 3 scenarios. Split by function:
  D0-Instant-Response · Day-3-Follow-Up · Booking-Confirmed.
  Single-job workflows are testable, debuggable, replaceable.
RULE 2: Name everything descriptively. Use folders.
  Bad:  Workflow 1 | New Automation | Copy of Copy of Test
  Good: [Booking] WF FB Lead → Booking v2 | [Nurture] WF Cold Reactivation v3
  Folders by function: Booking, Nurture, Internal, AI.
RULE 3: Always add a loop guard.
  Step 1 of any enrollment workflow: check for seq:active tag.
  Tagged → stop or alert. Prevents double-enrollment on re-submission.
RULE 4: Test with a dummy contact before going live.
  Create test contact → fire the trigger manually → watch History tab live.
RULE 5: Wait steps for time-sensitive sends.
  Wait → Send beats scheduling inside the action — it gives you a cancel window.

Reentry Settings

Troubleshooting — The History Tab Routine

1. Automation → Workflows → Open Workflow → History tab
2. Search the contact's email or phone
3. Check: Did it trigger? What was the last completed step? Were steps skipped?
4. Logs tab: Twilio bounces, invalid emails, API errors
5. Check Status column: Paused / Completed / Failed — paused on a Wait step usually means the required condition was never met (the #1 cause of stalled workflows)

Trigger Reference

Logic & Flow Controls

Action Reference

Conversations → All unifies: SMS/MMS, Email, Facebook Messenger, Instagram DM, Google Business Messages, web chat, WhatsApp native 2025, and voice calls with AI transcription.

AI Messaging Features (2025–2026)

Email Builder Modes

Compliance — Non-Negotiable

SMS (TCPA):
  ☑ "Reply STOP to opt out" in every first message — exact text
  ☑ STOP keyword handling enabled (Settings → Phone Numbers)
  ☑ Written prior consent before marketing SMS
  ☑ Check national DNC list before cold campaigns
  // TCPA violation: $500–$1,500 PER TEXT. Class actions are real.
  // GHL does not handle TCPA compliance for you. You handle it.
EMAIL (CAN-SPAM / GDPR / PECR):
  ☑ Unsubscribe Link element in all campaigns
  ☑ Physical address in footer
  ☑ Monitor: Marketing → Email → Stats → Unsubscribed
  // Missing opt-outs get your Mailgun/Twilio/LC account flagged.

WhatsApp Setup (Button to Button)

1. Enable the WhatsApp add-on — $10/sub-account/month Verified Jun 2026
2. Complete Meta Business Manager verification (business docs required; 1–3 business days)
3. Create a WhatsApp Business Account inside Meta
4. Connect: Settings → Integrations → WhatsApp
5. Verify a dedicated business number — it cannot be an existing WhatsApp number
6. Create message templates → submit for Meta approval (allow 24–72h). First contact with any new lead must use a pre-approved template; free-form replies unlock only after the contact responds
7. Test end-to-end in the Conversations tab

RCS Messaging (Android)

Payment Integrations

Connect Stripe: Settings → Integrations → Connect Stripe. PayPal and Venmo support one-click OAuth setup Dec 2025. GHL's open payments infrastructure also supports NMI, Authorize.net, Square, Adyen, Razorpay, and custom providers Verified Jun 2026. Use in funnel order forms, invoices, and subscription plans.

PAYMENT EVENT TRIGGERS:
  payment.cleared      → ✓ Move to Closed-Won, fire fulfillment, send receipt
  payment.submitted    → ⚠ NEVER use for fulfillment (funds not confirmed)
  payment.failed       → SMS alert + pause delivery + collections sequence
  subscription.created   → start retention sequence
  subscription.cancelled → cancellation flow, offboarding
  Abandoned Cart        → recovery sequence

SaaS Mode — Resell GHL as Your Own Platform

1. Upgrade to SaaS Pro ($497/mo) for white-label: custom domain, logo, login page, app name
2. Configure pricing tiers in the SaaS Configurator — import Stripe products directly 2025
3. Set rebilling markup on SMS/email/AI usage — this is the margin engine
4. Wire the signup flow: payment → webhook → auto-create sub-account → assign snapshot → email credentials (full blueprint below)

Reporting → Dashboard covers revenue tracking, pipeline movement, lead-source summaries, appointment stats, and user performance. Review weekly with your team.

UTM Discipline (the attribution backbone)

1. Add UTM parameters to all funnel and page URLs — no exceptions
2. Use hidden form fields to capture UTMs into contact custom fields (M7)
3. Read results in Reporting → Attribution Report — first-touch attribution by source, campaign, UTM, and funnel entry point

What GHL Reports Well — and the Looker Stack for the Rest

Integration Decision Table

Classic patterns: new contact → Google Sheet row + Slack alert · payment received → onboarding workflow · workflow webhook → n8n → Claude API → write result back to a custom field.

API Access

Full REST API for contacts, conversations, calendars, payments, and webhooks. Get your API key: Settings → Company Settings. Test endpoints with Postman or Insomnia. Note: the official docs live at marketplace.gohighlevel.com/docs — developers.gohighlevel.com redirects there.

// API v2 — preferred for all new integrations
GET https://services.leadconnectorhq.com/contacts/{contactId}
  Authorization: Bearer {your_api_key}
  Version: 2021-07-28
// Scope keys minimally — never a full-access key in production.
// Rate limit: ~100 requests / 10s per location. Add retry logic in n8n.

AI Employee is the single biggest GHL update of 2025–2026: a suite of AI tools bundled natively into your CRM, funnels, and workflows. The lineup has kept evolving — Ask AI and AI Studio joined the original six, and Funnel AI + Workflow AI Builder moved to free (daily fair-use limits). The coverage table below reflects the April 2026 pricing structure.

The 6 AI Tools

Pricing Model

Voice AI Setup (Button to Button)

1. Settings → AI Agents → + New Agent
2. Name the agent — e.g., Main Receptionist, After Hours Bot
3. Training method: FAQ Text Upload (preferred) or Manual Prompting
4. Feed it: website URL, PDFs, FAQs, pricing info, top 10 objections
5. Set Fallback Behavior: notify user or route to a human rep — never launch without this
6. Assign a Booking Calendar for auto-scheduling
7. Assign to a phone number → test by calling it yourself

Agent Studio

GHL's advanced AI configuration hub: multi-modal agents with intent-based call routing — the AI identifies caller intent and routes to the right department automatically. It reads GHL contact data natively (name, stage, custom fields) mid-conversation.

Social Planner — Platform Support Reality Check

Why Workflows Fail — Diagnostic Table

Pre-Launch QA Checklist

FORMS:
  ☑ Test submission → contact created with correct tags + fields
  ☑ UTM hidden fields populated
  ☑ Day 0 sequence fired within 5 minutes
  ☑ Duplicate test: resubmit → no double enrollment
SEQUENCES:
  ☑ Merge tags render (not literal {{contact.first_name}})
  ☑ Unsubscribe link in every email · STOP triggers suppression
  ☑ Reply → sequence pauses immediately
  ☑ Delays at 1–5 min for testing → extended before go-live
  ☑ Every branch has end or stop logic · all users assigned
  ☑ Copy is mobile-friendly
PIPELINE:
  ☑ Stage change fires correct workflow
  ☑ Booking moves opportunity to correct stage
  ☑ Closed-Won fires fulfillment
PAYMENTS:
  ☑ Stripe test mode: simulate success → payment.cleared fires fulfillment
  ☑ Simulate failure → failure workflow fires
WEEKLY HEALTH CHECK (15 min):
  ☑ Test form submission → sequence fires?
  ☑ Workflow error notification email — any failures?
  ☑ Campaign stats — deliverability issues?
  ☑ New contacts — tags and fields populated?

QA SOP Template

BP1 — Agency Lead Nurture System (M7 + M9 + M5)

Objective: form → tag → nurture → booking → opportunity
  Lead submits form        → tag src:website
  Day 1: Welcome SMS + intro email
  Day 2: Testimonial + case study email
  Day 3: FAQ email
  Day 5: "Let's Talk" → calendar link CTA
  Booking                  → create opportunity: Booked Call
  // Conditional split: no booking after Day 5 → re-engagement flow (BP4)

BP2 — Voice AI Missed-Call Recovery (M16)

Objective: never lose a lead to a missed call
  Inbound call → Voice AI answers within 2 rings
  AI qualifies: service needed, location, budget
  AI offers live slots from your calendar
  Booked     → CRM opportunity + confirmation SMS
  Not booked → Call Back task created for a human rep
  // Deploy this before any other AI feature — recovers 40–60% of
  // leads that would otherwise fall through. Fastest AI ROI in GHL.

BP3 — Local Business Booking + Reminder Flow (M6)

  Booking → SMS + email confirmation
  1h before → reminder SMS
  Showed   → tag → 6h delay → feedback / review request SMS
  No-show  → 2h delay → tag status:no-show → rebooking link

BP4 — Cold Lead Re-Engagement (M4 + M9)

Smart List filter: Last Activity > 14 days AND Has Booking = false
  Day 1: SMS — "Still looking for help?"
  Day 3: Email — client testimonial
  Day 5: Booking link with urgency CTA
  Response    → tag Reengaged → new nurture flow
  No response → tag Dead → exit
  // Enable reentry "once every X days" or this loop fires exactly once, ever

BP5 — SaaS Signup + Snapshot Deployment (M13 + M2)

  Client picks plan on signup funnel
  Stripe/PayPal payment.cleared → webhook → auto-create sub-account
  Workflow assigns default snapshot to new account
  Login credentials emailed automatically
  Contact moved to Client Active stage
  // Combine with Multi-Brand + rebilling = complete white-label SaaS offer

Workflow & Automation (1–10)

AI & Automation (11–15)

Tagging & Segmentation (16–20)

Calendar & Booking (21–25)

Messaging & Communications (26–31)

Reporting & Analytics (32–36)

System Organization (37–41)

Team & Scaling (42–46)

Power User Habits (47–50)

Build and Test

1. A form linked to a pipeline stage
2. A calendar with a test appointment booked
3. A complete workflow: trigger → email + SMS → task assignment → pipeline update → internal notification
4. One AI-assisted automation: Conversation AI or Voice AI with a fallback configured

Then Answer

The 20-point assessment below, plus: troubleshoot 2 broken workflow scenarios (use the M18 diagnostic table) and identify 3 automation use cases for a given industry (M1 table is your reference).

Part 1 — Multiple Choice (10 pts)

Part 2 — True or False (5 pts)

Part 3 — Short Answer (5 pts) + Bonus