Command note: "Done" is a feeling. A read-back is a fact. Before you tell a client something is finished, pull it back out of the system and read it as if you had never seen it. Same screen they will see, same data they will touch. What a read-back catches: • A field that saved blank because the label changed • A step that exists in the builder but never fires • A message that reads fine in the editor and wrong in the inbox • A setting you changed on the wrong sub-account Do it now: 1) Write the finish line — one sentence: "When this works, X happens for Y." 2) Re-open the thing fresh — a new tab, not the one you built it in. 3) Walk it as the end user — submit it, click it, receive it. 4) Compare to the finish line — word for word, not by feel. 5) Note what you checked — one line in the account notes, so the next person does not redo it. Building tells you what you intended. Reading it back tells you what you shipped.

Welcome in. You're here early, and I don't take that lightly. Quick on what this is. GHL Command is the room for agency owners who use AI to actually run their operations, not just market with it. I run a healthcare agency on this exact stack every day: the GHL Command MCP, Claude, Slack and a small team of named agents. This is where I build it in public, drop the prompts and templates I'm using, and answer your GoHighLevel questions directly. What your membership includes, plainly: - GHL Command: all 250 tools for $97 a month, with every fix and update included while you're a member. - This community: the build-in-public room, the prompts and templates, and me answering questions. - A first look at new products, including beta testing before their public release. Billing runs through Stripe, not Skool. To change or cancel, reply to your welcome email and I'll take care of it. If you cancel, the tool and your spot here wind down together. Simple. Your first 20 minutes: 1. Open the Start Here course in the Classroom. It gets GHL Command installed and gives you a real win in about 10 minutes (point Claude at one of your sub-accounts and have it tell you what's silently broken). 2. Come back and introduce yourself below: who you are, how many sub-accounts you run, and the one GHL task you're most tired of doing by hand. 3. Read the first war story I pinned: "The $5,000 pipeline ID mistake every GHL agency owner makes." It's the bug that started all of this. That's it. Get the tool running, get your first win, then tell me what you want me to build next. This thing grows around what you actually need. Jerry

I noticed that you are using examples of clinics. Is your system HIPAA compliant? I have not done anything with any client with patients involved because I am not sure about this. My understanding is that even collecting information from patient leads could be affected by HIPAA compliance. I know it is possible. I just don't know how to do it, so I thought I'd ask you how you were ensuring compliance.

Command note: a merge field that fails doesn't error. It just prints. We sent a campaign where the greeting rendered as "Hi ," for part of the list. No bounce, no warning, nothing in the logs. The field was simply empty on those contacts, and the message went out anyway looking like a template somebody forgot to finish. Three ways this goes wrong: • The token is misspelled or points to a field that was renamed, so it renders as raw text • The field exists but is blank on a chunk of the list, so you get the punctuation with no name • The field only fills from one form, and half the audience never saw that form What we do now before anything goes out: 1) Check fill rate first — count how many contacts in that exact audience have the field populated 2) Write a fallback for every token, and assume the fallback will be the one that prints 3) Send the real message to a test contact with the field deliberately empty, then read it 4) If the fallback reads badly, rewrite the sentence so the field isn't load-bearing 5) Publish only to the segment where the data actually exists The fix is almost never better data. It's usually a sentence that works either way. A merge field is a promise about your data. Don't make one you can't keep.

Command note: A pipeline stage no deal ever reaches is a promise your process isn't keeping. Stages are instructions. If nothing ever lands in one, either the trigger that moves deals there is broken or the stage describes a step nobody actually does. What a dead stage usually means: • The automation that should move deals in was never connected • The stage was copied from a template and never fit how you sell • Deals skip it because the real work happens off-pipeline Try this prompt in Claude with the GHL Command MCP connected: "List every pipeline in this sub-account. For each stage, count the open opportunities in it and the date of the most recent one moved in. Flag any stage with zero deals, or none moved in during the last 60 days. Read-only, don't change anything." Do it now: 1) Run the prompt on one sub-account — start with the pipeline that matters most 2) Mark each flagged stage: broken trigger, wrong stage, or dead step 3) Fix the trigger or delete the stage by hand in GHL, one change at a time 4) Re-run next month and compare The prompt only reads. Every fix stays a human decision. A stage nobody reaches isn't a stage. It's a wish.