GoHighLevel Tutorial: How to Use GoHighLevel (Beginner)
A step-by-step GoHighLevel tutorial for week one — sub-account, phone number, A2P registration, calendar, first funnel, and your first working automation.
The steps
-
Create your first sub-account
From the agency dashboard, create a sub-account (a 'location'). Every client — or every business you run — gets exactly one. Never run two businesses in one sub-account; the data model assumes one business per location.
-
Buy a phone number and register for A2P 10DLC
Under Settings → Phone Numbers, buy a number (~$1.15/month). Then complete A2P 10DLC brand and campaign registration. In the US you cannot legally send SMS until this is approved, and approval takes 1–7 days — so start it on day one, not the day before launch.
-
Connect your calendar and email sending domain
Connect Google/Outlook calendar for two-way sync, then authenticate a sending domain (SPF, DKIM, DMARC records) so your email lands in inboxes rather than spam.
-
Build one funnel with one form
Use a template. Do not design from scratch on day one. Publish a single landing page with a single form that captures name, email, and phone.
-
Wire your first automation
Create a workflow triggered by that form submission: send an SMS within 60 seconds, send a follow-up email at 10 minutes, create an opportunity in your pipeline, and notify yourself. This one automation is the core loop the whole platform exists to run.
-
Test the loop end to end as a real lead
Submit your own form from your phone using a real number. Confirm the SMS arrives, the email lands outside spam, the opportunity card appears, and the thread shows in the Conversations inbox. Fix anything that fails before you send real traffic.
-
Save it as a snapshot
Once it works, save the sub-account as a snapshot. Every future client starts as a clone of this, not a blank page. This is the single biggest time-saver in the platform.
Most people who abandon GoHighLevel during the trial quit for the same reason: they open the dashboard, see forty menu items, and start clicking around instead of building one complete loop. This guide is the opposite approach. Ignore roughly 80% of the platform for now and get a single lead-to-appointment pipeline running.
By the end of the week you will have one thing: a lead comes in, gets a text in under a minute, books an appointment, lands in your pipeline, and you get notified. That loop is what the platform is genuinely excellent at. Everything else is a variation on it.
Before you start
Have these ready: your business (or client’s) legal entity name and EIN — you’ll need them for SMS registration — a logo, a domain you control DNS for, and the calendar you actually book on.
The one structural thing to understand first
GoHighLevel has an agency view and sub-accounts (the UI also calls them “locations”). The agency view is the control panel: billing, snapshots, global settings, and the list of sub-accounts. It is not where you work.
Each sub-account is an isolated workspace with its own contacts, calendars, funnels, phone numbers and automations. One business = one sub-account, even if you only ever have one. People who start building in the agency view end up rebuilding everything, which is a miserable way to spend a Saturday.
Day 1: the plumbing nobody warns you about
The steps above are ordered deliberately. A2P 10DLC registration is the long pole, and it is the number-one reason a trial gets wasted. US carriers require every business sending application-to-person SMS to register a brand and a campaign. GoHighLevel surfaces the form, but the carriers do the approving, and that takes days.
Kick it off in the first hour. Everything else you can do while you wait.
The failure mode here is nasty because it is quiet: without approved registration your texts don’t throw a big red error, they just fail or get filtered into the void. If you are debugging “why is my SMS not sending”, check Settings → Trust Center before you touch anything else. The full process is covered in Set up two-way SMS and A2P registration.
Day 2–3: calendar and domain
Two-way calendar sync means an appointment booked through GoHighLevel blocks your real calendar, and a busy slot on your real calendar disappears from your booking page. Without it, you will double-book, and you will look unprofessional in front of a client in the first week.
Authenticating your sending domain (SPF/DKIM/DMARC) is equally unglamorous and equally load-bearing. Skip it and your automated follow-ups go to spam, which makes the whole platform look broken when the problem is DNS.
Then book a test appointment through your own booking link and confirm it lands on your personal calendar. It takes thirty seconds and catches an embarrassing class of bug.
Day 4–5: the one loop that matters
Build this exact workflow:
- Form submitted →
- SMS within 60 seconds (“Hi {{contact.first_name}}, thanks for reaching out — want to grab a time?” with your booking link) →
- Wait 10 minutes → send email with the same link →
- Create an opportunity in the pipeline at stage “New lead” →
- Notify you.
That is it. That five-step workflow is the thing GoHighLevel is genuinely excellent at, and it’s the thing that makes the money. Speed-to-lead is the highest-leverage variable in local-business marketing, and a sub-60-second automated text beats a human callback an hour later almost every time — because the lead is still on your site with their phone in their hand, and has not yet filled in your competitor’s form.
It is also worth understanding why this is easy here and painful elsewhere. The CRM, the SMS sender, the email sender, the calendar and the funnel are all one system reading one database. The same automation across HubSpot + Twilio + Calendly + Zapier is four vendors, four auth tokens, and four ways to fail silently at 11pm on a Friday. That is the entire pitch of the platform, and this is the moment you feel it.
Go deeper on branching, waits and conditions in Build your first workflow automation.
Test it like a stranger, not like the person who built it
Pull out your phone. Fill in your own form with a real number and email, exactly as a customer would.
- Did the text arrive inside a minute?
- Did the email arrive, and stay out of spam?
- Did the opportunity card appear in the pipeline?
- Did the thread show up in the Conversations inbox — the unified inbox where you will actually live day to day?
Anything that failed, fix now. A half-working automation is worse than none, because you will trust it.
Day 6: snapshot it
Once it works, snapshot the sub-account. A snapshot clones funnels, workflows, calendars, pipelines, custom fields, and templates into a fresh sub-account. Building the second client should take an hour, not a week. Agencies that skip this step end up rebuilding from scratch ten times and conclude the platform is slow — when the real problem is they never used its best feature. See how to install a snapshot.
What to ignore in week one
SaaS Mode. White-labeling. Membership sites. Voice AI. The marketplace. All genuinely useful; none of it matters until the core loop runs. Come back for them in month two.
The honest expectation to set
Two weeks. That is the realistic time before the platform stops fighting you, and almost everyone who churns does so inside that window — not because the tool is bad, but because they never got one complete loop working and so never saw the point.
The learning curve is the most common complaint about GoHighLevel and it is a fair one. We say so plainly in our honest review, alongside the other things it gets wrong, and the pricing breakdown shows what the loop actually costs to run once SMS and email usage are counted on top of the subscription.
Ready to build? Start the free trial, then work through the steps above in order.