Sub-accounts are the entire reason GoHighLevel works as an agency platform in the first place. Each client gets a fully separate account, contacts, pipelines, funnels, and automations, while you manage everything from a single agency dashboard. Set them up carelessly and you end up with a mess of inconsistent client accounts. Set them up with a repeatable process and new client onboarding drops from hours to minutes.
This guide walks through building that repeatable process, the same setup I recommend to high-ticket dropshipping operators who also run agency-style client services and need their onboarding to actually scale rather than eating a full day every time a new client signs, and the same underlying architecture applies whether you are onboarding your very first client or your fiftieth.
Manage Every Client From One Agency Dashboard
Unlimited sub-accounts, white-label branding, and snapshot templates that turn hours of setup into minutes.
Step 1: Get on the Right Plan
The Unlimited plan at $297 per month is the practical starting point for any agency, since it includes unlimited sub-accounts, the agency dashboard, API access, and snapshot templates. If your model involves reselling GoHighLevel under your own brand and billing clients directly, the SaaS Pro plan at $497 per month adds full white-label capability and automated client rebilling through Stripe.
Choosing the right plan upfront matters, since downgrading later to save money often means losing access to features your existing client accounts already depend on. For the complete breakdown of every tier, see my GoHighLevel pricing guide.
Step 2: Configure Your Agency Master Account
In Settings, set your business name, logo, and time zone before creating any client sub-accounts. Your time zone should match your primary operating location, since follow-up sequences and scheduled automations need to fire during your actual business hours, not at an inconvenient hour because the account defaulted to the wrong zone.
Connect your agency’s email sending domain at this stage too, since this domain is used for outbound emails across every client account you create, and getting deliverability configured correctly once at the agency level saves you from fixing it separately for each client later.
Step 3: Create the Sub-Account
Creating a new sub-account takes under two minutes. Click “Add a Sub Account” from the agency dashboard, enter the client’s business name, location, niche, and contact details, then save. The account is live immediately and ready for the configuration steps that follow.
Double-check every detail entered here, especially the client’s niche and location, since these fields often feed directly into snapshot templates and automation logic you will apply in the following step.
Step 4: Apply a Snapshot Template
According to GHL VA Service’s step-by-step sub-account setup guide for agencies, attaching a snapshot at the point of sub-account creation reduces client onboarding from a roughly 10-hour manual build down to a 10-minute configuration task, since the snapshot pre-loads funnels, automations, email campaigns, and pipeline stages automatically.
Navigate to Settings, then Snapshots, inside the new sub-account and choose the template that matches the client’s industry or use case. Everything transfers in at once: workflows, pipelines, funnel templates, email sequences, tags, and dashboards, giving you a fully functional starting point rather than a blank account.
Step 5: Customize Domain Settings
In the sub-account’s Settings, then Domains, add the client’s own custom domain for their funnels and website. Without this step, pages publish on a generic GoHighLevel subdomain, which looks unprofessional and undermines the white-label positioning many agencies rely on to justify their pricing.
Domain setup typically takes 5 to 15 minutes for DNS propagation to fully complete, so build that lag time into your onboarding timeline rather than expecting the domain to work instantly the moment you save the setting.
Step 6: Set Up Phone Numbers
Go to Settings, then Phone Numbers, inside the sub-account and purchase a local phone number matching the client’s area code. This enables SMS, calling, and the missed-call text-back feature, all genuinely valuable capabilities for a local or service-based client business specifically.
If the client is in the US and plans to send marketing SMS, enable A2P 10DLC registration at this stage, since this registration is required for compliant bulk messaging and skipping it can result in messages being blocked or flagged as spam later.
Step 7: Customize Pipeline Stages
Go to Opportunities, then Pipelines, and review the pipeline stages against the client’s actual sales or service process. If you applied a snapshot in Step 4, the pipeline stages are already pre-configured as a starting template, so this step is mostly about renaming stages to match the client’s specific terminology rather than building the pipeline from scratch.
Getting pipeline terminology right matters more than it might seem, since a client who sees unfamiliar stage names in their own CRM immediately feels like the system was not actually built for their business.
Step 8: Set Client Permissions Correctly
Default every new client user to the Account User role, never Account Admin, and only upgrade permissions after a genuine training session and explicit sign-off from your team. According to Net Partners’ 2026 guide to HighLevel sub-account setup, disable four specific toggles for client users by default: Delete Contacts, Delete Workflows, Settings access, and Phone Number management, since these are the permissions most likely to cause accidental damage if a client user clicks the wrong thing without understanding the consequences.
Review these permission settings periodically as your relationship with each client evolves, since a client team member who initially only needed basic access may legitimately need broader permissions once they take on more responsibility.
Why Sub-Account Architecture Matters More Than It Looks Like It Should
It is easy to treat sub-accounts as a purely technical setting and miss why the architecture itself is the actual product decision. A single shared account with tags or custom fields separating clients might look similar on the surface, but it creates real risk: one client’s automation misfiring into another client’s contact list, one client’s team member seeing another client’s pipeline data, or a bulk edit accidentally touching every client at once instead of just one.
Sub-accounts eliminate that entire category of risk by design, since each one is a fully isolated environment with its own contacts, workflows, and permissions. According to Sawan Kumar’s agency setup guide for GoHighLevel sub-accounts, this isolation is precisely why agencies managing more than a handful of clients standardize on sub-account architecture rather than trying to segment a single shared account with tags, since tag-based segmentation eventually breaks down as client count grows past a small number.
There is also a billing clarity benefit that often gets overlooked. Because each sub-account tracks its own usage (SMS sent, emails delivered, phone minutes used), you get a clean, itemized cost breakdown per client rather than one blended number you have to manually estimate and divide when it comes time to bill clients for usage-based costs on top of your management fee.
Onboarding Timeline: What a Realistic First Week Looks Like
Setting client expectations correctly from day one starts with having a realistic, honest internal timeline yourself rather than an idealized one. On day one, complete the technical setup covered in the eight steps above: sub-account creation, snapshot application, domain connection, phone number purchase, and permission configuration. This portion, if you already have a solid master template, genuinely does take under an hour for most straightforward client niches.
Day two through four is typically spent on content customization: swapping in the client’s actual logo, brand colors, service descriptions, and any industry-specific automation triggers that a generic snapshot could not have anticipated. By day five, most agencies run a short client-facing walkthrough call to hand off login credentials, explain the Account User permission boundaries, and set expectations for what the client can and cannot change themselves.
Building this same five-day cadence into every new client engagement, rather than improvising the timeline each time, is what actually makes an agency feel operationally mature to a new client during the period when they are forming their first impression of your service.
Building a Reusable Master Template
The single biggest efficiency gain in sub-account setup comes from building one master “Template” sub-account containing your core pipelines, calendars, and three to five core automations, then cloning it via Snapshot for every new client rather than rebuilding from scratch each time. This approach cuts new-client setup from several hours down to roughly 25 minutes according to agency workflow benchmarks.
Update your master template periodically as you discover better automation patterns or pipeline structures through actual client work, so every new client benefits from lessons learned on previous accounts rather than starting from an outdated template.
Common Mistakes to Avoid
Skipping the snapshot step and building each client account manually is the most common inefficiency, since it directly undermines the entire reason sub-account architecture exists in the first place. Granting Account Admin access by default is another frequent mistake, since it removes the safety guardrails that prevent an untrained client user from accidentally deleting workflows or contacts.
Forgetting to set up the client’s custom domain before sharing funnel links with them is a small but visible mistake, since a client clicking their own “live” funnel and seeing a generic GoHighLevel subdomain immediately raises questions about the professionalism of your setup.
Troubleshooting Common Sub-Account Setup Issues
Snapshot application occasionally fails silently on larger templates, leaving a sub-account with some automations loaded and others missing. If a client’s account looks incomplete after applying a snapshot, re-apply it rather than trying to manually patch in the missing pieces, since a partial manual fix often creates inconsistencies that are harder to track down later than simply starting the snapshot application over.
Custom domain connections sometimes fail because of an existing DNS record conflicting with the one GoHighLevel requires. According to GoHighLevel’s own domain troubleshooting documentation, the most common cause is a client’s existing website host still holding the same subdomain the funnel is trying to use, which requires removing or adjusting the conflicting record with the client’s domain registrar before the new one can take effect.
A2P 10DLC registration delays are another frequent source of frustration, since carrier approval for SMS registration can occasionally take several business days rather than the same-day turnaround agencies sometimes expect. Set this expectation with clients upfront during onboarding so a normal registration delay does not get mistaken for something being broken.
Frequently Asked Questions
How many sub-accounts can I create on GoHighLevel?
The Unlimited plan and SaaS Pro plan both include unlimited sub-accounts, which is one of the core reasons GoHighLevel is positioned specifically for agencies rather than single businesses.
What is a snapshot in GoHighLevel?
A snapshot is a saved template containing funnels, automations, pipelines, and other configuration that can be applied to a new sub-account instantly, dramatically speeding up client onboarding.
Should new client users get Admin access?
No, not by default. Start every new client user at the Account User role and only upgrade to Admin after training and explicit agreement on what that access allows them to do.
How long does domain setup take for a new sub-account?
Typically 5 to 15 minutes for DNS propagation once the domain is correctly added, though this can occasionally take longer depending on the client’s domain registrar.
Do I need a phone number for every client sub-account?
Only if the client needs SMS, calling, or missed-call text-back functionality specifically. Not every client’s service model requires this, so evaluate it case by case rather than defaulting to it automatically.
Scaling Beyond Your First Ten Client Sub-Accounts
The setup process described above works cleanly for your first several clients, but agencies that grow past ten or fifteen active sub-accounts run into a different problem: keeping track of which clients are using which snapshot version, which automations have been custom-modified per client, and which permission settings have quietly drifted from your standard defaults over time.
At this scale, it is worth maintaining a simple internal spreadsheet or project tracker listing every active sub-account alongside its snapshot version, custom domain status, phone number, and the date permissions were last reviewed. This is a low-tech solution, but it solves a real problem: without it, agencies commonly lose track of which clients still have outdated automation logic running in the background, quietly underperforming compared to clients onboarded more recently with an improved template.
Periodically auditing existing sub-accounts against your current master template, rather than only ever building new templates and never revisiting old client accounts, is what keeps service quality consistent as the client roster grows rather than becoming a patchwork of different setup eras.
Some agencies handle this by scheduling a recurring quarterly review where every active sub-account gets a quick pass: confirming the phone number is still active, the domain still resolves correctly, and permissions still match the current standard rather than an older, looser configuration that predates a security incident or lesson learned from a different client. This small recurring investment of time is far cheaper than discovering a stale, over-permissioned account months after the fact, usually right at the moment something actually goes wrong.
The Bottom Line
Setting up GoHighLevel sub-accounts correctly the first time, complete with a snapshot template, proper domain configuration, and conservative default permissions, turns client onboarding into a repeatable, fast process rather than a multi-hour manual build every time. Invest the time upfront to build a solid master template, and every client after that benefits from the efficiency. For the complete rundown of GoHighLevel’s features and pricing tiers, see my GoHighLevel review.
A well-run agency also depends on solid fundamentals beyond the software itself. That means having the right high-ticket niche and dependable suppliers in place if your agency work sits alongside an ecommerce business.
It also means having your business structure squared away so you are ready to scale once your onboarding process is actually running smoothly.
Find the Right High-Ticket Niche Before You Scale Your Agency
Grab the free list of vetted high-ticket niches to start with the right product category.
Our Services
If you want the full system built around you instead of piecing together tools one at a time, check out my Done-For-You Store Service, Turnkey Store Package, Private Coaching, Supplier Recruiting, Google Shopping Ads Management, and Ecommerce SEO Service.
Free Resources
Get started with the Free Beginner’s Guide, the Free Mini Course, the Free Niches List, and the Free Supplier Directory.
Every platform decision should support the bigger picture of what high-ticket dropshipping actually is and how it fits your business. Learn more about the model and the rest of my resources at Ecommerce Paradise.
Related Articles
GoHighLevel Review 2026: All-in-One CRM and Marketing Platform for Agencies
GoHighLevel Pricing Explained 2026
How to Build a Sales Funnel in GoHighLevel (Step-by-Step)
Best CRM Software for Marketing Agencies in 2026
Best All-in-One Marketing Platforms for Agencies in 2026
Trevor Fenner is an ecommerce entrepreneur and the founder of Ecommerce Paradise, a platform focused on helping entrepreneurs build and scale profitable high-ticket ecommerce and dropshipping businesses. With over a decade of hands-on experience, Trevor specializes in high-ticket dropshipping strategy, niche and product selection, supplier recruiting and onboarding, Google & Bing Shopping ads, ecommerce SEO, and systems-driven automation and scaling. Through Ecommerce Paradise, he provides free education via in-depth guides like How to Start High-Ticket Dropshipping, advanced training through the High-Ticket Dropshipping Masterclass, and fully done-for-you turnkey ecommerce services for entrepreneurs who want a faster, more hands-off path to growth. Trevor is known for emphasizing sustainable, real-world ecommerce models over hype-driven tactics, helping store owners build scalable, sellable, and location-independent brands.
