GoHighLevel Agency Setup Guide: Features, Use Cases & Practical Guide

GoHighLevel Agency Setup Guide should begin with the agency's operating model rather than with random software configuration.

A clean HighLevel agency setup answers five questions:

What does the agency sell?

How are clients separated?

Which systems should every client receive?

Who can access each part of the account?

How does a new client move from sale to launch?

HighLevel provides several layers for answering those questions: an agency-level workspace, sub-accounts, an internal Agency Sub-Account, user permissions, reusable Snapshots, CRM, workflows, communication infrastructure and—on qualifying plans—SaaS Mode.

The mistake is configuring all of those independently.

A stronger architecture is:

Agency Business Model

↓

Agency Account

↓

Internal Agency Workspace

↓

Standard Client System

↓

Snapshot

↓

Client Sub-Account

↓

Customization

↓

QA

↓

Launch

If you prefer a shorter implementation-oriented companion resource, use our GoHighLevel Agency Setup Checklist while working through the steps below.

Start Your GoHighLevel 30-Day Free Trial →

A HighLevel agency account is the top-level environment from which an agency manages its own platform settings and client locations.

Client businesses generally operate inside individual sub-accounts, also called locations.

That creates a structure such as:

Agency

├── Client A Sub-Account
├── Client B Sub-Account
├── Client C Sub-Account
└── Agency's Internal Sub-Account

The separation matters.

Each client can have its own:

This prevents one client's operational data from simply becoming part of another client's workspace.

These two terms are easy to confuse.

This is the top-level administrative environment.

It is where the agency can manage areas such as:

This is a regular HighLevel sub-account designated as the agency's own internal business workspace.

HighLevel explains that an Agency Sub-Account represents the agency itself instead of an outside client. It can be used for the agency's own CRM and operations and, depending on plan and configuration, can also be involved in SaaS subscriptions, rebilling and payment-provider setup.

A useful structure is:

Agency View → Administration

and:

Agency Sub-Account → Run the Agency's Own Sales and Marketing

Your internal agency location can be used like any other business CRM.

For example:

Website Lead

↓

Agency CRM

↓

Sales Pipeline

↓

Discovery Call

↓

Proposal

↓

Won

↓

Client Onboarding

Possible internal assets include:

This keeps your own agency operations separate from client work.

The current main HighLevel plans are:

HighLevel currently lists unlimited contacts, unlimited users and 24/7 support on Starter. Unlimited adds unlimited sub-accounts, Basic API access and eligible phone/email rebilling without markup. Agency Pro adds SaaS Mode, automated sub-account creation, rebilling with markup, User/Agent Reporting and Advanced API access.

The public pricing page currently advertises a standard 14-day free trial. Extended promotional or partner trial routes can differ, so the signup offer should always be checked at the time of registration.

Starter can work when you are:

Its primary scaling limitation is:

3 Sub-Accounts

That can become restrictive quickly for a traditional agency.

Suppose you use:

1 sub-account for your agency

and:

2 client sub-accounts

You are already at the plan's listed sub-account capacity.

Unlimited is often more relevant once the business becomes a real multi-client agency.

Its key structural advantage is:

Unlimited Sub-Accounts

That means the plan itself does not impose the same three-location ceiling as Starter.

A conventional agency could therefore operate:

Agency Internal Account

Client 1

Client 2

Client 3

Client 30

without upgrading only because of client-account quantity.

Human delivery capacity is still a separate problem.

Agency Pro is currently $497 per month.

Its main additions include:

This plan becomes more relevant when your model changes from:

Agency Manually Creates Client Account

to:

Customer Purchases Plan → Account Provisioned

It is not required simply because you operate an agency.

Do not begin by building 30 workflows.

Write down the offer.

For example:

Lead Response & Appointment System for HVAC Businesses.

Now define the system behind it.

Lead Form

↓

CRM

↓

Immediate Response

↓

Qualification

↓

Calendar

↓

Appointment

↓

Follow-Up

This gives you a reason for every asset you build.

Without a defined offer, agency setup often turns into:

Feature → Feature → Feature

rather than:

Problem → System → Outcome

Before creating the master account, map the journey.

For example:

Google Ads → Landing Page

Landing Page → Form

Form → Contact + Opportunity

Workflow → SMS / Email

Lead → Calendar

Appointment → Pipeline

Service Complete → Review / Follow-Up

Now you know what HighLevel needs to support.

A repeatable agency should avoid building every client from an empty location.

Instead, create a clean internal implementation account.

For example:

HVAC MASTER

Build your standard:

This account becomes the source for your reusable system.

HighLevel defines a Snapshot as a reusable template created from a sub-account's configuration.

A Snapshot can capture supported assets including:

HighLevel also allows agencies to select all assets or handpick only the elements they want included.

The process is:

Build Master Sub-Account

↓

Agency View → Account Snapshots

↓

Create Snapshot

↓

Choose Source Account

↓

Select Assets

↓

Create

This turns your manual implementation into reusable infrastructure.

A Snapshot is created from an existing sub-account.

HighLevel specifically notes that you do not directly "build" a Snapshot first. You configure a sub-account and then capture that configuration.

So the correct sequence is:

Build → Test → Snapshot

not:

Snapshot → Somehow Build Inside It

Include repeatable infrastructure.

For example:

Avoid adding unnecessary assets simply because they exist.

A clean Snapshot is easier to maintain.

An agency may eventually have:

HVAC Lead System

Dental Consultation System

Real Estate Lead System

Agency Onboarding System

Each solves a different workflow.

For example:

Service Request → Response → Booking

Patient Inquiry → Consultation → Appointment

Lead → Discovery → Proposal → Onboarding

Niche-specific templates are usually more useful than one giant generic Snapshot.

HighLevel now allows agencies to create a new sub-account directly from a Snapshot.

The selected Snapshot loads during account creation instead of requiring a separate import afterward.

The workflow becomes:

Agency Dashboard

↓

Account Snapshots

↓

Select Snapshot

↓

Create New Account

↓

Enter Client Information

↓

Sub-Account Created With Assets

This can improve both speed and consistency.

HighLevel currently allows one Snapshot to be selected during the initial account-creation process.

Additional Snapshots can be applied later if needed.

This reinforces the value of a well-designed primary template.

When a Snapshot containing websites or funnels is loaded into a new account, HighLevel says those assets are copied as drafts.

They still require the correct custom domain and publishing configuration before becoming live.

So:

Snapshot Loaded ≠ Website Live

The fulfillment team still needs client-specific setup.

Snapshots are not only for brand-new sub-accounts.

HighLevel also supports loading them into existing locations.

This can add selected workflows, funnels, emails and other assets while preserving the existing client account and its data.

Use caution.

An existing client may already have:

Review conflicts before importing more assets.

After creating a client account, replace master-template information with real client information.

Review:

Do not assume the Snapshot handles client-specific identity.

A reusable template provides structure.

The fulfillment team provides customization.

HighLevel's current permission system is much more granular than simply choosing "Admin" or "User."

At agency level, access can be controlled through:

User Type

↓

Role

↓

Sub-Account Assignment

↓

Module Permissions

↓

Granular Permissions

HighLevel recommends using Account user type for people who should access selected client accounts without agency-wide access.

Use when someone genuinely needs agency-level access.

Examples:

Use when someone should work only in selected sub-accounts.

Examples:

The second option reduces unnecessary account exposure.

Role determines authority inside the permitted scope.

Broader administrative capability.

Access according to configured permissions.

This means:

Account User Type + User Role

can provide much tighter access than:

Agency + Admin

for someone performing routine client work.

Suppose a fulfillment specialist manages five clients.

Configure:

Specialist

→ Client A
→ Client B
→ Client C
→ Client D
→ Client E

instead of:

Specialist → Every Client

HighLevel specifically identifies restricted sub-account assignment as useful for fulfillment teams, sales teams and account managers.

HighLevel separates several high-impact capabilities.

These can include:

Do not enable them automatically.

Use:

Least Access Required

as the default.

Clients generally need access to their own location, not to Agency View.

HighLevel's recommended process is to open the client sub-account, go to its user settings and configure the client's role and permissions there.

This creates a cleaner boundary:

Agency Team → Agency/Assigned Accounts

Client Team → Client Sub-Account

At the sub-account level, HighLevel supports Only Assigned Data for supported records.

This can restrict a user's visibility according to assignments rather than exposing every supported record in the location.

For example:

Sales Rep A → Assigned Leads

Sales Rep B → Assigned Leads

This is different from feature permissions.

One controls:

Which records?

The other controls:

Which modules/actions?

HighLevel's updated Feature Permissions system contains more than 80 controllable features for sub-accounts.

An agency can decide that one client sees:

Another client may receive a different feature set.

This is useful when the agency sells packages.

For example:

CRM + Calendar

CRM + Workflows + Reputation

CRM + Workflows + AI Agents + Phone

The product experience can match the package.

Every agency setup should start with the customer's real sales process.

Do not import a generic pipeline and assume it fits.

A service-business pipeline might be:

New Lead

↓

Contacted

↓

Qualified

↓

Appointment

↓

Estimate

↓

Won / Lost

An agency lead pipeline might be:

Lead

↓

Discovery

↓

Proposal

↓

Won

The CRM structure should reflect actual decisions.

Ask:

When does an opportunity exist?

For some agencies:

Every form submission → Opportunity

For others:

Only qualified leads → Opportunity

Choose intentionally.

Otherwise the pipeline fills with records that sales staff do not consider real opportunities.

Use custom fields for information the business actually needs.

Examples:

Avoid creating dozens of fields without a clear purpose.

The field should support:

Build or connect the ways leads enter HighLevel.

Examples:

Website Form

Funnel Form

Facebook Lead

Phone Inquiry

Import

The important test is:

Lead Source → Contact Record

and then:

Contact → Correct Automation

Submit real test leads.

Do not rely only on builder previews.

For appointment-based agencies or clients, verify:

Then run:

New Lead → Calendar → Test Booking

HighLevel's broader communications and automation tools become much more useful when booking is reliable.

HighLevel's current LC Email system is built into the platform and powers email sending and receiving at the sub-account level without requiring a separate Mailgun or SendGrid account for standard use.

However, sending from an authenticated dedicated domain is still an important setup step.

HighLevel's current getting-started process directs users to:

Settings → Email Services → Dedicated Domain and IP → Add Domain

followed by the required DNS verification.

A practical setup might use:

lc.clientdomain.com

as the authenticated sending subdomain.

HighLevel specifically recommends dedicated-domain setup for stronger:

Do this before sending substantial campaigns.

Do not wait until deliverability problems appear.

For LC Phone-managed accounts, HighLevel allows phone numbers to be purchased directly inside the intended sub-account.

The current setup path is:

Settings → Phone System → Add Number

Numbers can then support eligible:

Phone numbers exist at the sub-account level, so buy them from the correct client location.

Do not assume every number and communication feature works identically in every country.

Requirements can vary by:

HighLevel's phone-number purchasing documentation specifically notes identity and regulatory requirements as part of the process.

Verify the target market before building client pricing around communication usage.

HighLevel's current setup guide allows incoming calls to be forwarded to another number.

The path is generally:

Phone Number → Edit Configuration → Forward Calls

A local-business configuration could become:

Customer Calls HighLevel Number

↓

Forward to Business

If unanswered:

Missed Call Workflow

↓

Follow-Up

Do not start with 30 automations.

Start with the customer journey.

Form Submitted

↓

Create Opportunity

↓

Confirmation

↓

Notify Team

No Booking

↓

Wait

↓

Follow-Up

Appointment Booked

↓

Confirmation

↓

Reminder

No Show

↓

Rebooking Follow-Up

Service Complete

↓

Review Request

That may be enough to create significant operational value.

Suppose a lead books an appointment.

The system should not continue sending:

Book your appointment.

A complete workflow includes both:

What starts it?

and:

What stops it?

This is one of the most important agency automation principles.

Prefer:

Trigger → Action → Wait → Condition

when that solves the problem.

Do not build ten nested branches just to demonstrate technical skill.

Simple workflows are easier to:

Determine how inbound communication should be handled.

For example:

New Message

↓

Assigned Salesperson

or:

AI Handles FAQ

↓

Human Handoff

or:

Support Message

↓

Client Team

The agency should define responsibility before launching communication.

Otherwise conversations accumulate without ownership.

HighLevel has many modules.

Your client may not need all of them.

Only enable what supports the offer.

For example:

Needs:

May not need:

Feature count is not value.

Outcome is value.

Do not configure automation only for clients.

Your agency should use its own system.

For example:

Agency Lead

↓

Discovery Appointment

↓

Proposal

↓

Opportunity Won

↓

Client Intake Form

↓

Notify Fulfillment

↓

Create Internal Tasks

Now HighLevel helps run the agency as well as client marketing.

A clean onboarding process might be:

Sale

↓

Welcome Email

↓

Intake Form

↓

Asset Collection

↓

Access Collection

↓

Implementation

↓

QA

↓

Launch

Collect:

Do not begin technical implementation with incomplete intake.

For each delivery item, define completion.

Example:

This eliminates ambiguity.

Never treat:

Builder finished configuration.

as:

Client is ready.

Run an end-to-end test.

Landing Page

↓

Form

↓

Contact

↓

Opportunity

↓

Message

↓

Calendar

↓

Appointment

Test:

Test:

Test desktop and mobile where relevant.

Old contacts may already contain:

Use clean test records so the system behaves more like a real new lead.

Create internal notes for:

Use naming conventions.

Instead of:

Workflow Final 2 New

use:

LEAD – Website – Initial Response

Instead of:

Automation 17

use:

APPT – 24 Hour Reminder

Documentation becomes increasingly important when the person supporting the account is not the person who built it.

Explore GoHighLevel With a 30-Day Free Trial →

A simple launch sequence is:

Final QA

↓

Client Approval

↓

Connect Live Domain

↓

Publish

↓

Activate Workflows

↓

Begin Traffic

↓

Monitor

Avoid changing:

all at once without testing.

Controlled rollout is easier to troubleshoot.

Do not disappear immediately after launch.

Watch real leads.

Check:

Did Contact Create?

Did Opportunity Create?

Did Message Send?

Did Calendar Work?

Did Salesperson Receive Notification?

Test data can miss real-world edge cases.

Production monitoring catches them.

Define how the client reports issues.

For example:

Client → Support Form → Agency Support

Then classify:

Client needs training.

Client wants an approved modification.

Something expected is not working.

Client wants a new system.

Do not mix all four into random chat messages.

HighLevel specifically recommends reviewing permissions as responsibilities change.

This matters because agencies evolve.

A contractor may leave.

A VA may move to another client.

A manager may need additional responsibility.

Use:

Current Role → Current Access

not:

Access Granted Two Years Ago → Never Reviewed

When you improve your implementation:

Fix Master Account

↓

Update Snapshot Strategy

↓

Document Change

Do not only fix one client while leaving the standard deployment broken.

Your master system should represent your best current implementation.

Snapshots improve deployment consistency, but they should not be treated as live synchronization.

An existing client account remains its own account.

Therefore, when your standard system changes, decide:

Do not assume every client should automatically receive every new feature.

Suppose the agency sells to plumbers.

The product is:

Lead Response and Booking System.

Master infrastructure:

Lead Form

↓

CRM

↓

Immediate Response

↓

Calendar

↓

Follow-Up

Agency setup:

PLUMBER MASTER

↓

Snapshot

↓

Client A

↓

Customize Branding + Phone + Calendar

↓

QA

↓

Launch

Then repeat for Client B.

This is significantly more scalable than rebuilding every workflow manually.

A dental system might contain:

Patient Inquiry

↓

Consultation Pipeline

↓

Booking

↓

Reminder

↓

Follow-Up

The client-specific items include:

The reusable items include:

Separate:

Standard

from:

Client-Specific

A real-estate workflow could be:

Property Inquiry

↓

CRM

↓

Assigned Agent

↓

Follow-Up

↓

Viewing

HighLevel can handle the marketing and CRM layer.

It may not replace specialist transaction-management or property-management systems.

The agency setup should account for that.

A white-label fulfillment provider could create:

Agency Client

↓

Sub-Account

↓

Snapshot

↓

CRM + Workflows

↓

Handoff

Permissions become particularly important when several organizations participate in delivery.

Each party should access only what they need.

A SaaS-oriented agency might build:

Customer Selects Plan

↓

Subscription

↓

Sub-Account Creation

↓

Feature Set

↓

Snapshot

↓

Onboarding

HighLevel's SaaS-generated sub-accounts inherit supported feature permissions according to the feature configuration of the relevant SaaS plan.

This helps turn a service-heavy process into a more productized model.

Before launching SaaS, define:

What does each package include?

Which modules are available?

What system is preloaded?

Who pays for communication or premium services?

What level of help is included?

What happens to the client account?

SaaS Mode solves provisioning.

It does not solve your business model for you.

HighLevel's current Feature Permissions can be managed per individual sub-account or incorporated into SaaS plans.

This allows:

The software experience can therefore match the subscription package.

As the agency grows, organize users by function.

Needs:

Needs:

Needs:

Needs:

Needs:

HighLevel's current permission architecture supports this layered approach.

Create individual users.

Shared logins reduce:

A professional agency setup should be able to answer:

Who has access?

To which clients?

To which features?

HighLevel provides the mechanisms.

The agency still needs to use them properly.

At minimum:

HighLevel specifically treats sub-account transfers as high-impact actions affecting ownership, access, billing and integrations, so transfer permission should be given only to authorized users.

Do not calculate agency economics using only:

$297 HighLevel Subscription

Client communication can add usage costs.

Budget separately for areas such as:

Your agency pricing model should use:

Platform

Usage

Fulfillment

Support

Margin

=

Client Price

If a client pays a flat monthly fee but can create unlimited communication cost for the agency, margin can disappear.

Define:

This becomes increasingly important as the client base grows.

Once the agency is live, track more than account count.

Useful metrics include:

Lead → Discovery Call

Discovery → Won

Won → Intake Complete

Intake → Launch

Lead → Response → Appointment → Sale

Clients Retained / Clients Due for Renewal

HighLevel should support decisions, not only store data.

Software does not define the agency.

The business problem does.

Separate client businesses into appropriate sub-accounts.

Use Snapshots for repeatable systems.

Use Account-type users, sub-account assignments and granular permissions where appropriate.

Client-specific:

still need setup.

Run an end-to-end customer journey.

Start with high-value processes.

Configure the sending domain before scaling outbound email.

Phone numbers are managed at sub-account level, so purchase them from the client account where they will be used.

Your agency's sales pipeline is different from a client's sales pipeline.

Keep them logically separate.

Use Feature Permissions to keep client environments focused.

Agency Pro is useful when you actually need its additional SaaS and agency functionality.

Do not upgrade solely because it sounds more professional.

Define:

Configure:

Build:

Clean the master system.

Create reusable Snapshot.

Configure and test:

Create:

Test:

Lead → CRM → Follow-Up → Appointment

Deploy the system to one controlled client account.

Learn from the implementation.

Then improve the master system.

Only after the core journey works.

Phase 1:

Lead → Appointment

Phase 2:

Reputation / Reactivation

Phase 3:

AI / Advanced Automation

Phase 4:

SaaS / Productization

This sequence prevents feature overload.

Add AI where interpretation or conversation creates value.

For example:

Customer Question → Conversation AI

or:

Inbound Call → Voice AI

Do not add AI to a deterministic task such as:

Appointment Booked → Send Confirmation

A standard workflow is easier to understand.

Consider SaaS when you already have:

The sequence is:

Agency Service

↓

Repeated Pattern

↓

Standardized Product

↓

SaaS

Trying to productize chaos usually creates scalable chaos.

It depends on the number of client accounts and business model. Starter currently provides three sub-accounts, Unlimited provides unlimited sub-accounts, and Agency Pro adds SaaS Mode, automated sub-account creation and other advanced agency features.

Current public pricing is $97/month for Starter, $297/month for Unlimited and $497/month for Agency Pro. Annual options are currently $970, $2,970 and $4,970 respectively.

A sub-account is an individual HighLevel location that can represent a client business or, when designated appropriately, the agency's own internal workspace.

It is a regular sub-account designated as the agency's own business workspace. Depending on plan and setup, it can also support parts of SaaS, subscriptions, rebilling and payment-provider configuration.

For separate client businesses, individual sub-accounts generally provide the cleanest separation of CRM data, workflows, calendars, communications and users.

A Snapshot is a reusable template created from a configured sub-account. It can capture supported assets such as workflows, funnels, calendars, forms, campaigns and custom fields.

Yes. HighLevel can create a new sub-account using a selected Snapshot so the packaged assets are loaded as part of initial account creation.

Yes. HighLevel supports loading selected Snapshot assets into an existing sub-account while preserving the existing account and data.

No. HighLevel says copied funnels and websites arrive as drafts and still need the correct domain and publishing setup.

Yes. An Account-type user can be assigned to selected sub-accounts without receiving agency-wide access.

Yes. HighLevel currently provides user type, role, sub-account assignments, module permissions and granular action-level permissions.

Yes. HighLevel's current Feature Permissions system provides more than 80 controllable features and can be configured per sub-account or incorporated into SaaS plans.

Yes. LC Email is HighLevel's built-in email service for sub-accounts, although configuring a dedicated authenticated sending domain remains recommended for professional sending.

For LC Phone-managed sub-accounts, yes. Numbers are purchased inside the applicable sub-account and can support eligible calling, messaging, routing and automation.

No. Agency Pro is primarily relevant when you need its additional SaaS, automated account provisioning, rebilling and advanced API capabilities. Unlimited can support conventional multi-client agency operations with unlimited sub-accounts.

A strong GoHighLevel Agency Setup Guide should produce a repeatable business system, not merely a configured software account.

The foundation is:

Agency Offer

↓

Customer Journey

↓

Standard Client System

↓

Snapshot

↓

Client Sub-Account

↓

Customization

↓

QA

↓

Launch

Start by choosing the plan that matches the business model.

Starter provides three sub-accounts.

Unlimited removes that client-account quantity constraint.

Agency Pro becomes more relevant when the agency is ready for SaaS Mode, automated account creation and additional rebilling or API capabilities.

Next, separate the agency's own operations from client work.

Use the internal Agency Sub-Account for your agency where appropriate, while keeping individual client businesses in their own locations.

Build one strong master implementation.

Test it.

Create a Snapshot.

Then use that reusable configuration to speed up new account creation instead of rebuilding every CRM, calendar and workflow manually.

After deployment, customize the details that cannot be standardized:

Branding

Users

Calendar

Phone

Email

Domain

Business Process

Then control access carefully.

HighLevel's current permission architecture allows agencies to decide not only whether someone is an Admin or User, but also their scope, assigned client accounts, visible modules and supported granular actions.

Finally, test the customer journey rather than individual settings.

Run:

Lead → CRM → Response → Qualification → Appointment → Sale

If that path works reliably, the agency has a functional client system.

If the system can also be documented, duplicated and supported by another team member, the agency has something more valuable:

a repeatable delivery model.

That is the real objective of a professional GoHighLevel agency setup.

Claim Your GoHighLevel 30-Day Free Trial →