What actually breaks when you run an agency on GoHighLevel — and how to fix it. Operator notes from the team building GHL Command, the AI that runs your GHL agency from Claude.
One Goal Event per workflow, any-of criteria, three choices for contacts who never meet it. Where to place it so a booked lead stops getting nurture texts, and when an exit workflow is the better tool.
Read →
Snapshot first, clean it into a master, choose transfer, eject or export, move the numbers and A2P before anything is deleted, hand over access, and delete last inside the 24-hour undo window.
Read →
A tag is an event that can start a workflow. A Smart List is a saved, dynamic view with no trigger of its own. Events on tags, state on fields, views on Smart Lists, plus the quiet ways each one breaks.
Read →
The prompt is the easy part. One job per bot, channels and the primary bot, a small knowledge base, message limits and sleep, handover and stop rules, the workflows already texting the same contact, then Off to Suggestive to Auto-Pilot.
Read →
Every layer of a GoHighLevel account points at the layer under it. Snapshot at creation, access, custom values, A2P and email domain early, integrations, structure, and workflows last, so nothing gets built twice.
Read →
A PIT is static, shown once, and works until someone rotates it. Agency versus sub-account tokens, the fewest scopes that work, the two rotation buttons and when to press each, and a simple policy for who should hold the keys.
Read →
The reminder that went out three hours early and the contact stuck for nine days come from different settings. Past-date handling, condition waits that are already true, missing timeouts, Time Window, timezone, and how to prove which one from the logs.
Read →
One answer per sub-account, or one answer per contact. That question decides where every piece of snapshot data belongs. Why custom values arrive still holding the last client's details, what Update Custom Value really changes, and the day-one check after every load.
Read →
One toggle decides whether a contact can run the same sequence twice, and it cannot restart someone who is still active. When re-entry is right, the setups where it double-texts people, and the guardrails that make either choice safe.
Read →
Only one of the five bills per sub-account on its price page. Three of the others bill per sub-account without saying so. The billing unit behind each tool, published list rates, and the arithmetic at 5, 15 and 40 sub-accounts.
Read →
It looks fine, and GoHighLevel has no opinion about whether it is. Six passes in thirty minutes, ordered so the things that can reach a real client contact today get read first: access and outstanding tokens, what is published, A2P per number, dead IDs, entry points, baseline.
Read →
Your Private Integration Token cannot build a workflow, and no scope will fix that: HighLevel documents a single workflow route and it is a read. What the second login actually hands over, how long it lasts, and the five questions to ask before you give it to a vendor.
Read →
Two connector subscriptions at list price before anything GHL-specific gets built. A line by line teardown from published vendor prices: the tier cliff that moves on volume rather than locations, and the work no connector can reach.
Read →
Every branch you add doubles what you have to test, and GHL creates a None path you cannot delete. When branching earns its place, the three actions that beat it, and the five-point audit to run before a real lead hits it.
Read →
GoHighLevel is built around one sub-account at a time, and above about fifteen clients the switching becomes the job. What portfolio operation actually requires: credentials, rate limits, cross-account reads, and the write that has to know which account it is in.
Read →
Most A2P denials are not about the campaign form. They are about your website copy, your legal name, and whether a reviewer can reach your opt-in page. The denial codes, what each one means, and the pass to run before you submit.
Read →
57 native triggers sounds like abundance. Most agencies fire about a dozen. Here is the real map of GHL trigger coverage, the gaps, and how to know your true coverage before you build.
Read →
A GoHighLevel workflow can read Published and green while one stale ID quietly kills an action, or every action after it. Here is the mechanism, and how to catch it.
Read →
AI is a force multiplier on some parts of a GoHighLevel workflow build and a liability on others. Here is the honest split, and the one step you never delegate.
Read →
The per-account fee is only the line item you can see. Here is the full bill: the stack tax, usage metering, tier cliffs, and the leverage you leave on the table.
Read →
A published GHL workflow can show green and do nothing from step three down. Here is the bug GHL hides, and how to catch it first.
Read →
Per-account pricing punishes the exact thing you are working for: growth. Here is the math, and a flat alternative.
Read →
A loaded snapshot can look perfect and still be broken three steps down. The failure modes to expect, and the pre-trust audit to run before a real lead hits the account.
Read →
A snapshot copies everything, good and rotten, and breaks every cross-reference on the way in. Here is the clean way to onboard.
Read →GHL Command audits workflows for silent failures, builds pipelines from a sentence, and operates every sub-account from one place. Flat $97/mo, every account included.
See how it works