The GoHighLevel client onboarding checklist

There are two onboarding checklists in this business and agencies routinely run only one of them. The first is technical: does the account work. The second is human: does the client believe the account works, know how to use it, and feel like they bought well.

The technical sweep is covered separately in the fourteen-point snapshot import checklist — timezone, custom values, sender authentication, carrier registration, calendar ownership and orphaned triggers. This piece is the other one: the fortnight around it, run under your brand, where retention is actually decided.

Why the first fortnight decides the year

A client forms their view of your competence long before the system produces anything. They form it from response speed, from whether you asked for the same thing twice, from whether the walkthrough was recorded or improvised. Nothing that happens in month six overwrites it.

The other reason is momentum. A client who sees something real happen quickly stays engaged. A client who waits three weeks for a login has already started explaining the purchase to themselves as a mistake.

Days 1–2: intake, and only intake

1. Send one intake form, immediately on signature, that asks for everything at once: brand assets, domain access, business details, service list, pricing, opening hours, the calendar to connect, the phone number to port or provision, review profile links and who the notifications should reach.
2. Book the kickoff call at the same time, in the same message. Do not wait for the form to come back; a booked date is what makes the form come back.
3. Send the welcome sequence — what happens, when, and what you need from them. Under your brand, from your domain, with your name on it.

Days 3–4: the kickoff call

Forty-five minutes, structured, recorded. Three jobs: confirm what happens to a lead from first contact to booked appointment in their business, agree what they will consider a good first result, and set the date they will see it.

The middle one is the important one. If you and the client do not agree in week one what success looks like, you will both invent a definition later and they will not match.

Days 5–8: the build week

This is where the technical checklist runs. From the client’s point of view nothing is happening, which is a risk — so make something happen anyway.

• Send a short written update at the end of day six. Two paragraphs, no jargon, and one thing they need to do.
• Get carrier registration submitted on day one of the build, not at the end. It is the longest lead time in the whole launch and it is out of your hands.
• Give them a single small task — approving the service list, or confirming opening hours. Participation early correlates with participation later.

Days 9–10: the walkthrough

Record it, always, and send it. Most clients watch it twice: once with you and once alone, and the second viewing is where the questions come from.

1. Show them the four screens they will actually use, and nothing else. A full platform tour is a way of losing somebody in twenty minutes.
2. Show them what their customer sees, not what the workflow does. Play the confirmation text. Show the reminder. Show the review request.
3. Show them where a lead lands and what they are expected to do with it, and be blunt about the part that still needs a human.
4. Leave them one written page — logins, the four screens, who to contact, and what happens next.

Days 11–12: the live test

Go through the system as a customer of the client’s business, on a real phone, with the client watching. Call the number after hours. Submit the form. Book the appointment. Wait for the confirmation. Deliberately miss the appointment and let the recovery call happen.

This single exercise does more for confidence than any report. It also finds the thing you missed, in front of the only audience that can forgive it at that stage.

Days 13–14: go live, and say so

• Turn everything on in the order a lead flows through it, not in the order it was built.
• Watch the first day of real traffic actively rather than waiting for a complaint.
• Send a short note confirming what is live, what is deliberately off, and what you are watching.
• Book the thirty-day review before the launch note goes out.

What the client’s customers should experience by day fourteen

A stranger calls the business at nine at night and has a real conversation rather than reaching voicemail. They get booked into a slot that genuinely exists. A confirmation arrives before they have put the phone down, then a reminder the day before and another an hour ahead. If they do not turn up, a call follows within the hour to rebook them — a recovery process built to a seventy per cent target. After the job, a review request goes out, aiming at a steady five to ten reviews a month.

Every one of those touches carries your client’s name, not yours and not ours. That is the whole point of onboarding under your own brand, and it is why the sender identity checks in the technical sweep are a customer-experience issue rather than a cosmetic one.

The thirty-day review

Not a report. A conversation with three questions: what has happened, what have you stopped doing manually, and what is annoying you. The third question is the one that saves the account, and clients almost never volunteer the answer unprompted.

If running this fortnight properly is the thing your week cannot absorb, it is available as a service — done-for-you client onboarding runs the whole sequence under your brand, with the walkthrough recorded in your name. Either way, run it. The build is the easy half.

When the client goes quiet

It happens on most engagements and it is the single largest cause of a launch slipping. The intake form does not come back, the brand assets never arrive, and the build sits waiting on somebody who has a business to run.

Silence is almost never disinterest. It is usually that you asked for eleven things and the client does not have the eleventh, so they have not sent any of them.

• Ask what is blocking it, specifically, rather than following up on the whole request. "Which of these do you not have to hand?" gets a reply where "just chasing this" does not.
• Offer to proceed without the missing item. Almost everything can be launched with a placeholder and replaced later; say which, and say what it costs to defer.
• Do the parts you can do and show them. Progress visible on their side restarts the conversation better than a reminder does.
• Put a date on it. "We will build with what we have on Thursday unless we hear otherwise" is not a threat; it is the permission most clients are waiting for.

Build this into the process rather than treating it as an exception, because it is not an exception. A client who has just paid you is at their most enthusiastic and their least available at exactly the same moment.

The short version

One intake form, a kickoff that agrees what good looks like, a build week with visible progress, a recorded walkthrough of four screens, a live test on a real phone, and a review booked before launch. Fourteen days. The account was ready on day eight; the client was not.