How long does it take to set up GoHighLevel?

For a single business with a pipeline, calendar, website forms and a handful of workflows, allow one to two weeks of part-time work, plus however long the UK phone bundle takes to approve. Agency builds with templates for several clients take longer. Most of the time goes on deciding how your process should work, not on clicking settings.

Should I use a snapshot to set up my account?

Only if you have reviewed what is in it. A snapshot can save hours, but it also imports workflows, custom values, pages and settings you did not choose. Load it into a test sub-account first, check every workflow is in draft, change anything US-specific, then use it. For a single business, a clean build is often quicker to understand and maintain.

Do I need a dedicated email domain in GoHighLevel?

For anything beyond a trickle of emails, yes. A dedicated sending subdomain, authenticated with the DNS records GoHighLevel provides, improves deliverability and keeps your reputation separate from other senders. HighLevel's documentation also sets much higher daily sending limits for dedicated domains than for the shared default.

GoHighLevel 6 min read Sajid Aslam5 October 2026

GoHighLevel Setup Checklist

Every setting a new GoHighLevel account needs, in the order that avoids rework and delays, including the UK steps most tutorials leave out.

Checklist for setting up a new GoHighLevel sub-account step by step

Short answer

Set up GoHighLevel in this order: business profile and users, UK phone number and regulatory bundle, dedicated email sending domain, custom fields and tags, one pipeline, calendars, forms on your website, core workflows, review requests, then test everything with your own phone and email before going live. Starting the phone registration first avoids the most common delay.

This GoHighLevel setup checklist is the order I work through for a new sub-account. The order matters: some steps take days to approve, and doing them last is why launches slip. Each section lists what to set, why, and what usually goes wrong.

It assumes a single business in one sub-account. Agency-level settings come at the end.

Before you start

Write down your process. How enquiries arrive, who answers them, what happens next, when a job is won, when it is complete. GoHighLevel should mirror this, not the other way round.
List what GoHighLevel replaces and when those subscriptions end, so you do not cancel anything before the replacement works.
Decide who has access and what each person should see.

Phase 1: account foundations

Business profile: legal name, address, phone, website, time zone set to Europe/London, currency set to GBP.
Users added with the right roles. Restrict permissions so staff only see what they need.
Mobile app installed and logged in for everyone who answers enquiries.
Notification settings for each user, so the right person is alerted and nobody gets everything.
Business hours set, because workflows and calendars depend on them.

What goes wrong: leaving the time zone on a US default. Every scheduled message is then hours out.

Phase 2: UK phone number and regulatory bundle

Do this on day one.

Buy a UK number in the phone system settings.
Create the regulatory bundle with the business's legal details and supporting documents.
Submit and wait for approval. HighLevel's UK SMS compliance article explains that UK long codes cannot send SMS or make calls without an approved bundle.
Set call forwarding to the phones that should ring, and a voicemail greeting.
Decide on porting: port your existing number in, or forward it to the new one.

What goes wrong: starting the bundle in week three and discovering approval takes days.

Phase 3: email

Dedicated sending domain set up, usually a subdomain such as mail.yourbusiness.co.uk, with the DNS records GoHighLevel provides.
SPF, DKIM and DMARC checked on your main domain as well.
Default from name and address set to something a customer recognises.
Email signature for each user.

HighLevel's LC Email documentation explains sending limits: new sub-accounts ramp up over the first week, and dedicated domains have much higher daily limits than the shared default.

Phase 4: data structure

Custom fields for what you actually need to record: service type, postcode, source, marketing consent and consent date.
Tags with a naming convention, such as source-google or status-customer. Keep the list short.
Smart lists for the views you use daily.
Import existing contacts with consent recorded where you have it. Migrating to GoHighLevel covers the import order.

What goes wrong: dozens of tags created ad hoc, which workflows then depend on and nobody can untangle.

A useful rule: if a piece of information has a value (a postcode, a date, a service type), it belongs in a custom field. If it is a yes-or-no state that triggers or filters something (customer, supplier, complaint open), a tag is fine. Mixing the two is how accounts end up with tags like service-boiler-repair-2025 that nobody dares delete.

Phase 5: pipeline

One pipeline that matches your process. Five to seven stages.
Stage names that describe a fact (quote sent) rather than a hope (hot lead).
Lost reasons set up, so you learn why work is lost.

Phase 6: calendars

Calendar per service or per person, depending on how you book.
Sync with Google or Outlook calendars, so existing commitments block slots.
Buffers, minimum notice and booking window set to what you can genuinely honour.
Confirmation and reminders handled in one place, either the calendar or a workflow, not both.

Phase 7: capture

Forms with fields mapped to contact fields and an unticked marketing consent checkbox.
Forms and calendar embedded on your website, or GoHighLevel funnels built for campaigns. GoHighLevel funnels and websites covers which to use.
Chat widget on the website if someone will actually answer it.
Social and messaging channels connected to the conversations inbox.
Privacy notice updated to mention the CRM and US hosting.

Phase 8: workflows

Build these first, in this order:

New enquiry: instant reply and owner alert
Missed-call text-back
Appointment confirmation and reminders
Quote follow-up
Review request after the job

Each one is explained in GoHighLevel workflow examples. Name every workflow clearly, filter every trigger, and add a stop on response.

Phase 9: reputation

Google Business Profile connected.
Review link tested.
Review request workflow sent to every customer, with no rating filter in front of the link. GoHighLevel reputation management explains why.

Phase 10: testing before go-live

Test	How
Form submission	Submit each form with your own details
Missed call	Call the number and do not answer
Booking	Book, reschedule and cancel an appointment
SMS reply	Reply to an automated text and check the workflow stops
Email deliverability	Send to Gmail and Outlook addresses and check spam folders
Pipeline movement	Move a test opportunity through every stage
Notifications	Confirm the right person is alerted for each event

Delete or tag test contacts afterwards so they do not skew reports.

Setup mistakes that cost the most time later

Mistake	Symptom	Prevention
Time zone left on a US default	Reminders arrive at odd hours	Set Europe/London in phase 1
Phone bundle started late	Launch waits on approval	Submit it on day one
No dedicated sending domain	Emails land in spam	Authenticate a subdomain in phase 3
Ad hoc tags	Workflows depend on tags nobody understands	Agree a naming convention first
Calendar notifications and workflow both on	Customers get two confirmations	Choose one source of messages
Contacts imported with workflows live	Every contact gets a welcome text	Pause creation triggers during import
Snapshot imported blind	Unknown workflows start sending	Review in a test sub-account

Each of these is quick to avoid at setup and slow to untangle once customers have been messaged.

Phase 11: handover

One-page document listing each workflow, what triggers it and what it sends.
Short walkthrough for staff on the inbox, pipeline and calendar.
Owner named for the account, responsible for changes.
Review date a month out to check what is working.

Phase 12: the first-month review

A setup is not finished on go-live day. Book a review four weeks in and check:

Unanswered conversations. Filter the inbox for messages with no reply. Each one is either a routing problem or a staffing one.
Stuck opportunities. Anything in the same stage for more than a fortnight. Either the stage is not being updated or the follow-up is not working.
Workflow errors. Open the execution logs and look for failed actions, usually missing phone numbers or emails.
Wallet spend. Compare it with what you expected. A spike usually means a workflow sending more than intended.
Staff feedback. Ask the people using it daily what annoys them. Small irritations become workarounds, and workarounds bypass the system.
Customer replies. Read a sample of replies to automated messages. Confused replies point to wording that needs changing.

Fix what you find before adding anything new. The temptation after a month is to build the next feature; the better move is usually to make the first set reliable.

Agency-level extras

If you are setting up an agency account rather than a single business:

Custom app domain and branding
Rebilling configured for phone and email
VAT number added to billing
A tested snapshot for new clients
Client data processing agreement in place

GoHighLevel white-label and SaaS mode covers these in more depth.

The GoHighLevel guide explains how all of this fits together. If you would rather hand the whole checklist over, my GoHighLevel setup service works through it in your account and documents what was built.

Related services

GoHighLevel Automation