What is in a GoHighLevel snapshot when it lands

Why this list carries no numbers

A GoHighLevel snapshot is a packaged copy of a configured sub-account, and what it delivers is a set of working behaviours rather than a quantity of objects. Counting the objects tells you almost nothing, because one well-written sequence can do the work of several badly split ones, and the badly split version looks better in a listing.

There is a second reason, and it is the stronger one. A count is a promise nobody checks. You cannot audit the contents of a snapshot until it is imported into a live account, and by then the link has been sent and the sale is final. A claim that cannot be verified before purchase should not be made before purchase. So the list below says what arrives and what each piece is for, and stops there. The method for testing whether any of it was written for your trade is set out separately in how to judge a snapshot before you pay.

Thirteen entries, in the order they appear on every edition sheet in this library.

The inventory

An AI receptionist

The phone answering that runs when nobody in the building can pick up. It takes the call, asks the qualifying questions your trade actually asks, and either books into the diary or captures enough that a human can call back knowing something. Its value is measured at nine at night and eleven on a Saturday, not at midday on a Tuesday.

An AI chatbot

The same job across text, the website chat widget, email and social messages. It exists because a proportion of enquiries will never ring; they type, wait a few minutes, and go elsewhere. The chatbot holds that conversation and hands it over cleanly rather than restarting it when a person joins.

Pipelines

The stages a job or a case moves through, named in your trade’s language rather than a sales textbook’s. Pipelines are where an account stops being a contact list and becomes a record of what is actually happening. A stage nobody uses is worse than no stage, so an edition carries the stages the trade genuinely moves through.

Workflows

The automation behind everything else: what fires, on what trigger, with what delay, and what happens when a condition is not met. Most of the writing in a snapshot lives here, invisible until it runs. The branch nobody thinks about, the one that handles a reply arriving mid-sequence, is the branch that separates a built system from a demonstrated one.

Appointment reminders, confirmations and no-show recovery

The diary work. Confirmation on booking, a reminder ladder pitched at the intervals the trade needs, and a recovery attempt when somebody does not turn up. The recovery is the part most builds omit, and it is the part with the clearest arithmetic behind it. The ladder itself is set out in the piece on no-show recovery.

Funnels

The pages that take an enquiry from an advertisement or a search result to a booking, without the detour through a home page. Funnels carry their own copy and their own forms, and both are trade-written or they are decoration.

An AI Studio website

The site itself, built and written to be found rather than to be admired. It arrives with the edition’s own words in it. During installation it takes your name, your colours, your contact details and your service wording, and the placeholder copy is replaced rather than hidden behind an image.

A nurture campaign

The long game for enquiries that did not buy. Different trades need wildly different patience here: a borrower comparing rates and a homeowner deciding about a roof are on different clocks, and the campaign’s intervals should show it. Nurture is where a generic snapshot is most obviously generic.

Review automation

The engine that asks for reviews on an ongoing basis, routes an unhappy response to a person before it reaches a public profile, and keeps the ask from arriving twice for the same job. The target it is built to hold is five to ten reviews a month, and that is the system’s target rather than a measured result from anybody’s account.

Seasonal automation

The work that only makes sense at a particular point in the year: the first hot week, the storm anniversary, the renewal window, the quiet quarter. Seasonal sequences sit dormant most of the year, which is exactly why they are the first thing missing from a general build.

Custom values

The reusable business details wired through every message: your trading name, your hours, your booking link, your address, your policies. Set once, referenced everywhere. When these are configured properly a rebrand is an afternoon; when they are not, your old company name appears in an SMS eight months later.

Custom fields

The fields on the contact record that hold what your trade needs to know about a person. A law firm’s matter type is not a car wash’s vehicle size. Fields decide what your automation is able to say, because a sequence can only reference what somebody thought to capture.

Forms and surveys

The capture side: enquiry forms, intake questions, feedback surveys. Written to ask the fewest questions that still let the next step be automatic, and mapped to the custom fields above rather than dropped into a notes box nobody reads.

What arrives around it

The file is not the whole transaction. Your edition is set and sent inside one working day, counted as twenty-four business hours between 9am and 5pm Central, Monday to Friday, with no weekend deliveries. Installation is free: eleven hours of installation time, to be booked and used within nine days of purchase. All sales are final once the snapshot link has been sent, which is why every edition sheet is readable in full beforehand.

Read one and see how the thirteen entries change shape by trade. The Law Firm edition is a good test case, because intake that screens before it books is a constraint most trades do not have. The sequence from order to live account is on how it works.