HLAI Experts

Guide · Snapshots

Building a HighLevel snapshot: where each client value goes

Give each value one of three homes, on purpose: the Business Profile for the basics HighLevel's account merge fields read, Custom Values for anything the whole account shares, and Custom Fields for anything that belongs to one contact or record. In a GoHighLevel (GHL) snapshot, that choice decides what each new account has to fill in, and where a blank will show up if nobody does.

Rob EasonPublished

A snapshot can include Custom Fields and Custom Values, so the build arrives with its structure. What it can't do is know the next client's name, phone number or booking link. The work is deciding, value by value, where each piece of client information lives, so a copied account can be filled in once and checked before anything goes live.

Three homes for a value

Every piece of client information in a build belongs in one of these. Put it in the wrong one and it shows up later as a blank, or as the wrong business's details.

  • The Business Profile in company settings: the account's own details, such as the Friendly Business Name and Business Phone. Account merge fields read from here.
  • Custom Values, under Settings > Custom Values: information shared across the account's content. Change one and its references update.
  • Custom Fields: information that belongs to an individual record, such as one contact's answer on a form.
Shared by the whole account: a Custom Value. Belongs to one contact: a Custom Field.

When the Business Profile is the right home

Use a Business Profile field when the feature reading it supports account merge fields. The Friendly Business Name supplies the account name merge field, and Business Phone supplies the account phone merge fields. Merge field support varies by feature, so check every place that will read the value before you rely on it; an unsupported merge field can stay unresolved.

One trap catches new accounts: Business Phone only fills merge fields. Entering it doesn't provision a number the account can call from. That's a separate step in every copied account, and it's easy to assume it's done because the phone number shows up in messages.

Custom Values for everything the account shares

Custom Values hold the information an account reuses across its content: a booking link, a service area, the name a message is signed with. Because one edit updates every reference, a copied account needs each value changed in one place, not hunted down step by step.

In our builds, anything an AI agent's prompt reads goes in a Custom Value, so the prompt itself is identical in every copy and the client's details sit in one list. That's our convention, not a HighLevel rule. Agent Studio can also read Account variables straight from the Location settings, and either can work.

Custom Fields for what belongs to one contact

Custom Fields hold what's different for each record: a contact's preferred service, an answer from a form, a date that changes from person to person. Including them in the snapshot gives the new account the same fields, ready for its own contacts.

The usual mistake runs the other way: business-wide information stored in a contact field. Then it has to be filled in on every contact, and anything that reads it comes up empty for the contacts nobody filled in.

AI agents and blank variables

In AI Agents > Agent Studio, an agent can use Account, Custom Values, Right Now, Form Data and Contact variables. When a variable's source data is missing, it resolves blank, and the agent shows a gap where the value should be.

That's why a copied account needs its Business Profile and Custom Values filled in before its agent goes live, and why the test runs after they're filled, not before.

Filling and checking a copied account

Run this on every account that loads the snapshot, using the value list you made when you built it.

  1. List every client value the build uses and mark each one Business Profile, Custom Value or Custom Field.
  2. In the new account, complete the Business Profile fields that the account merge fields read.
  3. Go to Settings > Custom Values, fill in each value, use + Add Custom Value for any that's missing, and Save.
  4. Wherever a value goes into content, insert it with the picker, so the merge field is one that feature supports.
  5. In Agent Studio, save the agent and use Test to see each variable resolve with the new client's details.
  6. Set up the account's calling number on its own. Business Phone won't do it for you.

Rather have it set up for you?

We plan where every client value lives, build the snapshot around that plan and check a copied account resolves each one, starting with a 30-minute 1:1 with Rob.

Book a 1:1 with Rob

Questions

Snapshot value questions

What's the difference between a Custom Value and a Custom Field?
A Custom Value holds information shared across the account, and changing it updates every reference. A Custom Field holds information that belongs to an individual record, such as one contact. In a snapshot, shared client details go in Custom Values and per-contact details go in Custom Fields.
Does a snapshot include Custom Values?
Snapshots can include Custom Fields and Custom Values. HighLevel's snapshot overview doesn't spell out whether every value's contents come across in every case, so check each value in the new account before anything goes live.
Why does my AI agent leave a blank where the business name should be?
The variable's source is empty in this account. Agent Studio resolves missing values as blank. Fill in the Custom Value or Business Profile field the prompt reads, then use Test in Agent Studio to confirm it resolves.
Does entering a Business Phone set up calling?
No. Business Phone supplies the account's phone merge fields and nothing more. A number the account can call from is a separate setup.
Should AI prompts use Custom Values or Account variables?
Either can work. Agent Studio reads Account variables from the Location settings and can read Custom Values too. We put anything a prompt reads in Custom Values, as a convention, so every copied account fills its details in one place.
Rob Eason

Who you talk to

Rob Eason

Rob runs HLAI Experts and takes the 1:1 calls himself.

He is a HighLevel Certified Admin with the second-most reviews in HighLevel's Certified Admin Directory worldwide, all of them 5 out of 5.

He won HighLevel's Top New Subaccounts via AI Employee award in its 2025 Summer of AI Awards and taught HighLevel's official masterclass on its AI Employee.

Before HighLevel, he co-owned a 60-employee financial services firm and sold his share.

On the call he looks at your account, not a script.

5/5 across 83 reviews in HighLevel's Certified Admin Directory