- Published
- Byline
- GoHighLevel Partners Editorial
- Filed under
- GoHighLevel Automation
On day one they need access to systems holding other people’s customers, which makes sequence the whole problem.
New agent onboarding checklist: the first week, in the right order
Onboarding a new person into an agency that runs client accounts is a different problem from onboarding them into most jobs, because on day one they need access to systems holding other people’s customers. Move too fast and you have handed broad permissions to someone you met last week. Move too slowly and they spend a fortnight unable to do the work you hired them for, which is its own kind of expensive.
The way through is sequence. Access, context, supervised work, then independence — with each stage having a visible end so nobody is left guessing whether they have arrived.
Before day one
Almost everything that makes a first day feel organised happens before it. The accounts exist, the equipment works, the first week is written down, and someone is expected to be available. None of that is difficult; all of it is noticed.
- Accounts created and tested by signing in yourself.
- The permission level decided deliberately rather than copied from whoever seems similar.
- A named person responsible for their first week, with time actually blocked out.
- The written material they will be given, checked for accuracy — a stale SOP teaches the wrong thing more confidently than no SOP at all.
why an sop is required before you can hire is the prerequisite here. Hiring before the work is documented means the new person learns by interrupting someone, which costs two people’s time and produces a version of the process that lives only in their memory.
Access: start narrow and widen on evidence
| Stage | What they get | What triggers the next step |
|---|---|---|
| Day one | Their own account, one sub-account, read access | They can navigate without being led |
| First week | Write access to their assigned accounts | Supervised work reviewed and correct |
| Later | Additional clients, additional tools | Demonstrated need, not seniority |
| Rarely | Administrative and billing rights | A specific responsibility that requires them |
Two rules make this work. Every person gets their own login, always — a shared account destroys the audit trail permanently, and the day you need to know who changed something is the day you discover that. And permissions are granted against a named responsibility rather than a job title, which keeps the answer to “why does this person have that” a sentence rather than a shrug.
protected snapshot assets is worth understanding early if the agency reuses builds across clients, because it governs what a new person can and cannot alter in a shared asset without realising the scope of the change.
Context before tasks
A new person given a task list before they understand the business does the tasks and misses the point. Spend the first days on what the agency sells, who the clients are, what each is paying for, and what “good” looks like in a deliverable. pipeline stages and exit criteria is a fast way to convey this: reading the pipeline definitions tells them how work actually moves, and what each stage promises the client.
Then the standards that have deadlines attached. a conversation sla and the lead response playbook define response expectations that a new person cannot infer, and getting one wrong in week one is the kind of mistake that damages a client relationship rather than just a task.
Supervised work, with a real review
The first real work should be genuine, small, and checked before it reaches a client. Reviewing it properly is the part that gets skipped when everyone is busy, and skipping it does not save time — it defers the correction to a point where the habit has set and a client has seen the output.
Be specific about what was wrong and why, and update the written process whenever a correction reveals that the documentation was ambiguous rather than that the person was careless. structure, owners and exceptions in an sop is the shape that survives: owners, exceptions, and what to do when reality does not match the steps.
The mechanics people get wrong in week one
Certain things in a client CRM are easy to do and hard to undo, and they are worth calling out explicitly rather than hoping they are inferred.
- Editing a shared asset, thinking the change is local.
- Sending to a list without checking who is on it.
- Leaving what each appointment status claims unset, which quietly breaks the reporting and can fire the wrong follow-up.
- Publishing something to a client site without the review step.
- Replying from a shared inbox in a voice that does not match the account.
A short list of “things that reach a client immediately” is more useful than a long training document, because it tells a cautious person exactly where to ask first. targeted announcement banners can carry that reminder inside the platform where the work happens rather than in a document nobody reopens.
Knowing when onboarding has finished
Set a visible end. A person who does not know whether they are still being onboarded keeps asking permission for things they own, or stops asking about things they do not. Define it as a small number of demonstrable outcomes — they have run a full cycle of the core process unsupervised, handled one exception correctly, and been reviewed on both.
The same logic as activation in the first week applies: the useful measure is not time elapsed but whether the person has done the thing that predicts they will keep doing it. And the same connection to retention holds — the mechanics of retention in an agency is often about whether the person handling an account knows it well enough to notice something going wrong.
Write it down as you go
The best time to improve onboarding is while someone is being onboarded, because the gaps are visible only to a person who does not yet know the answers. Ask them at the end of the first week what was missing, and change the material then rather than promising to.
Keep a record of what was granted, when, and by whom — a log kept outside the platform is enough — because that record is what access, handover and continuity when someone leaves depends on. Offboarding is only as clean as onboarding was documented, and the day someone leaves is a bad time to start working out which systems they could reach. It is also the point where the same discipline applied to onboarding a new client pays off, since a client handover between people is a smaller version of the same problem.
Frequently Asked Questions
How much access should a new team member get on day one?
Their own account, one client sub-account, and read access. Widen it on evidence rather than on a schedule — write access once supervised work has been reviewed, additional clients once there is a demonstrated need. Permissions should attach to a named responsibility, not to a job title.
Can new staff share an existing login to get started faster?
No. A shared account destroys the audit trail permanently, and the day you need to know who changed something is the day you find out. Creating an individual account takes a minute, and it is the only version that lets you cleanly remove access later.
What should come first, training or access?
Narrow access first so they can look around, then context, then supervised work. Someone given a task list before they understand what the agency sells will complete the tasks and miss the point, and the misunderstanding surfaces later in something a client sees.
Do we need written procedures before hiring?
Yes, in practice. Without them a new person learns by interrupting someone, which costs two people’s time and produces a private version of the process that exists only in their memory. A stale document is worse than none, so check the material before handing it over.
How do we know when onboarding is finished?
Define it as demonstrable outcomes rather than elapsed time: they have run a full cycle of the core process unsupervised, handled one exception correctly, and been reviewed on both. Without a visible end, people keep asking permission for things they own.
What mistakes do new people make most often in a client CRM?
Editing a shared asset believing the change is local, sending to a list without checking who is on it, leaving appointment statuses unset, and publishing to a client site without review. A short list of actions that reach a client immediately is more useful than a long training document.
How does onboarding relate to offboarding?
Offboarding is only as clean as onboarding was documented. Keep a record of what access was granted, when and by whom, because the day someone leaves is a bad time to start working out which systems they could reach and which client accounts they touched.
We build your GoHighLevel account for you
CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.
- Setup (one-time)$850
- Ongoing (per month)$38.80
No obligation quote · reply within 1 business day
This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.