By Alpit Patel and the aibrevo team · October 13, 2026 · 6 min read
GoHighLevel Setup Checklist: Your First 30 Days, in Order
A GoHighLevel setup checklist works best in build order: account structure and users first, then phone and A2P, domain and email authentication, contacts and pipelines, calendars and forms, and only then workflows. Three tasks block go-live because other companies control them: A2P review, DNS and number porting. Start those in week 1.
Part of the guide: GoHighLevel setup guide
Key takeaways
- Build in dependency order: account structure and users, phone and A2P, domain and email, contacts and pipelines, calendars and forms, then workflows. A workflow built before its pipeline, calendar and sender exist has to be rebuilt.
- Three items can block go-live because outside parties control them: A2P 10DLC review, DNS changes and number porting. Start all three in week 1 and build everything else while they run.
- HighLevel's own porting guide gives about 2 to 4 weeks for fewer than 50 numbers after documents are submitted, and 6 to 8 weeks for larger or more complex ports (article modified October 6, 2026).
- Test with a real phone and a real inbox before launch: one inbound call, one outbound text, one form submission, one booking, one email to Gmail. Five tests catch most day-one failures.
- Owner and hours in the table below are our planning estimates, not HighLevel figures. Your data volume and number of calendars move them most.
What should be on a GoHighLevel setup checklist, and in what order?
A GoHighLevel setup checklist should follow dependencies: things other tasks need come first. The order that holds up is account structure and users, phone and A2P registration, domain and email authentication, contacts and pipelines, calendars and forms, custom values, and then workflows. This page is the 30-day checklist version of our GoHighLevel setup guide, which explains each layer.
The reason for the order is waiting time. Building a pipeline takes an afternoon. A2P review, DNS propagation and a number port are measured in days or weeks and are controlled by carriers, registrars and HighLevel support. So the checklist starts the slow items on day 1 and fills the waiting time with the work you control.
Build order and where the waits sit
- Account and users. Business info, time zone, roles. No outside wait.
- Phone and A2P. Buy or port numbers, file A2P. Waits: A2P review, port (weeks).
- Domain and email. Connect domain, authenticate the sending domain. Wait: DNS.
- Contacts and pipelines. Fields, tags, stages, CSV import. No outside wait.
- Calendars and forms. Booking, reminders, lead capture. Depends on users and pipeline.
- Custom values and snapshot. Reusable business data, then optional template.
- Workflows. Last, because they point at everything above.
Which tasks block go-live, and how long do they take?
Three tasks block go-live: A2P 10DLC registration, DNS changes for your domains, and number porting. Everything else in the checklist you can finish yourself.
| Blocker | Who controls it | What it blocks | Time to plan for |
|---|---|---|---|
| A2P 10DLC brand and campaign review | Carriers and HighLevel’s registration flow | Business texting from US local numbers | Roughly one to two weeks without rejections, per our A2P approval timing page |
| Number port | Your current carrier and HighLevel | Using your existing business number | About 2 to 4 weeks for under 50 numbers after documents are submitted; 6 to 8 weeks for larger ports (HighLevel, checked 2026-10-13) |
| DNS records | You or your registrar or IT contact | Custom domain for funnels and websites, authenticated email | Minutes to a day of work; wait depends on your registrar. Verify in the account |
| Toll-free verification (if you use toll-free) | Carriers via HighLevel | Texting from a toll-free number to US or Canadian recipients | Separate from buying the number; voice calls are not affected |
Two cautions from HighLevel’s porting guide. Keep the old carrier active until the port is fully completed, because canceling early can interrupt or fail the transfer. And a port that is waiting on an unsigned letter of authorization stalls, so confirm the signer can open the email. Our porting FAQ covers that process, and the phone number setup guide covers buying and routing.
What do I do in the first 30 days, task by task?
The table lists each task with an owner and a time estimate. Owners and hours are our planning estimates for a single-business account, not HighLevel figures. Menu paths come from HighLevel’s help articles, checked 2026-10-13, and menus change, so confirm against your screen.
| Week | Task | Owner | Est. time | Done when |
|---|---|---|---|---|
| 1 | Confirm account type (agency or single sub-account) and fill business info | Account owner | 1 hr | Business name, address, time zone saved |
| 1 | Invite users and set roles (roles guide) | Account owner | 1 hr | Each person logs in and sees only what they should |
| 1 | Gather A2P documents (legal name, EIN, address, website, opt-in page) | Business owner | 1 to 2 hrs | Names match IRS records exactly |
| 1 | Buy numbers, or submit the port request | Admin | 1 hr | Number visible in Settings > Phone System, or Request SID saved |
| 1 | Submit A2P brand and campaign | Admin | 1 to 2 hrs | Status shows submitted or in review |
| 1 | Connect the domain (domain FAQ) and add email authentication records (SPF, DKIM, DMARC) | Admin plus whoever owns DNS | 1 to 2 hrs | Domain verifies; sending domain records pass |
| 2 | Create custom fields, tags and the pipeline (pipeline and contact setup) | Admin | 2 to 3 hrs | Stages match your real sales process |
| 2 | Clean and import contacts from CSV | Admin | 2 to 4 hrs | Import finishes in Bulk Actions with no unexplained errors |
| 2 | Enter core custom values (custom values guide) | Admin | 1 hr | Business phone, address and booking link set |
| 3 | Build calendars and reminders (calendar setup) | Admin | 2 to 3 hrs | A test booking appears on the right user’s calendar |
| 3 | Build forms and surveys that create contacts and opportunities | Admin | 2 hrs | A test submission lands in the right stage |
| 3 | Configure call routing, voicemail and recording notice | Admin | 1 hr | A test call rings the right people and reaches voicemail |
| 4 | Build the first workflows (automation pillar) | Admin | 4 to 8 hrs | Each workflow tested with a test contact |
| 4 | Review consent, opt-out and recording rules (compliance pillar) | Business owner | 1 to 2 hrs | Opt-in language and disclosures reviewed |
| 4 | Run the five-test go-live check | Admin | 1 hr | All five pass |
| 4 | Save a snapshot if you will repeat this build (snapshots) | Admin | 30 min | Snapshot created from the tested account |
What are the five tests to run before going live?
Run these five from outside your own login, using a personal phone and a personal inbox:
- Inbound call: call the business number from a mobile phone. Confirm who rings, where it goes on no answer, and that the call shows in Conversations.
- Outbound text: send a text to your mobile phone. If A2P is still pending, expect this to fail or be filtered; that is the signal to hold the launch.
- Form submission: submit your own form. Confirm a contact is created, tagged, and (if intended) an opportunity appears in the first stage.
- Booking: book through the public calendar link. Confirm the confirmation email, the reminder timing and the entry on the right user’s calendar.
- Email to Gmail: send a workflow email to a Gmail address. Check that it lands in the inbox, not spam, and that the sender name and address are what you set.
If a text or email fails, the troubleshooting hub routes by symptom.
What should I not do in the first 30 days?
Do not build the full automation library in week 1, do not import contacts before the fields and pipeline exist, and do not cancel your old phone provider before the port finishes. Also avoid copying a purchased snapshot into a live account without replacing every custom value, since the values arrive as the source account had them.
If the timeline matters more than the learning, the “have it done” route is a scoped build. See our GoHighLevel setup agency page and the setup cost estimator to see where your scope lands before you contact anyone.
Sources
- HighLevel Support: How to Submit and Track Port-In Number Requests (modified October 6, 2026): menu path, timelines, “keep the numbers active” caveat. Checked on 2026-10-13.
- HighLevel Support: How to Purchase a Phone Number (modified September 18, 2026): A2P 10DLC and Toll-Free Verification after purchase. Checked on 2026-10-13.
- HighLevel Support: How to buy a toll free number (modified August 31, 2026): verification is separate; voice not affected. Checked on 2026-10-13.
- HighLevel Support: User Access (modified October 6, 2026): users menu paths. Checked on 2026-10-13.
- HighLevel Support: Importing Contacts and Opportunities via CSV (modified September 16, 2026): import location and Bulk Actions monitoring. Checked on 2026-10-13.