GoHighLevel Client Onboarding Checklist: Signed Proposal to Live Sub-Account in 7 Days (2026)

The fastest way to lose a new client is to make them wait. A client who signs a proposal is at peak enthusiasm on day one — and that enthusiasm decays every day their sub-account sits half-built. In our agency builds, the pattern is consistent: clients onboarded within seven days renew at roughly twice the rate of clients who took a month to go live. The reason is simple behaviour, not magic. A client who sees a working calendar, a tested SMS number and a live pipeline in their first week believes you can deliver. A client still chasing DNS records in week four starts wondering what they're paying for.

Slow onboarding also wrecks cash flow. Most GoHighLevel agencies bill from go-live or tie the first invoice to delivery milestones, so every idle day between signed proposal and live sub-account is unbilled work-in-progress. Worse, drawn-out onboarding consumes the hours you should be spending on the next sale. This checklist is the exact seven-day process we run for every new sub-account — what happens each day, who owns each task, and where Australian agencies in particular get caught out (hint: SMS compliance). Follow it as written and you can take a client from signature to first campaign in a single week.

Day 1: Kick-off call, intake form and access collection

Day 1 is about information, not building. Run a 45-minute kick-off call with one agenda: confirm scope, confirm the seven-day timeline, and walk the client through your intake form on the call rather than emailing it and hoping. The intake form should capture business details (legal name, ABN, address, opening hours), brand assets (logo files, colours, fonts), offer details (services, pricing, guarantees), and the answers that will populate your custom values later — booking link wording, review link, primary contact details.

The second half of Day 1 is access collection, and it is the single biggest cause of onboarding delays. Before you end the call, collect or schedule: domain registrar login (or a delegate invitation), Google Business Profile access, Facebook Business Manager partner access, existing CRM export if you're migrating contacts, and email platform access if a list is moving across. If the client "needs to find the login", book a 15-minute follow-up for tomorrow morning — never leave it open-ended. I tag every missing credential as a task with a due date inside our own sub-account so nothing drifts.

Day 2: Sub-account creation, snapshot deployment and custom values

Create the sub-account from the agency dashboard with the correct business name, timezone (Australia/Sydney, Brisbane or Perth — get this right or every appointment reminder fires at the wrong hour) and address. If you run SaaS Mode, attach the correct plan and payment details now so rebilling for phone and email usage is configured from day one rather than retrofitted later.

Then deploy your niche snapshot. A good snapshot loads your workflows, pipelines, custom fields, tags, email templates, funnels and calendar shells in minutes instead of days — it's the difference between a 7-day onboarding and a 30-day one. If you haven't systematised this yet, our guide to deploying and updating GoHighLevel snapshots across sub-accounts covers how to structure snapshots so they push cleanly into new locations.

Immediately after deployment, populate custom values from the Day 1 intake form: business name, phone, booking link, review link, owner first name, brand colours if your funnels reference them. Because every workflow and template in the snapshot references custom values rather than hard-coded text, this one step personalises the entire account. Finish Day 2 by skimming each workflow to confirm triggers carried across correctly — snapshot imports occasionally disable triggers, and a disabled trigger discovered on go-live day is an avoidable embarrassment.

Day 3: Domain, DNS and email deliverability

Day 3 is infrastructure. Connect the client's domain (or a subdomain like go.clientdomain.com.au) for funnels and websites, and set up the dedicated sending domain in Mailgun — typically a subdomain such as mail.clientdomain.com.au. Add the SPF, DKIM and DMARC records at the registrar, plus the CNAME records for the funnel domain and tracking. This is why you collected registrar access on Day 1: DNS propagation takes time, so records added on Day 3 are verified well before go-live.

Start the warm-up early

A brand-new sending domain has no reputation. Don't blast the client's full list on Day 7 — start warming on Day 3 with small internal sends, then ramp volume gradually over the first two to three weeks. Verify the domain in Mailgun, send test emails to Gmail, Outlook and an Australian ISP address, and check headers for SPF/DKIM passes. We run every new sending domain through our GoHighLevel email deliverability checklist before any client-facing email leaves the account — it catches misaligned DMARC policies and missing return-path records that quietly destroy inbox placement.

Day 4: Phone number, ACMA/A2P compliance and SMS testing

Purchase the client's phone number through LeadConnector (or your own Twilio integration if you run a custom setup). For Australian clients, choose a local number with the right prefix for credibility, and configure call forwarding to the client's existing line with whisper and call recording if your offer includes call tracking.

Compliance is not optional

This is where Australian agencies need to slow down. If you also serve US clients, A2P 10DLC registration is mandatory before business SMS will deliver reliably. For Australian traffic, ACMA rules under the Spam Act apply: you need consent, sender identification and a working opt-out on every commercial SMS. Build "Reply STOP to opt out" into your SMS templates at the snapshot level so it's never forgotten, and confirm the client's intake process actually captures SMS consent. Carriers filter aggressively now — an unregistered or non-compliant number means silent message failures and a client asking why leads aren't replying.

Finish Day 4 with live testing: send a test SMS to two or three real Australian mobiles, reply to confirm two-way conversation threading works in the Conversations tab, test the missed-call text-back workflow, and place a test call to confirm forwarding and recording. If you've enabled Conversation AI for after-hours responses, test its replies against five or six realistic enquiries and tighten the prompt before a real lead ever talks to it.

Day 5: Calendars, pipelines and workflow customisation

Configure calendars properly: availability windows in the client's timezone, buffer times, minimum scheduling notice, and Google or Outlook calendar sync for every team member who takes bookings. Test a booking end-to-end and confirm the confirmation and reminder workflows fire on the correct triggers.

Then shape the pipelines. Your snapshot ships a default pipeline; Day 5 is when you rename stages to match how this client actually talks about their sales process — a physio clinic and a solar installer do not share stage names. Map which workflow actions move opportunities between stages, and adjust the lead nurture workflows with the client's own offer language. In our agency builds we cap snapshot customisation at roughly 20% of workflow content; if you're rewriting more than that for every client, your snapshot is wrong for the niche, not the client.

Day 6: Client training, recorded walkthrough and team permissions

Run a 60-minute training call covering only what the client touches daily: the mobile app, the Conversations tab, moving opportunities through the pipeline, and checking the calendar. Resist the urge to demo everything — overwhelmed clients disengage, and disengaged clients churn. Record the session and supplement it with a short Loom-style walkthrough of their specific account, not a generic GHL tutorial, so new staff can self-train later.

Set team permissions deliberately. Client users get user-level roles scoped to their own location, with agency settings, snapshot access and billing hidden. Restrict who can edit workflows — a well-meaning client "tidying up" a workflow is one of the most common causes of broken automations three weeks after go-live. Add each staff member with their own login rather than a shared one, so call assignments, calendar sync and the activity log actually mean something.

Day 7: Go-live checks, handover doc and first campaign

Day 7 starts with a final pass: every workflow published, every trigger enabled, forms submitting and creating contacts with the right tags, domain SSL active, sending domain verified, phone number tested, calendar booking live. Then submit one test lead through the public-facing funnel and watch it travel the entire journey — form fill, tag applied, workflow triggered, SMS and email received, opportunity created in the pipeline, booking confirmed. If the test lead's journey is clean, you're live.

Deliver a one-page handover document: login URL, support process, links to the training recordings, and a plain-English summary of what's automated. Then launch something small the same day — a database reactivation campaign to the client's existing list, or a Google review request workflow. A first-week win, even a modest one, anchors the client's perception of value before the first invoice lands. If you're an Australian business reading this from the client side and weighing up who to hire for a build like this, our guide to choosing a GoHighLevel expert in Australia sets out exactly what a competent implementation partner should be doing in week one.

Automate the onboarding itself with a GHL pipeline

The final upgrade is to run this checklist inside your own agency sub-account. Build an "Onboarding" pipeline with a stage per day — Kick-off, Account Setup, Domain & Email, Phone & SMS, Customisation, Training, Go-Live — and create an opportunity the moment a proposal is signed. Workflows attached to each stage do the chasing for you: the signed-proposal trigger sends the intake form and kick-off booking link automatically, a stalled-stage trigger nudges the client when access credentials are 24 hours overdue, and stage transitions assign internal tasks to the right team member. The same tags, custom fields and triggers you sell to clients will run your own delivery — and the pipeline view tells you at a glance which onboarding is stuck and exactly which day it's stuck on.

The 7-day onboarding checklist

Common mistakes to avoid

• Building before access is collected. Starting the sub-account while waiting on registrar logins guarantees a stall on Day 3. Access collection is the Day 1 job for a reason.
• Skipping the dedicated sending domain. Sending client email from a shared domain ties their deliverability to every other account's behaviour. Set up Mailgun with a dedicated subdomain on every build.
• Ignoring SMS compliance until messages fail. ACMA consent and opt-out requirements (and A2P registration for US traffic) must be sorted before go-live, not after the client complains that leads aren't getting texts.
• Over-customising the snapshot. Rebuilding workflows from scratch for each client erases the entire point of a snapshot. Customise language and stages; keep the architecture standard.
• Giving clients admin-level permissions. Unrestricted workflow access is how automations get quietly broken. Scope roles tightly and individually.
• Going live without an end-to-end test lead. Checking workflows individually is not the same as watching one lead travel the full journey. Always run the test lead before handover.

If you want a proven onboarding system that gets clients live in days instead of months, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

Can you really onboard a GoHighLevel client in seven days?

Yes, provided two things are true: you have a tested snapshot for the niche, and the client supplies access credentials on Day 1. The seven-day timeline fails almost exclusively because of missing logins or DNS access, which is why access collection happens on the kick-off call rather than by email afterwards.

What is ACMA compliance for SMS in Australia?

The Australian Communications and Media Authority enforces the Spam Act, which requires consent before sending commercial SMS, clear sender identification, and a functional opt-out such as "Reply STOP". Build the opt-out into your GoHighLevel SMS templates at snapshot level and make sure your intake forms capture SMS consent, or carriers may filter your messages.

Do I need a dedicated sending domain for every client?

Yes. A dedicated Mailgun sending subdomain (for example, mail.clientdomain.com.au) isolates each client's sender reputation, so one client's poor list hygiene can't damage another's inbox placement. Set it up on Day 3 and begin warming it immediately with low-volume sends.

What should be in a GoHighLevel onboarding snapshot?

A complete snapshot includes workflows with triggers, pipelines, custom fields, tags, calendars, email and SMS templates, funnels and forms — all referencing custom values rather than hard-coded business details. That way, populating custom values on Day 2 personalises the entire account in one step.

How much should an agency charge for GoHighLevel onboarding?

Australian agencies typically charge between $1,500 and $5,000 AUD as a one-off setup fee depending on scope, alongside a monthly retainer. A documented seven-day process justifies the higher end, because the client sees a working system — tested phone, live calendar, first campaign — within the first week.