A naming convention for GoHighLevel sub-accounts that survives a second builder

Naming is the cheapest quality improvement available in a GoHighLevel account and the one agencies skip most reliably. It costs nothing at build time and saves days at maintenance time, which is exactly the trade humans are worst at making.

Here is the convention we apply to every kit and every build.

Workflows: number, dot, verb

01 · Capture · Instant lead response
01 · Capture · Missed call text back
02 · Nurture · 14-day ladder
02 · Nurture · Stale lead recovery
03 · Booking · Reminder 24h
03 · Booking · No-show recovery
04 · Delivery · Onboarding chase
09 · Internal · Tag housekeeping

Three properties make this work:

The number sorts. Workflows list alphabetically, so numbering gives you the lifecycle order for free. Anyone opening the list reads the account’s shape top to bottom.

The middle word groups. Capture, Nurture, Booking, Delivery, Retention, Internal. Six categories cover almost everything, and 09 · Internal at the bottom keeps the plumbing out of the way.

The last part is a verb phrase. “Instant lead response”, not “Workflow 3”. You should be able to guess what it does without opening it.

Pipelines and stages: nouns that describe a state

Stages should describe where the contact is, not how the team feels. Estimate Sent is a state. In Progress is a mood. The test: can someone else tell whether a card is in the right stage without asking? If not, rename it.

Avoid stage names that duplicate across pipelines. Two pipelines both containing Follow-Up makes every report ambiguous.

Tags: namespace them

Tags are the fastest thing to make a mess of, because everyone can create one.

src-google-ads
src-referral
stat-customer
stat-unsubscribed
seq-nurture-active
seq-nurture-suppressed

Three namespaces cover most needs: src- for where they came from, stat- for what they are, and seq- for what they are currently inside. A tag with no prefix is a tag nobody will trust in six months.

Write the taxonomy down in the account itself — a note in a custom value called 00 tag vocabulary works — because the list living only in someone’s head is how you end up with customer, Customer and client.

Custom values: prefix by domain

biz.name
biz.phone
biz.service_area
link.booking
link.review_google
link.review_facebook
copy.guarantee
ops.timezone
ops.quiet_hours_start

Dot-prefixing groups them visually in a list that has no folders. When a builder needs the booking link they type link. and see every link in the account.

Calendars and forms: audience first

Client · Consultation and Internal · Team availability read better than Consultation Calendar and Calendar 2, because the first word tells you who is meant to see it.

The rule that matters more than the convention

Be consistent, not clever. A mediocre convention applied to every asset beats an elegant one applied to sixty percent of them. If you inherit an account with a different convention, adopt theirs rather than mixing two.

Retrofitting an existing account

Renaming is safe for workflows, pipelines and calendars. It is not safe for tags referenced in workflow conditions, or for custom values referenced in templates — renaming those breaks the reference silently.

Retrofit in this order: workflows, then calendars and forms, then pipelines, then tags (updating every condition as you go), then custom values last and carefully. If the account is large enough that this sounds daunting, that is what a sub-account audit is for — the inventory comes first, then the renaming becomes mechanical.

Every kit in our catalog ships with this convention already applied, which is less about elegance and more about a second builder being useful on their first day.

The two things naming actually protects

Snapshot updates. Pushing an improved kit into a live account is a merge. Against consistently named assets it is reviewable; against Workflow 4 (copy) it is unpickable. This matters most in self-serve delivery, where updates land in customer accounts unattended — SaaS mode snapshots.

Debugging under time pressure. When a client says “someone got two texts”, the first job is finding which two workflows are involved. A grouped, prefixed list turns that into a minute. The diagnosis order itself is in GoHighLevel snapshot not loading, and the duplicate-asset case is case four.