A reused GoHighLevel account can look right until a customer hits one old detail.
The company name in the obvious settings looks correct. The main funnel has the new logo. A test message goes out. Then a customer clicks a reminder and lands on the previous booking page, an SMS shows the old phone number, or an email footer still names the business that originally owned the setup.
Those mistakes often come from two places: a reusable value that still contains old information, or a hard-coded detail that never used the reusable value in the first place.
A GoHighLevel custom values audit is the work of finding both. The point is not to open every page and patch whatever looks wrong. It is to identify the source values the account depends on, trace where they appear, find the places that bypass them, then test the customer-facing output after the corrections.
Changing the Business Profile does not update every source of business information
HighLevel has several kinds of values that can look similar when they appear inside an email, workflow, page, or calendar.
Location values pull information from the sub-account. User values can pull information tied to a user. Contact and Company fields can resolve from CRM records. Custom Values are different: they are reusable key-value pairs created under Settings > Custom Values and inserted wherever the platform supports them.
That difference matters during cleanup. A business can correct its main location phone number and still have a custom value called Support Phone holding the old number. The reverse can happen too. Someone updates the custom value, but a page still contains a phone number typed directly into the text block.
HighLevel’s current merge fields and custom variables overview separates these value types. Start there if the account uses several kinds of placeholders and nobody is sure which source should own a particular detail.
The audit needs to answer one practical question for each repeated detail: where is this supposed to come from?
Build the list around details a customer could actually see or use
Start with business information that could send somebody to the wrong place, make the company look inconsistent, or create a broken handoff.
That usually includes the business name, main phone number, address, website, support email, booking URL, review URL, sender identity, service or offer names, and any policy or legal links the account inserts into customer-facing content. If the setup uses reusable references to logos or other brand assets, include those too.
Do not turn the inventory into a catalog of every merge field in HighLevel. Contact first name, appointment time, opportunity value, and other record-specific fields solve a different problem. This audit is about reusable business details that may have been inherited, copied, or left behind during a rebuild.
| Detail | Possible source | Customer-facing failure |
|---|---|---|
| Business name | Location value, Custom Value, hard-coded text | Old company name appears in a message or page |
| Phone or support email | Location setting, Custom Value, workflow or template text | Replies and calls go to the wrong team |
| Booking or review link | Custom Value, trigger link, button URL, hard-coded message | Customer reaches an old calendar, page, or location |
| Service or offer name | Custom Value, template copy, funnel text | Old offer language survives after the rebuild |
| Policy or legal URL | Custom Value, footer, button, hard-coded page link | Customer is sent to an outdated or unrelated document |
A GoHighLevel custom values audit should start at the source
When several places show the same wrong detail, the source is the better place to look first.
HighLevel describes Custom Values as key-value pairs that can be created once and reused throughout the platform. When the stored value changes, places using that key resolve to the new value automatically. That is the reason to inspect Settings > Custom Values before fixing five emails one at a time.
Search the list for business names, phone numbers, addresses, domains, email addresses, booking links, review links, offer names, and other details from the source account. Folder names can help, but they are not proof that the contents are current.
Also look at the key itself. HighLevel’s current Custom Values settings guide notes that changing the display name of a Custom Value does not change its key. An old-looking key can therefore still point to the new correct value, while a clean new label can hide a value that was never updated.
Judge the stored value and where the key is used. Do not delete something because the label looks outdated.
A copied account can bring the old Custom Values with it
This problem is especially believable in reused setups because HighLevel snapshots can include Custom Values along with workflows, funnels, calendars, forms, emails, triggers, and other configuration assets.
That is useful when the values are meant to be reusable defaults. It is risky when they contain the source company’s real phone number, booking URL, review page, email address, or brand name.
Do not turn this into a snapshot-import checklist. The broader migration or buildout job has many other dependencies. For a GoHighLevel custom values audit, the snapshot fact explains why an account that looks newly built can still resolve an old business detail in several places at once.
BrandLyft’s GoHighLevel buildout timeline covers the wider launch sequence. This page stays with the reusable-value layer and the customer-facing details it can spread.
Search workflows twice because placeholders and hard-coded text are different problems
Workflows are one of the easiest places to miss stale details because the wrong information may sit inside an action that has not fired during testing yet.
HighLevel’s current Workflow Find & Replace tool supports separate search modes for Custom Values and text. Use that distinction.
First, search for important Custom Values and confirm the workflows using them are supposed to use those keys. A workflow may still point to a generic support-email value even though that particular message needs a location-specific address.
Then search literal text for the old phone number, domain, email address, booking link, brand name, or offer name. This catches actions that bypass the reusable-value system completely.
Do not replace everything in bulk simply because a search result appears. Read the action. An old company name in a historical internal note is not the same problem as an old booking URL inside tomorrow’s appointment reminder.
Email and SMS can be correct structurally and still say the wrong thing
A workflow can trigger at the right time, use the right contact, and still send stale business information.
Check the actual Send Email and Send SMS actions that customers receive. Look at visible business names, phone numbers, support addresses, booking links, review links, offer names, and footer content. HighLevel supports Custom Values in workflows, conversations, and email templates, which is exactly why one source value can affect more than one message.
Sender details deserve a boundary check. HighLevel can use custom values in some email fields, including sender-related fields, but the actual sending domain, provider, authentication, and reply-path setup belong to the separate email-infrastructure cutover problem. Do not let a Custom Values audit become a deliverability or DNS article.
The same restraint applies to phone numbers. This article should catch a stale number printed inside a message. It does not own phone-number provisioning, call routing, SMS registration, or telephony migration.
After the edits, trigger the real workflow with a test contact. Reading the action in the builder does not prove the final message resolves the values you expected.
Pages and forms need a rendered check, not just an editor scan
HighLevel supports Custom Values across websites and funnels, and reused pages are a common place for source-account details to survive.
Search the visible copy, buttons, footer areas, confirmation content, forms, and next-step pages for the business details on your audit list. Look at the URLs behind buttons as carefully as the text on top of them.
A page can show the new business name and still send the click to an old website. The form may submit correctly while the confirmation message gives the previous phone number. A thank-you page may use a reusable value in one block and hard-coded text in the next.
Preview the page, then use the public or test path that a real customer would use. HighLevel’s current Custom Values guidance specifically documents use across websites, funnels, email campaigns, templates, workflows, and other parts of the account. The useful audit step is seeing what those placeholders resolve to outside the editor.
Booking communication can carry stale values after the calendar itself is fixed
Fixing the calendar owner or availability does not prove the surrounding message is current.
HighLevel now supports Custom Values inside calendar settings, services, rentals, appointment titles, custom meeting locations, email notifications, SMS reminders, and related booking communication. That widens the places where a reusable business detail can appear.
Review confirmation messages, reminder emails, reminder texts, custom meeting-location text, booking instructions, and any next-step page the customer sees after scheduling. If a Custom Value provides the support phone number or meeting link, test that exact path.
The current HighLevel calendar guide recommends a test booking to confirm the value displays correctly. That is the right standard here too.
One completed booking can expose a stale URL that an hour of staring at Settings never shows.
Links deserve their own pass because the text around them can look perfect
Booking links, review links, support URLs, policy pages, and offer pages can be stored as Custom Values or typed directly into assets.
Trigger Links create another layer. HighLevel lets a Trigger Link use a Custom Value as its destination URL, which can be useful when the destination changes over time. But the message still needs the actual Trigger Link if the account expects click tracking and trigger behavior. A raw Custom Value URL is not the same thing.
During cleanup, identify which links are supposed to be ordinary URLs and which ones are supposed to be Trigger Links. Then click them from the rendered email, SMS, or page.
Do not assume the new domain in the visible copy means the destination changed. The old URL can still be sitting behind a button, inside a reusable value, or inside the Trigger Link configuration.
HighLevel’s Trigger Links overview explains the difference between using a Custom Value as the changeable destination and inserting the Trigger Link itself into the message.
Fix the source when one wrong value is feeding several assets
The best cleanup is often smaller than it first appears.
If five customer-facing assets all use the same Custom Value and the stored value is wrong, correct the source. Do not hard-code the new phone number into five separate messages just to make today’s tests pass. That removes the reason the reusable value existed.
The opposite case needs a different fix. If four assets use the correct Custom Value and one old page contains hard-coded text, changing the source will not touch that page. Patch the bypass and, when it makes sense, replace the literal detail with the same reusable value used elsewhere.
Do not centralize everything merely because Custom Values exist. Some information belongs to Location fields, Contact fields, User fields, Company fields, calendar data, or another source that changes with context. HighLevel’s current variable picker separates these sources for a reason.
The audit should leave fewer ambiguous sources, not a giant Custom Values folder trying to own every piece of data in the account.
Be careful when deleting or renaming values during cleanup
Old-looking values can be tempting to remove as soon as the obvious assets stop using them.
Take one more pass first. Search for the key in workflows and the other customer-facing areas that matter to the business. Check any less frequent automation, campaign, calendar, page, or other customer-facing asset that may still depend on it.
HighLevel lets admins edit, organize, move, and delete Custom Values. It also documents that changing the Custom Value name does not change the existing key. That makes renaming useful for organization, but it can also confuse an audit if the team assumes the label and token always match.
If a value has been replaced, document which source now owns that information. Otherwise the next person can recreate the same stale-data problem six months later because nobody knows whether Support URL, Booking URL, Main Calendar, or Review Link is the current one.
Finish the audit by testing what the customer actually receives
A clean Custom Values screen is not the finish line.
Use the account the way a customer does. Trigger an important lead workflow. Send an email and SMS. Submit a form. Book an appointment. Open the confirmation page. Click the booking, review, support, and policy links that matter. Check the name, number, email, address, offer, and sender details that appear along the way.
If the account uses the same value in several surfaces, test more than one of those surfaces. Support Email may resolve correctly in a workflow but still be hard-coded incorrectly in a page footer. A review link may be correct in SMS and stale in a campaign template.
Record what passed and what was changed. If one source-value correction fixed several assets, note that relationship so future updates happen in the right place.
A GoHighLevel custom values audit should leave the team knowing which stored source each repeated business detail should come from and which assets still contain one-off text that needs separate care.
Stale Custom Values do not automatically mean you need a custom build
Stale Custom Values do not automatically mean the account needs a custom build.
If the problem is an old phone number, booking URL, email address, or business name sitting in reusable values and hard-coded text, standard cleanup is usually the right layer. BrandLyft’s GoHighLevel Custom Build article owns the different situation where normal fields, workflows, integrations, or data structure no longer fit how the business operates.
Keep that line clear. Do not add custom logic because the existing account was reused badly.
If stale values are part of a larger rebuild, BrandLyft’s Revenue System Build is the broader implementation path. If the account already works but old business details keep appearing in messages, pages, calendars, or workflows, the GoHighLevel Partner service is the more direct fit.
