How to Install a GoHighLevel Snapshot, Step by Step
To install a GoHighLevel snapshot, sign into the agency account that owns the destination sub-account, open the share link and import it, then set the custom values before anything runs, rebrand the website it ships with, register A2P/10DLC, connect calendars and numbers, and test one booking and one deliberate no-show.
The order of operations, before the detail
Install a GoHighLevel snapshot in this order: sign into the correct agency account, import the share link into the destination sub-account, fill the custom values, rebrand the shipped website, register A2P/10DLC and authenticate sending, connect calendars and numbers, then test.
The order matters more than any individual step. Every installation that goes wrong goes wrong because something was published before the thing it depends on was set.
Two routes, and what each one costs you
| Self-install | Installation by us | |
|---|---|---|
| Cash | Nothing beyond the snapshot | $225 |
| Your time | An evening, plus the A2P wait | Supplying access and approving the rebrand |
| Who fills the custom values | You | Us, from details you provide |
| Who answers the carrier | You | Us, within the hours |
| Bounded by | Your patience | 8 hours, to be used within 9 days of purchase |
| Never included either way | Third-party integrations, third-party software, custom development | The same three |
The rest of this page is the first column, written out.
What you need in front of you
- The snapshot share link, and the sub-account you intend to load it into
- The agency login that owns that sub-account
- Your business details: legal name, address, phone, service area, hours, booking preferences
- A domain or subdomain you can point at the site
- The A2P/10DLC information — legal entity name, EIN, business address, a website URL and a sample message
Assemble these first. Half of a slow install is looking for an EIN.
Step 1 — Sign into the right account, then open the link
A snapshot loads into a sub-account under whichever GoHighLevel agency you are currently authenticated as. Open the link from the wrong login and it lands in the wrong place.
Sign out, sign in as the agency that owns the destination sub-account, and only then open the share link. GoHighLevel will ask which sub-account to load into. Choose the destination, confirm, and wait — the import runs in the background and larger builds take several minutes to finish writing.
If the destination sub-account already has automations you rely on, stop and read the collision note in step 2 before you confirm.
Step 2 — Understand what an import can overwrite
An import is a merge, not a replacement. Two things collide predictably.
Custom values with the same name. The incoming build sets its own; anything you had under an identical name is at risk. Export or note your existing values before importing into a live account.
Assets with the same name. Workflows, funnels and calendars sharing a name with something incoming can end up duplicated or confusingly renamed. On a live account, rename yours first so the two sets stay distinguishable.
On an empty sub-account neither applies, which is why a fresh sub-account is the cheapest place to install.
Step 3 — Fill the custom values before anything runs
This is the step people skip and the one that produces the embarrassing text message.
The workflows in a well-built snapshot do not contain your business name. They read it from a custom value, so that changing it in one place changes it everywhere. That design is correct and it means the build ships with those fields empty.
Work through the whole list before publishing a single workflow. Typically:
- Business name as a customer should see it, and the trading name if they differ
- Main phone number, and the number that texts should come from
- Booking link and the calendar each booking type belongs to
- Service area, hours, and the after-hours boundary
- The review destinations the review automation should point at
- The address, for anything that gets sent or displayed
Leave one empty and the first message that references it goes out with a gap where a word should be.
Step 4 — Rebrand the website that came with the build
The snapshot ships an AI Studio website configured for the trade, not for you. Change it in this order so you do not redo work: global settings first — logo, colours, fonts, contact details in the footer — then page by page.
Read every page rather than the ones you assume matter. Service descriptions, area names and any place the shipped copy names a hypothetical business all need attention, and the pages nobody checks are the ones a prospect finds through search.
Point your domain or subdomain at it once the content is right, not before.
Step 5 — Register A2P/10DLC and authenticate your sending domain
Neither of these travels in a snapshot, because both are attached to your business identity rather than to the configuration.
Submit the A2P/10DLC brand and campaign registration from inside GoHighLevel. Carriers review it on their own schedule and frequently come back with questions — usually about the sample message, the opt-in wording, or a website that does not visibly show a privacy policy. Answer promptly; an unanswered query stalls indefinitely.
Set up domain email inside GoHighLevel at the same time, so that email is sent from an authenticated domain rather than spoofed from an address you do not control. Deliverability problems traced back weeks later are almost always this.
Text messages will appear to send before registration completes. They will not reliably arrive. Treat SMS as unavailable until the campaign is approved.
Step 6 — Connect calendars and numbers
Decide, explicitly, which calendar each booking workflow writes into and which number sends what. A build that ships with several booking paths will have several calendars, and the defaults are the builder’s, not yours.
Set the hand-over point too: where the AI receptionist stops and a person takes the conversation. That boundary is a business decision and no snapshot can make it for you.
Step 7 — Run the two tests that matter
Do not test by reading the workflows. Test by being a customer.
- Book yourself in. Use the public booking path, receive the confirmation, and let the reminder sequence run. Check every message for placeholders, wrong times and links that go nowhere.
- Miss the appointment deliberately. Let the time pass without attending and watch the recovery run fire. This is the sequence built around the no-show recovery the system targets — around 70% is the target it aims at, not an outcome you should expect on day one — and it is also the sequence most likely to be misconfigured, because nobody tests failure paths.
If both behave, the build is in. Turn the rest on.
Illustrative arithmetic on doing it yourself
Assume you have never installed a snapshot before, you set aside one evening, and A2P review takes three business days. Then: import, roughly ten minutes. Custom values, forty minutes if your details are to hand. Rebranding the site, two hours. A2P submission, thirty minutes plus waiting. Testing, thirty minutes.
That is an evening of your time plus a wait you do not control. Those numbers are a worked scenario with its assumptions printed, not a measurement of anyone’s install.
If that evening is worth more to you than $225, installation by us does the same work: loading the snapshot, rebranding the site, A2P/10DLC, domain email and a few extra automations, within 8 hours of installation work to be used within 9 days of purchase. It never includes third-party integrations, third-party software or custom software development, on any package, at any price.
Either way, the written path is in the PDF that ships with every order, and the installation page sets out both routes before you choose. Every build in the catalogue installs the same way.