GoHighLevel Setup Tutorial: The Complete Step-by-Step Guide (2026)

GoHighLevel is an all-in-one CRM and automation platform built for service businesses. Instead of running separate tools for your CRM, email marketing, SMS, booking calendar, and landing pages — it handles all of them from a single dashboard.

This guide covers everything you need to get it running: account setup, pipeline configuration, your first automation, booking, lead capture, and a complete follow-up sequence. By the end, your core operations system will be live.

GoHighLevel (GHL) is a CRM and marketing automation platform originally built for marketing agencies but increasingly used by service business owners who manage their own client operations.

In a single platform, it replaces:

• CRM: contact management, pipelines, deal tracking
• Email marketing: campaigns, sequences, broadcasts
• SMS automation: two-way texting, automated responses
• Booking calendar: appointment scheduling, reminders
• Landing pages and funnels: drag-and-drop builder
• Reputation management: automated review requests
• Workflow automation: trigger-based sequences for any event

The result is fewer tools to manage, fewer integration points to break, and one monthly fee instead of five.

After starting your trial, you'll land in the GHL dashboard. The first things to configure:

Business profile

Go to Settings → Business Profile. Add your business name, address, phone number, and timezone. This populates default fields across emails, SMS, and confirmation messages.

Connect your email sending domain

Go to Settings → Email Services. Add your domain and verify SPF, DKIM, and DMARC records in your DNS. This is critical — without it, your automated emails land in spam.

Add your phone number

Go to Settings → Phone Numbers. Purchase a local number ($1.15/mo) or use your existing number. This enables two-way SMS automation.

Your pipeline is the visual board that tracks every lead and client from first contact to closed deal. Go to CRM → Pipelines and create a new pipeline.

Recommended stages for a service business

1. New Lead
2. Contacted
3. Proposal Sent
4. Follow-Up
5. Closed — Won
6. Closed — Lost

Keep it simple. Six stages cover most service business sales cycles. You can add complexity later — starting lean means you'll actually use it.

Lead source tagging

Under Settings → Custom Fields, add a "Lead Source" field. Tag every contact by where they came from (social, referral, organic). This data becomes valuable once you have 50+ contacts.

Build this one first. It produces the highest return of any automation in GHL.

The 5-minute lead response

When a new lead submits a form, an automated SMS and email fire within five minutes. A lead who gets a response within five minutes is nine times more likely to convert than one who waits thirty.

To build it: Go to Automation → Workflows → New Workflow.

1. Trigger: Contact Created (or "Form Submitted" if using a specific form)
2. Action: Send SMS — "Hi [First Name], thanks for reaching out. I'll be in touch shortly — is there a good time to connect this week?"
3. Action: Send Email — confirmation email with your calendar link or next step
4. Action: Add to Pipeline — moves contact to "New Lead" stage automatically

Test it by submitting your own form. Confirm the SMS and email arrive within five minutes. Then leave it running — it fires on every new lead from this point forward.

Go to Calendars → Calendar Settings → New Calendar. GHL's calendar is a full booking system with automated confirmations, reminders, and no-show recovery.

Configure the basics

• Set your availability windows
• Set appointment duration and buffer time
• Connect your Google Calendar for two-way sync
• Enable automated confirmation email and SMS reminder (24hr + 1hr before)

Add the no-show recovery workflow

Go back to Workflows and create a second automation triggered by Appointment No-Show:

1. Wait: 60 minutes after missed appointment
2. Send SMS: "Looks like we missed each other — still want to connect? Here's a link to rebook: [calendar link]"
3. Wait: 1 day
4. Send Email: follow-up with the same rebook option

Go to Sites → Forms. Build a simple contact or enquiry form with name, email, phone, and one qualifying question. Embed it on your website using the embed code GHL generates, or use a GHL landing page.

Connect the form to your 5-minute lead response workflow from Step 4. Every form submission now triggers the automation automatically.

Most leads don't convert on the first contact. A follow-up sequence handles the persistence automatically. Go to Automation → Workflows → New Workflow.

Basic 5-touch follow-up sequence

1. Day 0: Initial response (your 5-minute automation)
2. Day 2: SMS check-in — "Any questions I can answer before we connect?"
3. Day 4: Email — value content or a relevant result
4. Day 7: SMS — "Still happy to connect when the timing works."
5. Day 14: Final email — leave the door open, move to long-term list

Each message should be short and low-pressure. The goal is to stay visible at the moment timing shifts in the lead's favour — not to push for a close.

Go to Reputation → Settings and connect your Google Business profile. Then create a workflow triggered when a project or deal stage changes to "Closed — Won":

1. Wait: 24 hours after project completion
2. Send SMS: "Hi [First Name], really enjoyed working with you on this. If you have 60 seconds, a Google review would mean a lot: [review link]"
3. Wait: 3 days
4. Send Email: same request, slightly different framing

Most clients are willing to leave a review. Most never get asked at the right moment. This automation fixes that permanently.

Once the core four are running — lead response, no-show recovery, follow-up sequence, review requests — your operational layer is largely automated. From here:

• Client onboarding sequence: triggered when a deal closes, delivers welcome email, intake form, and onboarding timeline automatically
• Re-engagement sequence: for leads that went cold 30–60 days ago
• Proposal follow-up: triggers when a proposal is sent, follows up automatically if no response after 48 hours

Each of these is covered in detail in the Automation OS Blueprint — the free guide that maps out all four systems and what to build in what order.