GoHighLevel setup checklist: what a proper build includes

By Veronica Loyal · Updated 13 September 2026 · 9 min read

GoHighLevel can hold your website, forms, calendars, pipeline and follow-up in one place. That is its strength, and also why so many accounts end up half-finished. There is a lot to set up, and it is easy to stop once the first form works.

I have built GoHighLevel funnels for businesses as different as a farm stay, a construction company, a strength and conditioning gym and a financial coach. The details change, but the same problems come up. The account was set up by someone who never documented it, so nobody dares change anything. Forms capture a name and an email, which is not enough to route or prioritise a lead. And automations fire once and stop, so anyone who does not reply on day one is never contacted again.

Here is what a proper build covers, section by section.

1. Account and domain basics

These are not exciting, but skipping them causes problems in every section that follows.

• Business profile complete: business name, address, phone and, most importantly, the correct time zone. Every reminder and workflow depends on it.
• Accounts in the business's name: the sub-account, billing, domain and connected services should belong to you, not to whoever built it.
• Individual user logins: everyone gets their own user with the right permissions. Nobody shares a login.
• Domain connected: your own domain or a subdomain for funnels, websites and booking pages, so links look like your business.
• Email sending domain set up: a dedicated sending domain authenticated with the DNS records your provider asks for, usually SPF, DKIM and DMARC, so your emails reach inboxes.
• Phone number configured: call forwarding, voicemail and missed-call handling set up the way you actually answer the phone.
• Integrations connected: your Google or Outlook calendar, Google Business Profile and any social accounts you plan to use.
• Custom values in place: business name, phone number and booking link stored once, so every template updates when one of them changes.

2. Pipelines and stages

The pipeline is the map of how a lead becomes a customer. The default template rarely matches how you actually sell.

• One pipeline per genuinely different sales process. Not one per lead source. Where a lead came from belongs in a field or tag.
• Stages that describe what has happened. For example: New lead, Contacted, Quote sent, Booked, Won, Lost. Anyone should be able to read a stage name and know where the deal stands.
• Clear rules for moving between stages, including which moves are automatic and which a person makes.
• An owner on every opportunity, so it is always clear who is responsible.
• Opportunity values filled in, so pipeline reports mean something.
• Lost reasons recorded, so you can see why deals are not closing.

3. Forms that capture the right fields

A form is not just a way to collect contact details. It is how you decide what to do next with a lead.

• Ask for what you need to quote or route. For a mobile notary, that might be document type, county and urgency. For a builder, project type, location and timeline. A name and an email alone tell you almost nothing.
• Map answers to custom fields, not into a notes box, so they can trigger workflows and appear in reports.
• Track the source with hidden fields for campaign details, so you know which marketing is producing leads.
• Add a clear consent checkbox for marketing texts and emails. Plain language, and never pre-ticked.
• Tell people what happens next on the thank-you page or message.
• Send an instant notification to the person who will actually follow up, not a shared inbox nobody checks.
• Test on a phone. Submit the form yourself on mobile and confirm the contact, fields and notification all arrive.

4. Calendars and reminders

• The right calendar type: a personal calendar for one person, or a round-robin style calendar for a team.
• Realistic availability: working days, buffers between appointments, minimum notice and how far ahead people can book.
• Two-way sync with your Google or Outlook calendar so nobody gets double-booked.
• Useful booking questions, kept short, so you arrive prepared.
• Instant confirmation by email and, with consent, by text.
• Reminders before the appointment, with reschedule and cancel links so people move a booking rather than simply not turning up.
• Appointment statuses kept up to date, such as showed or no-show, because the follow-up below depends on them.

5. Automated follow-up sequences

This is where most of the value sits. A good sequence keeps going past the first message and stops the moment the person replies or books.

New lead

• Instant reply confirming you received the enquiry and what happens next
• Internal notification and an opportunity created in the right stage
• A short series of follow-ups over the following days, each one useful rather than a repeat
• Stops automatically on reply or booking

No-show

• Triggered when an appointment is marked as a no-show
• A friendly message with a link to rebook, with no guilt-tripping
• One more nudge later, then a task for a person to call

Gone quiet

• Triggered when a lead sits in a stage with no activity for a set number of days
• A check-in, then something genuinely helpful, then a polite message asking whether to close the file
• Moves the lead to a nurture list or to Lost, so the pipeline stays honest

Review request

• Triggered when a job is marked complete or won
• A short message with a direct link to your review page, plus one reminder
• Sent to every customer in the same way. Filtering out unhappy customers before they reach your review page goes against Google's review policies.

6. Email and SMS compliance basics

This is general guidance, not legal advice. Rules differ between the US, Canada and the UK, and some industries have extra requirements, so check the details with your provider or adviser.

• Get consent before sending marketing messages, and keep a record of when and how it was given.
• Make opting out easy. Marketing emails need a working unsubscribe link and your business details. Text replies such as STOP should mark the contact so no workflow messages them again.
• Register for A2P 10DLC in the US. If you send business texts to US numbers from a standard local number, carriers generally require your brand and messaging campaign to be registered first. Unregistered messages can be filtered or blocked, and approval can take time, so start early.
• Match your registration to reality. The sample messages you submit should reflect what you will actually send, and your website should have a privacy policy and terms that cover text messaging.
• Respect sensible sending times, so nobody gets a text from your business in the middle of the night.
• Check industry rules. Mortgage, financial, health and legal businesses often need compliance approval before messages go out.

7. Reporting

If nobody can see what the system is doing, nobody trusts it. A simple dashboard is enough.

• New leads by source
• Pipeline value by stage
• Appointments booked, attended and missed
• Deals won and lost, with reasons
• Progress against a weekly goal the team actually cares about

Then build the habit: look at it once a week, at the same time, and ask what needs to change.

8. Documentation and handover

A build is not finished until someone other than the builder can run it.

• Written SOPs: what each pipeline stage means, what each workflow does and when it fires, and how to make everyday changes.
• Clear naming: workflows, forms, tags and fields named so their purpose is obvious.
• An inventory: every integration, domain and connected account, and who owns each one.
• A walkthrough: a recorded session showing the team how to use and adjust the system.
• Ownership confirmed: the account and documentation stay with you if you stop working with the person who built it.

Common mistakes

• Importing a snapshot and never tailoring it to the business
• Forms that only collect a name and an email
• Automations with no stop conditions, so people keep getting messages after they reply
• Texting contacts without consent, or before registration is approved
• Testing only on a desktop computer
• So many pipelines, tags and workflows that nobody knows which ones matter
• Notifications going to an inbox nobody watches
• No documentation, so the account becomes too risky to touch

How I can help

If your account is half-built, or you are starting from scratch, this is the work I do. A GoHighLevel build with me starts at $900 as a fixed-price project and is typically delivered in one to three weeks: pipeline stages mapped to how you sell, intake forms wired to real notifications, automated follow-up, a reporting dashboard against a weekly goal, and written SOPs so your team can run it. If you need the website too, a website and CRM together starts at $2,200. Everything stays in your name, and nothing depends on me still being around.