What actually belongs in a GoHighLevel agency snapshot

“Agency snapshot” is one of the more slippery phrases in GoHighLevel, because it is used for two products that share almost nothing.

The first is the snapshot that runs your agency. Your lead capture, your proposal pipeline, your onboarding sequence, your retention touches. It lives in one sub-account, it never gets deployed anywhere, and it is the thing that stops you running an automation business on a spreadsheet and a calendar link.

The second is a snapshot you deploy into a client’s sub-account. It is a vertical system — HVAC, dental, mortgage — and its whole job is to be redeployable by somebody who did not build it.

Both are legitimately called agency snapshots. Confusing them is the structural mistake that costs the most, because every install of the hybrid ends with you deleting your own pricing page out of a client’s account.

The one that runs your agency

Nobody can sell you this one usefully, because it encodes your delivery process, and your delivery process is the thing your agency actually is. Here is what belongs in it.

Inbound capture, honestly wired. A form, a calendar, a chat widget, and a single pipeline that everything lands in. Most agencies have three lead sources and no shared definition of what “qualified” means, which is why their pipeline reporting is fiction.

A proposal stage that is a stage. Sent, viewed, followed up on day 2 and day 5, marked dead at day 14 with a reactivation tag rather than a deletion. The deletion is why agencies believe they have no pipeline; the leads are there, they were just tidied away.

An onboarding sequence that starts the clock. The single biggest delay in agency delivery is not the build, it is waiting on the client for DNS access, brand assets and decisions. That waiting should be automated and chased on a schedule, not remembered. The 14-day onboarding playbook has the full sequence and the two review gates that keep it from becoming six weeks.

Retention touches. A monthly check-in, a quarterly review booking, a renewal conversation that happens before the charge rather than after the complaint.

A reactivation campaign for your own list. Agencies run these for clients and never for themselves. Every agency has two years of leads that went quiet, and they are the cheapest pipeline available. If you would rather it were built and run for you than built by you, that is a database reactivation campaign.

Notice what is not in that list: funnels for a client’s industry, review request automation for a service business, appointment reminders for a walk-in trade. Those belong to the other snapshot.

If you want the agency-side account built properly and once — pipelines, sending identity, phone registration, the lot — that is agency account setup.

The one you deploy to clients

Here the requirement inverts. It must work for a business you have not met yet, installed by somebody who did not build it.

Ours is always the same nine components, rewritten in each vertical’s own vocabulary:

1. AI receptionist — answers every call, qualifies, books, transfers the hot ones.
2. AI outbound caller — works missed appointments, cold leads and old customers.
3. AI chatbot — website, SMS, email, Facebook and Instagram.
4. Professional website — pre-written copy, compliant forms, booking calendars.
5. Smart appointment system — confirmations, 24h/1h/15min reminders, no-show recovery.
6. Review harvesting — the trigger that fires at job completion.
7. Review automation — the ongoing multi-channel cadence and follow-ups.
8. Database reactivation — the six-month inactive trigger and win-back offers.
9. Lifetime nurture — seasonal reminders, offers, referral prompts.

The set does not change between a roofing snapshot and a dental practice snapshot. The vocabulary does, completely: a roofer has jobs and storm season, a dentist has visits and recall intervals, and every message, field name and pipeline stage follows from that. Nine components, twenty-one vocabularies, in the full library.

Two of those nine cause the most argument, so to be explicit about it: review harvesting is the trigger and capture at the moment a job completes, and review automation is the ongoing engine — the follow-up cadence, the multi-platform links, the escalation path for someone who is not happy. They are a trigger and a machine, not two names for the same thing.

What must never cross between them

This is the part worth writing down, because the leakage is easy and embarrassing.

• Your pricing. Custom values holding your rates have a way of surviving into a client’s account.
• Your brand. Email footers, funnel favicons, calendar descriptions, SMS sign-offs.
• Your internal notifications. A client-facing snapshot that notifies your Slack on every booking is a snapshot that notifies your Slack on every client’s every booking, forever.
• Your sales sequences. Nothing in a client’s account should ever pitch your agency to their customers.

The clean way to prevent all four is to keep the two snapshots in separate source sub-accounts from day one, and never take a client-facing snapshot from the account you run your own agency in. It is a five-second decision at the start and a genuinely painful one to unpick later.

The naming and structure that makes both survivable

Whichever you are building, three disciplines decide whether it is still usable in a year.

Prefix everything. Every asset — workflow, funnel, pipeline, custom field, template — gets a short identifier. Imports add rather than replace, so without a prefix your second snapshot’s “Follow Up” workflow sits next to your first one’s “Follow Up” workflow and neither of you can tell them apart in a trigger dropdown.

Put every client-specific detail in a custom value. Business name, phone, booking link, address, offer, sending identity. If it differs per client, it is a variable, not a typed string. This is the single largest determinant of how long an install takes.

Reference nothing that cannot travel. Snapshots carry configuration, not connections. Phone numbers, payment integrations, Google Business Profiles, sending domains and users all stay behind. Anything wired to one of those arrives pointing at nothing, so keep a written list of what has to be reconnected — that list is your install guide, and it is the most valuable document in the whole product.

Full mechanics for building one that survives redeployment are in how to create a GoHighLevel snapshot, and the import-side checklist is in how to install one.

Build it or buy it

Straight answer, and it differs by which snapshot you mean.

The agency-side one: build it. It encodes your process. Buying somebody else’s is buying their process, and you will spend longer bending it than building yours.

The client-facing ones: buy until you have three in the same vertical. A custom build pays for itself through redeployment, so below three clients of a type the redeployment saving never catches the build cost. The arithmetic is worked through in snapshot vs custom build. Above three, commission a custom snapshot build designed for your delivery from the start.

Everything in our library is licensed for unlimited sub-accounts rather than per install, delivered within 24 business hours — business hours being 9am to 5pm Central, Monday to Friday — and installed free of charge with 12 hours of dedicated support to be used within 10 days of purchase. All sales are final once the link has been sent. Pricing is published, $890 to $2,490 by vertical depth.

Separate the two snapshots first, though. Every other decision here is easier once you have.