Client builds and pages
Reuse a build across client accounts
Find your snapshots, share one, and know exactly what does not travel with it.
What you'll get
- Every snapshot on your agency, named, so you can pick one without hunting through the agency view.
- A clear split between the ones you built and the ones you imported from somebody else.
- An honest list of what a snapshot leaves behind, which is the part that costs people a day when they find out late.
Say this
List my snapshots.
Which of these snapshots did I build, and which came from somewhere else?
Give me a share link for the Client Launch Template.
The pro prompt
The exact ask we run on real client accounts
Proven liveList every snapshot on my agency with its name and id, and split them into the ones I built here and the ones that were imported from somewhere else. I am about to roll one out to a new client, so tell me which is the most recent version of my own template, and remind me what will not carry across when it is applied. This is a read. Do not apply anything.
Click the box to select it, then press ⌘C (or Ctrl+C)
Everything in [brackets] is yours to change. Ask for the version explicitly. Agencies accumulate templates named v1 through v4.6, and applying last year's to a new client is a quiet, expensive mistake.
What does not travel
A snapshot carries structure. It does not carry the specifics, and nothing warns you.
| Travels | Does not travel |
|---|---|
| Workflows, pipelines, calendars, forms, funnels | Custom value values. The keys arrive, the values arrive empty |
| Custom field and custom value definitions | Anything typed into a knowledge base for the old client |
| AI agents and their knowledge bases | Your Private Integration key. Each account needs its own |
The custom values one catches everybody. Every text and email that referenced {{custom_values.booking_link}} now renders with a hole in it, and the workflow still reports success. Fill the values in as step one of every rollout, before you turn anything on.
Good to know
- Snapshots are a copy, not a link. Fixing a workflow in your template does not fix the twelve accounts you already applied it to.
- Check whether workflows arrive published. A snapshot that lands live starts messaging real contacts the moment the account has any, which is rarely what you want on day one.
- Name your snapshots with versions and dates. "Client Launch Template v4.6" tells you something; "Client Template Final" does not.
- Imported snapshots are somebody else's work and can change out from under you. If a template matters to your business, build your own from an account you control.
- Applying a snapshot is an agency-level action. Reading the list works with your agency key; the rollout itself happens in the GHL agency view.
- Needs the full license.
Where people go wrong
| What happened | The fix |
|---|---|
| "The new account's texts have gaps where the details should be." | Custom values arrived empty. Fill them in before switching anything on. |
| "The bot is answering with the last client's information." | Knowledge base text was written for that client and copied verbatim. Rewrite the answers for the new one. |
| "It started messaging people on day one." | Workflows came across published. Check their status before the account has contacts in it. |
| "Claude cannot see the account I just made." | A new sub-account has no Private Integration key yet. Create one in that account, then save it. |
| "I applied the wrong version." | Ask for the list first and read the names. Version numbers exist for exactly this. |