What is the GoHighLevel setup checklist for a new business?
The GoHighLevel setup checklist is the ordered list of ten objects a new account needs before it can answer, follow up and book a lead: sub-account, phone number and A2P registration, domains, pipeline, calendars, workflows, forms, AI agents, integrations and reporting.
Why does the order of a GoHighLevel setup matter?
The order matters because most objects depend on an earlier one. A workflow cannot send a text until the number is registered, a calendar cannot book until team calendars are synced, and a pipeline stage change cannot trigger anything until the pipeline exists. A setup done out of order produces automations that fire into nothing.
The ten steps below are the order Skill Up Experts follows for every GoHighLevel build, from a single-location US clinic to an agency sub-account. Most accounts are live in two to four weeks; the phone registration step is usually the longest wait.
Each step names the object, what it needs and where the detailed guide is.
What are the ten setup steps and what does each one need?
The table is the checklist. Work top to bottom; do not start a row until the rows above it are done.
| Step | Object | What it needs before it is done |
|---|---|---|
| 1 | Sub-account and users | Business name, time zone, currency, one login per team member with the right role |
| 2 | Phone number and A2P 10DLC | A local number, business registration details, sample messages and a consent statement for carrier approval |
| 3 | Domains and email | A sending domain with DKIM and DMARC, a funnel or booking subdomain, a branded short link |
| 4 | Pipeline | Named stages that match how the business sells, from new lead to won or lost |
| 5 | Calendars | Team calendars synced, calendar type chosen, buffers and minimum notice set |
| 6 | Forms and surveys | A short lead form with a consent checkbox, mapped to contact fields |
| 7 | Workflows | Speed-to-lead, missed-call text-back, reminders, no-show, review request, reactivation |
| 8 | AI agents | Voice AI on the number, Conversation AI on web chat and WhatsApp, with handoff rules |
| 9 | Integrations | Meta lead forms, Google Ads call tracking, website embeds, WhatsApp, payment processor |
| 10 | Reporting | Weekly report on calls answered, response time, appointments booked and cost per booked appointment |
What has to be true before any automation can run?
Before any automation can run, the account needs a registered phone number, an authenticated sending domain and the right users. The phone number step includes A2P 10DLC registration for US texting, explained in our A2P 10DLC guide; without it carriers filter or block the messages.
The sending domain needs DKIM and DMARC records so confirmation emails land in the inbox rather than spam. The users step is where roles are set, so a front-desk login cannot delete workflows.
These three steps are boring and they are where most self-built accounts fail, because the owner starts building workflows first and discovers weeks later that texts were never delivered.
How should the pipeline, calendars and forms be built?
The pipeline should copy the stages the business already uses in its head: new lead, contacted, qualified, appointment booked, showed, won, lost. Fewer stages are better than more, because every stage change can trigger a workflow and too many stages produce too many messages. Our pipeline automation guide covers the triggers.
Calendars come next, built as described in the calendars guide: team calendars synced first, then the type, the buffers and the booking form. The lead form asks for name, phone, one qualifying question and consent; every extra field lowers completions.
With these three in place a lead can enter, move and book, which is the skeleton the automations hang on.
Which workflows and AI agents come first?
The first workflows are the ones that pay back fastest: speed-to-lead on new form submissions, missed-call text-back on the tracked number, and the confirmation-reminder-no-show sequence on the calendar. Review requests and database reactivation follow once the first three have run for two weeks.
AI agents are configured after the workflows exist, because the agents book into the calendar and hand off into the workflows. Voice AI answers the registered number; Conversation AI answers web chat and WhatsApp. Both are metered, with speech-to-speech voice at $0.10 to $0.20 per minute, and an agency can only rebill that usage on the $497 plan.
Handoff rules are written before the agents go live: which questions transfer to a human, what happens outside hours, and how a caller reaches a person by saying so.
What connects the account to ads, the website and reporting?
Each source is tagged so the report can show where booked appointments came from.
Reporting is the last object and the one that keeps the system honest. A weekly report shows calls answered, median response time, appointments booked and cost per booked appointment by source, as covered in our cost per booked appointment guide.
When step ten is running, the setup is finished and the work becomes tuning: message wording, timing and the handoff rules, adjusted from the transcripts.
What do we test before an account goes live?
Every item is tested from the lead’s side, on a phone, before launch.
- A test text from the registered number arrives on a US phone
- A confirmation email lands in a Gmail and an Outlook inbox, not spam
- A form submission creates a contact and starts the speed-to-lead workflow
- A missed call to the tracked number produces a text within 30 seconds
- A calendar booking appears in the team member’s synced calendar
- The AI receptionist answers, books a slot and transfers when asked for a person
- A Meta test lead lands in the pipeline with its source tag
- The weekly report shows the test bookings under the right source
Common questions about setting up GoHighLevel
How long does a full GoHighLevel setup take?
Two to four weeks for a single-location business. The longest wait is usually A2P 10DLC approval in the United States, which the carriers control. Building the pipeline, calendars and first workflows takes days once the number is approved.
Which GoHighLevel plan does a new business need?
A business using one sub-account is usually set up under an agency’s $297 or $497 plan rather than buying its own. The $497 plan is required if the agency needs to rebill AI usage to the business. We advise on the plan during the strategy call.
Can I set GoHighLevel up myself with this checklist?
Yes, the checklist is complete. The steps most owners get wrong alone are A2P registration, email authentication and workflow stop conditions, which are the ones that fail silently. If you build it yourself, test every item in the launch check from a phone.
Do I need to change my business phone number?
No. The existing number is ported or forwarded into GoHighLevel so it becomes the tracked number, and callers see no change. Porting takes a few days; forwarding works the same day.
Want the checklist done and tested for you?
We build all ten objects in order and test every one from a phone before launch.
Book a Free Strategy Call