Close & Onboard Your First Client
Discover the need, show a tested example, agree scope, and install with approval.
Why this matters
Demonstrate the customer and owner experience. Fit, trust, and informed agreement still matter. Launch depends on access, facts, tests, and approvals. An onboarding draft does not create an account, collect payment, or put a client live.
Before you begin
- Booked demo, tested number/page, written package.
- Payment process, agreement, and secure collection of facts/access.
Finish with this
For a consenting client: scope/payment terms, separate configured location, passed tests, and written launch approval.
Use the checks below to record actual work. They do not certify third-party approval or client results.
Do this and verify
Loading your checklist…
Check an item after you do it or document why that channel is outside your agreed scope. Reading a phase does not complete it.
Matching tools
Use these to prepare drafts and estimates. Complete actual configuration in the correct HighLevel location.
Missed-call opportunity estimate
Explore what would have to be true for a service to be worthwhile. These starting numbers are examples, not measured losses or promised results.
Formula: job value × missed calls/week × 52 ÷ 12 × recoverable share × completed-job rate. Apply job gross margin, then subtract the service fee and extra costs. Missed calls can include repeat callers, spam or people who would already be called back. Measure the baseline and attributable results; this is not net profit.
Client Onboarding Package Generator
Enter confirmed business details to prepare custom values, message drafts and a setup checklist. This does not connect accounts or activate a client system. Unknown fields stay in brackets.
Business name, industry, and city are required.
Instructions and examples
Rehearse the complete demonstration
| Part | Action |
|---|---|
| Discovery | Ask what happens when the team cannot respond; verify rather than announce assumed losses. |
| Customer | Use practice number/page for an FAQ and booking/callback. |
| Owner | Show contact, real appointment/request, notification, and human takeover. |
| Limits | Explain support, fallback, scope, and usage. Label estimates; no promised leads/savings. |
| Offer | Explain one recommended scope and all fees. Offer a written proposal or suitable follow-up. |
Of course. Is there a question about scope, cost, or how your team would use it? I can send a written proposal and we can choose a suitable follow-up time. There is no need to decide on this call.
That may already meet your needs. If overflow or after-hours requests are a problem, we can test a limited backup service that hands off to your team. Which requests, if any, are difficult to cover?
Create and test your own demo calendar before outreach, using hours you can attend. The client calendar is configured later with the client's actual staffing and availability. Use scheduling controls for real limits, without implying appointments or demand that do not exist.
Client setup and launch run sheet
Real business, authorized contact, location: Approved services, FAQs, quote policy: Calendar owner/timezone/hours/booking rules: Website/domain role-based access: Phone owner/carrier/routing/voicemail/fallback: Messaging use case, consent, policies, registration status: Notification and support recipients: Fees, allowances, billing start, dependencies: Test date, change window, rollback, written approver:
The client does not need a second agency subscription in the default managed model. Invite them to their location with suitable permissions. In the client-owned model, they subscribe and invite you. Use invitations rather than shared passwords. Never mix client data, numbers, or registrations.
Subject: [Business] setup plan and next steps Hi [Name], Thank you for choosing [Agency]. We agreed [scope], [setup fee], [monthly fee/start condition], and [usage terms]. Please provide [approved facts/invitations] using [secure process]. Our next review is [agreed date]. We will configure, test with you, and request written approval before changing live routing. Dependencies: [access/calendar/registration]. Proposed launch: [date or condition], subject to those checks. Questions: [support channel/hours]. [Your Name]
14 placeholders left to review and replace before using this draft.
Facts, booking, routing, notifications, consent/registration for enabled messaging, and human fallback must pass. Record owner approval. Pending SMS can stay paused while an agreed voice/chat scope launches. Do not announce 'you're live' or promise 48 hours before checks pass.
Your next action
Monitor and report actual outcomes with Phase 10.
If blocked, note this phase, account view, location, expected/actual result, and a redacted screenshot. Use your available community/support channel. Menu names can change; confirm the right view before changing a plan.
Written instructions reviewed October 8, 2026. Official links are the reference for current prices and requirements. Older recordings may show different menus or terms.