GoHighLevel Sub-Accounts: How to Manage 13 Clients Without Losing Your Mind

The multi-client GHL problem

GoHighLevel's sub-account model is theoretically perfect for agencies and multi-client operators: one agency account, multiple client "sub-accounts" underneath, all sharing your Twilio and Mailgun connections.

In practice, managing 13 of them simultaneously is a completely different skill set from managing one.

I've been running 13+ sub-accounts for clients across solar, real estate, and B2B services. Here's what actually works.

---

The naming and organisation foundation

This sounds trivial. It's not. When you have 13 sub-accounts, poor naming creates a maintenance nightmare.

Sub-account naming convention

Use: [ClientName] — [Industry] — [Primary Campaign Type]

Examples:

• Sunrise Solar — Solar — Inbound Lead Gen
• Premier Properties — Real Estate — Buyer Pipeline
• TechVantage — B2B SaaS — Outreach Automation

Don't use abbreviations or codes you'll have to decode later. You're going to be looking at this list exhausted at 9pm when something breaks. Make it readable.

Internal tag taxonomy

Every contact in every sub-account should have consistent tags. The specific values vary by client, but the structure should be the same:

• source: [facebook, website, vendor, referral, cold]
• status: [new, contacted, qualified, booked, closed, lost]
• campaign: [campaign name]
• timezone: [timezone code]
• assigned: [closer username]

Consistent tags mean your reports work the same way across sub-accounts, and you can build automations that behave identically across clients without re-thinking the logic for each one.

Pipeline naming

Every sub-account should have the same core pipeline structure:

1. New Lead
2. Contacted
3. Qualified
4. Appointment Booked
5. Appointment Completed
6. Closed Won / Closed Lost

Additional stages can be added per client need (e.g., "Contract Sent" for B2B clients), but the core stages are fixed. This means your reporting metrics mean the same thing across all clients.

---

Templates: the multiplier

If you're building each sub-account from scratch, you're wasting enormous time. The answer is a master template structure.

The agency template sub-account

I maintain a "Template" sub-account in GoHighLevel that contains:

• Every workflow I've built (tagged "TEMPLATE — [workflow type]")
• Every SMS/email/voicemail sequence
• Standard pipeline configurations
• Standard calendar setups

When onboarding a new client, I clone this template sub-account and then customise. What would take 2–3 days to build from scratch takes 4–6 hours.

Cloning workflows across sub-accounts

GoHighLevel lets you export workflows as snapshots and import them into other sub-accounts. Use this constantly.

When you build something that works well in one client's sub-account — a re-engagement sequence, an appointment reminder flow, a lead routing logic — export it and add it to your template. Over 13+ clients, your template keeps getting better.

Customisation checklist per sub-account

After cloning the template, here's what needs to be customised per client:

• Phone numbers (Twilio numbers assigned to this client)
• Calendar availability and booking links
• Business hours (timezone-aware)
• Contact details in email/SMS templates (agent names, business name)
• Pipeline stage values (close reasons, industry-specific stages)
• Tag taxonomy additions (industry-specific tags)

Everything else — the workflow logic, the sequence structure, the automation triggers — stays the same. This consistency is what makes management at scale possible.

---

The monitoring workflow

With 13 sub-accounts, you cannot monitor everything manually. You need a systematic monitoring routine and alerts for the things that can't wait.

Critical metrics to watch daily

For each sub-account, I track:

1. New leads entered (vs. expected based on campaign activity)
2. First contact rate (% of new leads who received automated outreach in under 5 minutes)
3. Response rate (% of outreach that got any reply)
4. Appointments booked (daily and weekly)
5. Active automations running (if a workflow errors out, it stops here)

This is a 10-minute check in GoHighLevel's reporting section. I run it every morning before anything else.

Alerts for critical failures

Certain things can't wait for the daily check:

Twilio number suspension: If a sending number gets flagged by carriers, all outbound SMS from that sub-account stops. I set up a Zapier monitor that checks message delivery rates hourly and fires a Slack alert if delivery drops below 70%.

Workflow errors: GoHighLevel shows workflow error counts in the dashboard. Anything above zero gets investigated immediately.

Calendar booking failures: If the calendar integration breaks, leads are qualifying but can't book. I monitor booking counts against qualification counts — if the ratio drops significantly, something's wrong.

Rate limit warnings: If a sub-account is approaching Twilio send limits, we get ahead of it before messages start failing.

The weekly review

Every Monday morning:

1. Review previous week's stats for every sub-account
2. Identify any sub-accounts underperforming vs. their benchmarks
3. Check for any contacts stuck in pipeline stages (pipeline stage "stuck contact" reports)
4. Review any flagged contacts that need manual attention
5. Update any sequences that had low performance metrics

This takes about 45 minutes for 13 sub-accounts when you have consistent dashboards and know what you're looking for.

---

Separation concerns: what can't be shared

Some things in GoHighLevel are shared across sub-accounts (your main Twilio account, your Mailgun domain). This creates considerations:

Twilio compliance: All numbers across all sub-accounts run through your agency's Twilio account. If one client's campaign sends high-volume messages that violate carrier guidelines (too promotional, no opt-out, wrong A2P category), you can get your entire Twilio account suspended — taking down all 13 clients.

This means having a clear campaign compliance review for every new client before they go live. Opt-out keywords in every message. Proper A2P 10DLC registration for every number. Business hours respected.

Domain reputation: If you're sending email through a shared domain, one client's spam complaints can affect all clients' deliverability. Better to use dedicated subdomains per client for email.

API rate limits: Heavy API usage in one sub-account (large bulk operations) can affect other sub-accounts' API performance. Schedule bulk operations for off-peak hours.

---

The most common mistakes

After managing 13 sub-accounts for 18+ months, here are the mistakes I've seen most often:

1. Building from scratch each time

If you're spending more than 2 days setting up a new sub-account, your template isn't complete enough. Every hour you spend reinventing the wheel is an hour of billable work you're not recovering.

2. Not tagging contacts consistently

When your tag taxonomy differs across sub-accounts, your cross-client analytics become impossible. You can't answer "across all my clients, what's the average time-to-book by lead source?" if sources are tagged differently everywhere.

3. No separation between client credentials

Keep each client's third-party credentials (their own Twilio if applicable, their own calendar, their own email domain) documented and separate. When a client offboards, you need to be able to hand off cleanly without digging through a mess.

4. Treating workflows as "set and forget"

Every workflow needs to be reviewed monthly. Carrier guidelines change. Conversion rates shift. What worked 6 months ago might not be the best approach today. Build a review cadence into your operating routine.

5. No escalation path for manual contact

Not everything can or should be automated. Some leads need a human touch. Build clear escalation paths — specific pipeline stages, specific tags — that push leads to human attention rather than continuing to automate.

---

The actual output

With this system running properly across 13 sub-accounts:

• Onboarding time for a new client: 4–6 hours (not 2–3 days)
• Daily monitoring time: 30–45 minutes (not full-time)
• Error detection: within hours, not days
• Consistency of execution: identical across all clients, regardless of industry

The 13-client threshold was never a ceiling — it was just where the client count was at the time. The system doesn't really have a limit. You add a sub-account, clone the template, customise, go live. The marginal time to manage each additional client drops with every one you add.

If you're building out a multi-client GoHighLevel operation, get in touch — this is something I help clients set up properly from the start.