· 8 min read

GoHighLevel for Agencies: Snapshots, SaaS Mode and a Setup Checklist

GoHighLevel for agencies:agency vs sub-accounts, which plan unlocks SaaS mode and white label, how snapshots work and a setup checklist with common mistakes.

Head of Marketing & Growth
Summarize with AI
GoHighLevel for Agencies: Snapshots, SaaS Mode and a Setup Checklist

GoHighLevel works for agencies because of three things: one agency account that controls many client sub-accounts, snapshots that copy a complete client setup in minutes, and SaaS mode, which lets you sell the platform under your own brand with your own plans and billing. White label and unlimited sub-accounts start on the $297/month Unlimited plan, while SaaS mode and usage rebilling with a markup require the $497/month tier. The platform pays off only when every sub-account is set up properly: sending domain, A2P 10DLC registration, pipelines, calendars and workflows.

Agency account vs sub-accounts

HighLevel has two levels. The agency account is your control panel: billing, branding, users, snapshots, SaaS settings and the list of clients. Each client gets a sub-account (formerly called a location) with its own contacts, conversations, pipelines, calendars, funnels, phone numbers and email sending settings.

This separation matters for two reasons. First, client data never mixes: a contact in one sub-account is invisible in another. Second, most configuration happens inside the sub-account, so a well-designed agency builds a standard sub-account once and reuses it, instead of configuring every client by hand. A common mistake we see is an agency running its own sales pipeline inside the agency view and its clients in sub-accounts with no shared structure. Keep your own agency business in a separate sub-account, just like a client.

Plans: which one unlocks SaaS mode and white label

At the time of writing, the official pricing page lists three self-serve tiers:

  • Starter, $97/month. Up to 3 sub-accounts. Fine for a single business or a small trial, not for an agency that plans to grow.
  • Unlimited, $297/month. Unlimited sub-accounts, a white-label desktop app under your own domain and branding, basic API access and pass-through billing for usage. Phone usage rebilling on this plan works for sub-accounts on LeadConnector Phone and is charged without your markup.
  • Agency Pro, $497/month (labeled Founder on some HighLevel pages). Everything in Unlimited plus SaaS mode with unlimited reselling and rebilling with your own markup on phone, email and other usage.

A white-label mobile app is a paid add-on on the standard plans and is included in the custom-priced Enterprise tier. Usage (SMS, calls, email, AI features) is billed on top of every plan. Plan names and bundles change often, so check the pricing page before you commit.

Snapshots: what they include and how to deploy and update them

A snapshot is a template of a sub-account. According to HighLevel's help center, it carries the building blocks: workflows and triggers, funnels and websites, calendars, forms and surveys, email templates, custom fields, custom values, pipelines, membership content and similar assets.

What a snapshot does not carry is just as important. Contacts, appointments, conversations, reputation data, Stripe connections and third-party integrations stay behind, and lead gen forms are excluded too. Every new sub-account still needs its own phone numbers, sending domain, calendar connections and payment setup.

Deployment works in three ways:

  • New client. Create the sub-account from the snapshot and all assets are loaded at once.
  • Existing client. Load the snapshot into the sub-account. HighLevel checks for conflicts and asks, asset by asset, whether to override the existing version or skip it. Overriding replaces the client's version and cannot be undone through the load.
  • Updates. Edit the master sub-account, refresh the snapshot to add or remove assets, then push the new version to selected sub-accounts.

In our projects, the safe pattern is a dedicated master sub-account that is never used for live clients, custom values for everything client-specific (business name, phone, address, booking link) and a test sub-account where each snapshot version is loaded before it goes anywhere else. Pushing an update that overrides a workflow a client has customized is the most common way agencies break a working setup.

SaaS mode basics: plans, billing and rebilling

SaaS mode turns your agency into a software vendor. Instead of charging a retainer and paying for the platform yourself, you sell your own branded plans and the client pays you a subscription.

In practice, it works like this:

  • Payment provider. You connect your agency to Stripe. Newer SaaS versions also list other processors, but Stripe remains the standard path, and the connection cannot be removed while active SaaS billing depends on it.
  • Plans. In the SaaS configurator you define your own plans: price, trial period, which features each plan enables and which snapshot is loaded when a client signs up.
  • Onboarding. A client buys through a checkout link generated by the configurator, and a sub-account is created and set up automatically.
  • Rebilling. The client adds their own card to the sub-account, and phone, email and other usage is charged to them. On the $497 tier you can apply a markup; HighLevel's default multiplier is 1.05x, which roughly covers payment processing fees.

SaaS mode is a business model, not a feature you switch on. You become responsible for client onboarding, support, compliance questions and failed payments. If you do not have a support process, start with managed accounts and add SaaS later.

Setup checklist for every sub-account

Whether you sell services or SaaS plans, the same areas decide if the account actually delivers leads and messages:

  • Domain and email sending. Use a dedicated sending domain or subdomain (for example mail.clientdomain.com), publish the SPF, DKIM and DMARC records HighLevel shows, and make sure the From address is on the same domain. Start DMARC with p=none and tighten it once reports are clean.
  • A2P 10DLC registration. Business text messages to US numbers over local 10-digit numbers require a registered brand and campaign. Submit accurate business details, a real opt-in description and sample messages that match what you will send. Registration and monthly campaign fees are passed through from carriers and The Campaign Registry.
  • Phone numbers. Buy local numbers in the client's area, attach them to the registered campaign, set call forwarding and missed-call text-back.
  • Pipelines. Few stages, each with a clear exit criterion. Stages should reflect the client's real sales process.
  • Calendars. Connect each team member's Google or Outlook calendar, set buffers, availability and confirmation and reminder messages.
  • Forms and funnels. Every form needs consent language for SMS, hidden UTM fields and a mapped pipeline stage.
  • Workflows. Speed-to-lead response, booking reminders, no-show follow-up, nurture and internal notifications.
  • Reputation and reviews. Connect the Google Business Profile and send review requests after a completed job, not after every contact.
  • Integrations. Ad lead sources, the website if it lives outside HighLevel, accounting, Stripe and any webhook flows.
Setup areaWhat to configureCommon mistake
Email sendingDedicated subdomain, SPF, DKIM, DMARCSending from a Gmail address or a mismatched domain
A2P 10DLCBrand, campaign, opt-in proof, samplesVague use case and no consent on forms
Phone numbersLocal numbers, forwarding, text-backTexting before the campaign is approved
PipelinesStages with clear exit rulesTwelve stages nobody updates
CalendarsSynced calendars, buffers, remindersDouble bookings from unsynced users
Forms and funnelsConsent text, UTM fields, stage mappingLeads landing with no source
WorkflowsResponse, reminders, follow-upOverlapping workflows texting one lead twice
ReviewsGoogle profile, post-job requestAsking every contact, including lost leads
SnapshotsMaster account, custom values, versioningPushing updates that override client edits

If you want this done once and turned into a reusable snapshot, our GoHighLevel setup service starts at $2,000 and typically takes 2–4 weeks.

When GoHighLevel is the wrong choice

HighLevel is built for agencies and local service businesses. It is a poor fit when:

  • The client is a B2B company with a long sales cycle, multiple departments and strict reporting needs. A dedicated CRM with a deeper data model will serve them better.
  • The client already runs a CRM that the sales team likes, and all they need is better lead capture. Connecting forms and ads to the existing system is cheaper than a platform switch.
  • Nobody will own the account. A platform with dozens of modules decays fast without someone to maintain workflows and numbers.
  • Most messaging goes outside the US and Canada, where SMS pricing and phone options differ.
  • You want SaaS revenue but have no support capacity. Branded software with unhappy users hurts the agency brand.

When the answer is a different CRM, or HighLevel plus existing tools, the work shifts to CRM setup and migration (from $2,000; a pure CRM migration starts at $2,500) or to integrations and automation between the systems you already use.

Our decision rule

Choose GoHighLevel if you manage three or more clients with a similar lead flow (form or call, text, booking, review) and can reuse one snapshot for most of them. Start on Unlimited for managed accounts and white label. Move to the $497 tier only when you have a defined SaaS offer, a Stripe account, an onboarding process and someone to answer client questions. If your clients differ so much that no shared snapshot makes sense, HighLevel loses most of its advantage, and a client-by-client CRM choice is the better path.

FAQ

Questions & answers

Contact us

No. At the time of writing, the white-label desktop app with your own domain and branding is part of the $297/month Unlimited plan. The $497 tier adds SaaS mode and rebilling with markup, and the white-label mobile app is a separate add-on or part of Enterprise.

No. Snapshots copy structure: workflows, funnels, calendars, forms, custom fields and similar assets. Contacts, appointments, conversations, reputation data, Stripe connections and integrations are not included, so data has to be imported separately.

It can. When you load a snapshot into an existing sub-account, HighLevel flags conflicts and lets you override or skip each asset, and an override cannot be undone through the load. Test every version in a separate sub-account first and only override assets the client has not customized.

Brand checks can be quick, but campaign review by carriers and vetting partners often takes from several days to a few weeks, longer if the submission is rejected. Plan the registration at the start of the project and avoid sending business SMS until the campaign is approved.

Stripe is the standard and best-documented processor for SaaS mode, and older SaaS versions support only Stripe. Newer versions list additional processors, so check which options your account shows before planning billing.

10+ years in business, 100+ projects, clients in 9+ countries