The mechanism
A GoHighLevel snapshot is a copy of a fully configured sub-account — its funnels, workflows, pipelines, calendars, custom fields and campaigns — that can be loaded into a different account and start running there.
That sentence is the whole of it, and it is worth being precise about, because "snapshot" gets used loosely enough that people buy expecting page designs. What you are buying is a working system: the same nine components in every build in this vault, arranged across five stages, arriving in your account as thirteen things you can see and edit.
The descent
Every build in the vault is wired this way. What changes between them is the language, the timing and the cadence — a roofer's storm call and a law firm's conflict check need the same machine set differently.
Somebody tries to reach you. Every route they might take — the phone, a text, a form, an advert, a message on a social account nobody watches — lands in one place, is answered immediately, and arrives with enough context to be useful.
A voice answers, holds a real conversation, works out what the caller actually needs and puts a time in the diary while they are still on the line. When the call is urgent enough to warrant a person, it hands over instead of pretending.
Website chat, SMS, email, Facebook and Instagram all reply at once, in the same voice, with the same questions. The reply is not an acknowledgement — it asks the thing that decides what happens next.
A submission from your site, a lead form on an advert, a landing page from a campaign — each one starts the ten days immediately and carries where it came from, so you can tell which spend produced which booking.
Most enquiries do not buy on the first day and almost nobody follows up past the second. Ten days of sequenced contact runs on its own, changes channel as attention moves, and stops the moment they book.
Email carries the explanation: what you do, what it costs to start, what happens on the first visit. It is written already, and it goes out whether or not anyone remembered.
Shorter, closer, on the device they answer. A dated reason to act, a link that books in one tap, and a way to say no that stops the sequence cleanly.
A call, because by day eight silence usually means an unanswered objection rather than a lost interest. It asks, it handles the ordinary ones, and it books or it leaves a message a person would leave.
A booking is not revenue until somebody turns up. Three things run between the booking and the door: confirmation while it is still fresh, reminders at the intervals that actually change behaviour, and a call within the hour when the slot goes empty.
A text with the time, the address and what to bring. A calendar invitation that lands in whichever calendar they use. Anything you need from them beforehand asked now, not on the day.
A day out, an hour out, and a last one shortly before. Each is a different length and asks a different thing, and every one carries a link that moves the appointment rather than forcing a phone call.
When somebody does not arrive, the call goes out inside sixty minutes while the day can still be rearranged. It asks what happened and offers the next available time in the same conversation. The system targets recovering around 70% of no-shows this way.
Reviews are the one asset that compounds and the one job that never gets done. The ask fires at the point the customer has something to say, it routes an unhappy answer inward rather than outward, and what comes back is put to work.
A couple of hours after the work is finished, a single question goes out. A good answer becomes a link straight to Google or Facebook. A bad one becomes an internal alert to somebody who can still fix it.
Every review gets a response in your voice. Praise gets thanked specifically rather than generically. A complaint gets acknowledged without arguing, and anything serious is escalated to a person rather than smoothed over.
New reviews appear on the site without anybody pasting them in, sit next to the enquiry forms where they do the most good, and keep the profile that search engines read looking active. The build targets five to ten reviews a month.
The last landing is the one that pays for the others. Contacts you already own get contacted again on a rhythm that suits the trade, get answered when they come back, and get asked to bring somebody with them.
Seasonal reminders when the season is actually relevant, a check-in at the interval that suits the work, something on the anniversary of the first job. Enough to be remembered and not enough to be muted.
An existing customer asking a question at nine at night gets an answer, not a form. Rescheduling, status, opening hours, what they paid last time — the routine questions are handled without waking anybody.
Contacts who have gone quiet past the point that is normal for your trade get a genuine reason to come back. Regulars get asked, occasionally and specifically, to recommend you — which is the cheapest lead you will ever get.
The nine
Nine components ship in every build, and there is no tenth. Padding a snapshot out with invented extras is how a catalogue stops meaning anything.
What each one does on a particular trade’s day is written out on that trade’s record. Open one and read the difference.
The handover
This is what you can open and edit once the snapshot is loaded. Two of them carry a number because there is exactly one of each; the rest are stated without a count, deliberately. A counted promise is a promise, and we would rather describe what is there than publish a figure nobody has checked against a real build.
Two things leave here when an order is placed.
A 24-business-hour release window applies to every order. Business hours are 9am to 5pm Central, Monday to Friday. Nothing is released at a weekend.
Installation is optional and costs $225. It buys 8 hours of installation work, to be used within 11 days of purchase. Once those hours are used, or the window closes, further work is quoted.
Covered
Never covered, on any package
Quoted separately, or handled by a virtual assistant.
Ask a question or see it first — before ordering, not after.
Before you payAll sales are final. The moment the order exists and the share link leaves us, the snapshot is in your hands and cannot be returned — so the order is non-refundable from that point. You will see this on the product page, in the cart and on the checkout, before you pay, not after.
A GoHighLevel snapshot is a copy of a fully configured sub-account — funnels, workflows, pipelines, calendars, custom fields and campaigns — that can be loaded into a different account and start running there. It is a working configuration, not a design template.
The import itself takes minutes. The work is what surrounds it: rebranding the site that ships with the build, registering A2P/10DLC, authenticating your sending domain and setting the custom values the workflows read. The written guide walks through all of it in order.
Yes. The same nine components and the same five stages ship in every build. What differs is when each part fires, what it says, and why that timing is right for the trade — which is what the individual records are about.
Usually, but it is the case to ask about first. A snapshot loaded over a live sub-account can collide with workflows and custom values that are already there, so it is worth a look before the import rather than after it.
Calls, texts and AI usage are billed by GoHighLevel against your own account at their rates. The snapshot is configuration; the running cost sits where your other platform usage already does.
Nothing is charged here. The tray holds what you have chosen.
The tray is empty.
Running total$0
Go to checkoutOpen the full releaseA 24-business-hour release window. All sales are final.
Reading and motion
Kept in this browser only. Nothing is sent anywhere and no account is involved.
What this site stores
No analytics cookie, no advertising cookie and no third-party tracker runs here. What is kept in your own browser is your lighting and seal choice, your accessibility switches, whatever is in your order, and the fact that you answered this. Nothing is sent anywhere. Read the privacy note.