Onboarding a client is not finished when the login works. The client must receive the right inquiries, only authorized people should see their data, and the agency must know what happens when the relationship ends. This is a proposed operating checklist, not a record of a completed client deployment.
Published September 16, 2026 · Documentation-based guidance and illustrative workflows; not hands-on testing or measured customer results.
Before creating a client account
Write down the legal client name, agreed service, business timezone, authorized administrator, primary lead recipient and who owns the original customer data. Confirm which channels the client has permission to contact people through. Record the current CRM, calendar and funnel domains and who controls those accounts.
Decide whether the agency is delivering raw inquiries, qualified leads, booked appointments or closed business. Those are different handoffs. The agreement should say which party handles disputed leads, opt-outs and data export.
Create a pipeline that describes real work
HighLevel documents contact records, opportunities, pipelines, stages and manual or automated opportunity creation in its official pipeline guide. For a hypothetical consultation business, begin with a small stage set: New inquiry → Assigned → Contacted → Appointment booked → Attended or closed. Make lost and opted-out statuses explicit instead of silently deleting records.
| Field | Purpose | Typical owner |
|---|---|---|
| Source / campaign | Investigate which inquiry path worked | Agency tracking owner |
| Assigned representative | Make follow-up accountable | Client operations lead |
| Consent / opt-out status | Prevent inappropriate messages | Client compliance owner |
| Appointment status | Stop “book now” reminders after booking | Calendar or CRM owner |
| Resolution and reason | Support rejection reconciliation | Client representative |
A permission test before launch
- Create an authorized test lead using a form specifically approved by the client.
- Confirm that an intended team member can find its opportunity and history.
- Confirm that a different client or unrelated user cannot view the record.
- Test whether the designated owner gets the right notification, without exposing unnecessary personal data.
- Run an opt-out test to ensure the record is suppressed from inappropriate further messages.
- Have the client confirm the export and retention requirements in writing.
Record pass or fail and the person responsible for remediation. Avoid putting real personal data in demo accounts.
Keep follow-up under human control
HighLevel’s workflow documentation describes event triggers and actions. A useful pattern is form submission → contact/opportunity update → assignment → permitted confirmation → human response. Add exit conditions for a reply, booking, opt-out or incorrect contact. A single missed-condition test can reveal more than a polished funnel demo.
Do not automatically text or email every imported contact. Review actual permission records, sender identification and applicable communication rules with the client.
Client sign-off and offboarding plan
Obtain acceptance for the intake form, pipeline stages, who receives messages, appointment calendar, reported metrics and escalation path. Define who owns domains and telephone numbers and what the client can export. Before termination, decide how data will be transferred or retained, who turns off integrations, and when delegated access is revoked.
Our CRM migration and rollback plan handles the additional risk of moving an established business rather than starting from a blank account.
Check HighLevel’s current plans
If your work requires a shared pipeline and permission-based follow-up, compare its live terms and scope with the workflow above. This is an affiliate link, and the merchant controls its offer.
Sources & verification
Provider documents verify stated capabilities and prices. The checklists and hypothetical scenarios are editorial decision aids, not evidence of live product testing.