Agencies lose more clients in the first month than in any other period. Not because the work is bad — usually nothing has been delivered yet — but because the client signed feeling confident and then spent three weeks wondering whether anything was happening.
Onboarding is the most leveraged process in an agency. It is entirely within your control, it happens the same way every time, and it sets the tone for the whole relationship. This is a working SOP you can adapt.
What Good Onboarding Achieves
- Confirms the buying decision. Buyer’s remorse is real and it peaks in week one.
- Collects what you need without six rounds of chasing.
- Sets expectations about timelines and what you need from them.
- Produces a visible win early, before the big deliverable lands.
- Makes delivery repeatable so it does not depend on who is running the account.
Day 0: The Moment They Sign
Everything here fires automatically the moment the proposal is signed or the first invoice is paid.
- Welcome message within 60 seconds. SMS and email. Confirms it is real and names who is looking after them.
- Kickoff call booking link. Do not email asking for availability — send a calendar link with slots in the next three business days.
- Intake form. One form, everything you need, with clear explanations of why each item matters.
- Internal notifications. Sales notifies delivery, the account is created, the project is spun up.
- Create the sub-account and deploy your snapshot so the environment exists before the kickoff call.
The Intake Form
Ask for everything at once, and explain each item:
- Business details — legal name, address, phone, hours
- Brand assets — logo, colours, fonts
- Access — domain registrar, existing website, Google Business Profile, ad accounts, social pages
- Current tools you are replacing or connecting to
- Their services, pricing and typical customer
- Who on their side is the decision maker, and who does the day-to-day
- Anything that must not change
Everything they give you should map to a custom value, so filling in the account is a transcription job rather than a design one.
Days 1–3: Kickoff and Access
The Kickoff Call
Keep it to 45 minutes with a fixed agenda:
- Confirm what success looks like in 90 days, in their words and in numbers.
- Walk through their current lead flow — where leads come from, who responds, what happens next.
- Confirm scope and what is not included.
- Agree the timeline, including what you need from them and by when.
- Agree communication — who to contact, response times, reporting cadence.
- Book the next checkpoint before hanging up.
Record it, with permission. Whoever builds the account will want it.
Chasing Access
Access is the number one cause of onboarding delay. Automate the chase:
- Track each required item as a custom field.
- Reminder at 48 hours for anything outstanding.
- Escalate to a call task at day five.
- Be specific about what you need and why — “we need Google Business Profile manager access so review requests post correctly” beats “please send access”.
Days 3–7: Build
This is your work, but the client should still hear from you.
- Deploy the snapshot and populate custom values from the intake form.
- Start A2P 10DLC registration on day one. It has the longest lead time of anything in the build and it blocks SMS entirely. Starting it in week two is the classic scheduling mistake.
- Configure numbers, calendars and pipelines.
- Connect integrations — website forms, payment processor, whatever else.
- Set up users and permissions for their team. See our user roles guide.
- Send a mid-week progress note even though nothing is live. Silence during build is what makes clients nervous.
Deliver a Quick Win by Day 7
Find something that produces visible value inside the first week, before the main build is finished. Missed call text back is the usual candidate — it takes an hour, it starts recovering leads immediately, and it is easy to demonstrate. A review request sequence works too.
The quick win is not a gimmick. It converts a client who is hoping this works into one who has already seen it work.
Days 7–10: Test
Test properly before the client sees anything, because they will test it and they will find what you missed.
- Submit every form and confirm the contact, tag and workflow all fire.
- Send and receive a real SMS and a real email.
- Book, reschedule and cancel an appointment.
- Place a call and confirm it records and logs.
- Run a test payment end to end.
- Check every automated message for placeholder text — the merge tag that still says “Client Name” is the one that will go out to 400 people.
- Confirm deliverability basics. Our deliverability guide covers authentication.
- Test on mobile, not just desktop.
Days 10–14: Handover and Training
Training
Teach one workflow, not the whole platform. For most clients that is: how to answer a lead in the mobile app. Everything else can wait.
- 45 minutes, recorded.
- Focus on their daily actions, not on configuration.
- Walk through the mobile app on their actual phone, with notifications enabled before they leave the call.
- Give them a one-page reference, not a 40-page manual nobody reads.
Handover Pack
- What was built and what it does, in plain language
- Logins and how to reset them
- Who to contact and expected response times
- Reporting cadence and what the numbers mean
- The training recording
Day 14 Checkpoint
A short call: is it doing what we said, is anyone stuck, what is the first thing we should improve. Book the first monthly review before you finish.
Automating the SOP Itself
Run your own onboarding inside GoHighLevel. Build an internal pipeline with a stage per phase, attach tasks to each stage, and trigger the client-facing messages from stage changes. Then onboarding is not something anyone has to remember — it is something the system runs, and you can see at a glance which client is stuck where.
Common Mistakes
- Starting A2P too late. It blocks launch and it is not fast. Day one, every time.
- Going quiet during the build. The client cannot see work in progress; they can only see silence.
- Asking for access piecemeal. Five separate requests over two weeks reads as disorganised.
- Training on everything. Overwhelmed clients use nothing.
- No quick win. Thirty days before the first visible result is thirty days of doubt.
- Skipping the test pass. The client always finds the broken form.
- Different every time. If onboarding depends on who is running it, quality depends on who is available.
The Onboarding Pipeline
Run onboarding as a pipeline in your own account rather than as a document nobody opens. Stages that map to this SOP:
- Signed — welcome sent, kickoff link sent, intake form sent, sub-account created
- Awaiting information — intake and access chase running
- Kickoff booked
- Kickoff completed — notes recorded, scope confirmed
- Building — A2P submitted, snapshot deployed, configuration underway
- Quick win live
- Testing
- Training booked
- Handed over
- Day 14 checkpoint complete — moves to the account management pipeline
Attach the tasks for each phase to its stage, and set a maximum age per stage so a client stuck awaiting information for nine days surfaces automatically rather than being discovered at the monthly review.
What to Measure
Onboarding is a process, which means it can be improved — but only if you measure it.
- Days from signature to kickoff call. Target three business days.
- Days from signature to quick win live. Target seven.
- Days from signature to full handover. Target fourteen.
- Time spent awaiting client information. If this is consistently the longest stage, the intake form is asking badly rather than the client being slow.
- Churn rate in months one to three, by cohort. If it rises after you changed onboarding, change it back.
- Support tickets in month one. A spike usually means training was too broad.
Review these quarterly. Onboarding is the one process every client experiences identically, which makes it the easiest place in the agency to find a compounding improvement. Our guide to reducing client churn covers what happens after the first fortnight.
Frequently Asked Questions
How long should onboarding take?
Two weeks is a reasonable target for a standard build. Longer is fine if it is planned and communicated; the damage comes from open-ended timelines, not long ones.
What if the client does not send their information?
Automate three reminders, then escalate to a call. If it is still outstanding, say plainly that the timeline moves. Silently absorbing the delay trains clients to be unresponsive.
Should I charge an onboarding fee?
Many agencies do, and it improves both cash flow and client commitment. Our agency pricing guide covers packaging it.
How do I keep onboarding consistent across a team?
Put it in a pipeline with tasks per stage rather than in a document. Documents get ignored; tasks get closed.
What is the single most important part?
The quick win in week one. It converts hope into evidence, and evidence is what survives the first invoice.
Make It Boring
Good onboarding is unremarkable. The client gets exactly what they were told, when they were told, from someone who knew their name. That is achievable with a snapshot, a pipeline and a handful of automations — and it is the cheapest retention work an agency will ever do. Our guide to reducing client churn covers what comes after.
GHL Nexa builds onboarding systems for agencies alongside client work. Get in touch if yours is currently held together by memory.
This guide is part of our GoHighLevel for Agencies series — agency playbook covering the whole topic.
