Ask an agency what its GoHighLevel product actually is and the honest answer is a snapshot: the set of pipelines, workflows, calendars, templates and funnels that every client account starts from. Build it well and onboarding a client is filling in a form; build it badly and every new account is a week of copying and fixing, or worse, a workflow that texts a client’s whole imported list at 3am. GoHighLevel snapshots are simple to make and easy to make wrong. This is how I build and maintain them for agencies.
It assumes you know the platform and how a sub-account is set up (the setup guide) and which workflows a service business needs, because the snapshot is those things, packaged.
What a snapshot carries — and what it does not
| Included | Not included (set up per account) |
|---|---|
| Workflows (with their draft/published state) | Contacts, conversations, opportunities |
| Pipelines and stages | Phone numbers and A2P registration |
| Calendars and settings (not the team assignment) | Users and team members |
| Custom fields, custom values, tags | Integrations: Stripe, Google, Facebook, Mailgun, Twilio |
| Email and SMS templates, snippets | Domains and DNS |
| Funnels, websites, forms, surveys, quizzes | API keys and private integrations |
| Memberships, courses, products (some) | Most business-profile settings and media uploads |
| Trigger links, custom menu links, reputation settings | Conversation AI training and some AI settings |
The right-hand column is the onboarding checklist. Everything on the left should be done once, in the snapshot.
Step 1: Build in a clean sandbox sub-account
Never snapshot a client’s account. Create a sub-account called “SNAPSHOT — Base” (and later “SNAPSHOT — Dental”, “SNAPSHOT — Roofing”), build in it, and take snapshots from it. It contains no real contacts, no real numbers, and every message template uses placeholders. Keep it, because updating the snapshot means editing this account and re-snapshotting.
Step 2: Custom values are the whole trick
Anything that differs between clients — business name, phone number, booking link, review link, owner’s first name, opening hours, service area, brand colour — becomes a custom value, and every template, workflow message and funnel page references the value, not the text: {{custom_values.business_name}}, {{custom_values.review_link}}. Onboarding a new client is then: load snapshot, fill in twenty custom values, connect the integrations, done. Agencies that hard-code “Dave at Northside Plumbing” into the snapshot spend a day per client finding and replacing it.
Name values clearly and group them with a prefix (biz_name, biz_phone, link_booking, link_review) and keep a one-page “values to fill” document that travels with the snapshot.
Step 3: What goes in the base snapshot
- Pipeline: New lead → Contacted → Booked → Quoted → Won / Lost, with a lost-reason field.
- Core workflows, in draft: missed-call text-back, speed-to-lead for form leads, appointment confirmation and reminders, no-show follow-up, review request, lead nurture, database reactivation, birthday or annual reminder. All using custom values.
- Calendars: a consultation calendar and a service calendar with sensible durations and buffers; team assignment is done per account.
- Custom fields: service needed, urgency, source detail, lead score, consent flags — the fields the workflows read and write.
- Tags convention:
source-*,status-*,consent-*, documented. - Templates: SMS and email for every message the workflows send, in the brand’s plain voice.
- Forms and surveys: a contact form, a quote form with qualifying questions, an intake survey.
- Funnel/site template: one lead funnel (landing, form, thank-you with calendar) and, if the agency sells sites, a website template; both using custom values for name, phone and links.
- Reputation settings and review request template pointed at the review-link value.
- Custom menu links to the agency’s help centre and support form.
Step 4: Niche snapshots extend the base
A dental snapshot adds recall reminders, treatment pipelines and patient intake; a roofing snapshot adds storm-season campaigns, estimate follow-up and a photo-upload quote form. Build niche snapshots by loading the base into a fresh sandbox, adding the niche assets, and snapshotting that. Keep the base and niche assets visibly named (“BASE — Missed call text back”, “DENTAL — Recall 6 months”) so an update to the base can be applied to niche accounts without confusion.
Step 5: Draft state, and the messages-to-strangers problem
A workflow saved as published in the snapshot is published the moment the snapshot loads. If a client imports 4,000 old contacts before you have reviewed the account, a published reactivation or birthday workflow will message all of them, from an unregistered number, with placeholders unfilled. Keep every workflow in draft in the snapshot, and make “publish workflows” the last onboarding step after custom values, number, A2P and a test contact are done.
Step 6: Version it like software
- Name snapshots with a version and date: “Base v2.3 — 2026-09”.
- Keep a changelog: what changed, why, and whether existing accounts need the update.
- Never overwrite the previous version until the new one has been loaded into a test account and the ten core scenarios have been run (form lead, missed call, booking, reminder, review, opt-out, and so on).
- Store the “values to fill” document and the onboarding checklist alongside each version.
Step 7: Updating live client accounts safely
Loading a newer snapshot into an existing sub-account lets you choose, asset by asset, whether to add new items, overwrite existing ones or skip. The rules I use:
- Snapshot the client account first (its current state) so there is a rollback.
- Add new assets freely; they arrive in draft.
- Overwrite only assets the client has not customised — check the modified dates, and ask.
- Re-check anything that references a calendar or a user, because those are account-specific and can reset.
- Publish the new workflows one at a time after a test contact runs through each.
Sharing and selling snapshots
Snapshots can be shared with another agency by link, permanently or as a one-time link, which is how niche snapshots are sold. Before sharing: remove anything client-specific, confirm every message uses custom values, put the values document and a setup video in a custom menu link, and set every workflow to draft. A snapshot that installs cleanly and documents itself is worth more than a bigger one that needs a support call.
Pre-load checklist for every new client
| Before loading | After loading |
|---|---|
| Sub-account created with business profile and time zone | Custom values filled (all twenty) |
| Owner user added | Phone number bought, A2P started |
| Integrations connected (Google, Facebook, Stripe, email sending domain) | Calendars assigned to team members |
| Contacts not imported yet | Test contact run through form, missed call, booking, reminder, review |
| Snapshot version confirmed | Workflows published one by one; then import contacts with consent tags |
Mistakes I see in agency snapshots
- Built from a real client account, complete with their name in forty templates.
- Published workflows.
- No custom values, so every account is a find-and-replace project.
- Ten near-identical snapshots nobody can update.
- No test account, so the first client is the test.
- No changelog, so nobody knows which accounts have which version.
The agencies whose GoHighLevel business runs smoothly — including the ones I build snapshots for as a white-label partner — treat the snapshot as the product and the sub-account as an installation of it. It is the difference between onboarding in an hour and onboarding in a week, and between a platform you resell confidently and one you apologise for. If you are reselling under your own brand, the plain-English guide explains where snapshots sit in the agency model.
Further reading: GoHighLevel Help Center.
FAQ
What does a GoHighLevel snapshot include?
Workflows, pipelines and stages, calendars and their settings, custom fields and custom values, tags, email and SMS templates, funnels, websites, forms, surveys, memberships and courses, trigger links and custom menu links. It does not carry contacts, conversations, phone numbers, connected integrations, users, domains or API keys.
Can I update an existing client account from a new snapshot version?
Yes — load the snapshot into the sub-account and choose which assets to add or overwrite. Test in a sandbox first: overwriting a workflow the client has customised replaces their changes, and adding a published workflow can start sending messages immediately.
How many snapshots should an agency have?
One base snapshot with the parts every client needs, plus one per niche that adds industry pipelines, templates and funnels. More than a handful becomes impossible to keep updated; the variation belongs in custom values, not in separate snapshots.
Can I sell or share a snapshot?
Yes. Snapshots can be shared by link with other agencies, permanently or as a one-time link, and there is an active market for niche snapshots. Strip anything client-specific first and document the custom values the buyer must fill in.
Want a base and niche snapshot built, tested against the ten scenarios, documented and handed over under your brand? See how the white-label partnership works — snapshots are the most common thing agencies ask me to build first.
