Mockup, shared for your feedback. Every member, client, number and date on these screens is made up to show the layout; Jerry appears as host, nobody else is real. Click anything. When you have an opinion, email Jerry (drjerryrelth@gmail.com) with what works and what does not.
Home
What's happening this week
DW
JR
Dr. Jerry Relth HostStart Here · pinned
Pinned
Start here. Three steps, in order.
This is GHL Command. It's for agency owners who run GHL and want AI to actually run operations, not just write captions. I run it the same way I'm teaching it. I'd rather have Claude build the thing than click through GHL by hand, and that's the whole point of this room.
1. Install GHL Command. Six minutes. 2. Give your setup a checkup, so you find what's broken before your client does. 3. Build your first client account and post that it stood up. We keep a running thread of first wins. Yours goes there.
One ground rule for this place: specifics over hype. If something doesn't work for you, say so here. If you found a wall in GHL and a way around it, post it. This is an operator's room.
Checkup says forms are BROKEN, but I have six of them
Ran my first checkup this morning. Connection is green, most areas say working, but Forms says BROKEN. I definitely have six forms in that account. Did I do something wrong?
JRJerry· Host · 1 hour ago
Read the verdict, not the count. BROKEN means GoHighLevel rejected a read that should work, which is almost always a change on their end, not something you did. Your forms are still there. Run it again tonight; if it's still red, post the checkup here and we'll look together on Thursday's call.
74
PN
Priya NairWins · yesterday
Wins
First client account built on a call, before the call ended
New physical therapy client. Sent the intake form during the discovery call, approved the build plan while we were still talking, and the pipeline, fields, calendar and follow-up sequence were in the account before we hung up. The handoff page had two lines marked "Waiting on someone else" (text-message approval, Google sign-in) and it says so plainly. Client thought I had a team.
2911
TA
Tom AlvarezShare Your Build · 2 days ago
Share Your Build
Nine-step nurture for a med spa, stops the second they reply
Built from the "Build a nurture sequence" guide. Text, wait, email, wait, text. Separate exit flow so a reply pulls them out cleanly and tags them. Audited it before it went live and it caught one dead link the old build had been silently skipping for months. Screens below.
Attached: 2 screenshots (placeholder)
166
Start Here
Your first three moves, in order
Each step ends with something you can see working in your own account. Do the first, post it, then the next. Nothing here needs you to read the whole course first.
✓
Install GHL Command
Checked
About 6 minutes · Free plan or full license, same install
One install, two short steps. When it's done, Claude can see your GoHighLevel and you can ask it plain questions about any client account.
Done means: you asked "which account am I in?" and got the right answer back.
One command answers both questions: is everything still working, and what am I not using yet? Every area of the account is read live, right now, and you get a plain answer per area: working, broken, no access, or not switched on for your plan.
Done means: you have a checkup report for one real account and you know what's red and why.
About 1 hour · Best done on a call with the client
Send the intake form, review the brief, approve the build plan, and watch the account get built in stages: pipeline, fields, calendar, forms, follow-up. Nothing runs until you approve it, and every line on the handoff says whether it was checked.
Done means: the client does one named task in their new account, unaided, on the handoff call.
When something stands up, come back and say so. What worked, how long it took, what surprised you. The people who get the most out of this room are the ones who do the thing and then say what happened, good or broken.
Restart, checkup, what it can do, the guides, the prompts, the fixes, then the week itself. About twenty minutes, and every prompt on it copies with one click.
Each module states its promise in your language, what it writes to the account, and the checks it runs on itself. Labels here are honest: only "Available" is built.
Client Build
Available
Intake to go-live in seven stages, nothing applied before you approve it. The flagship.
Delivery Audit
In the works
Interviews you about every recurring task and ranks what to automate next.
Daily Brief
In the works
Which builds are blocked, what failed overnight, who went quiet, what needs a decision today.
Bot
Planned
A qualification and booking bot built and tested for one client.
Funnel
Planned
Landing page, form, follow-up, wired and verified on the real address.
Every project you run with Claude starts from zero unless you give it a place to remember. The Command Center is that place: one folder that says what's in flight across every client, who owns what, and what needs you. Every session reads it first and updates it last.
You don't configure anything by hand. You paste the prompt below into Claude Code and it builds the whole hub, finds your existing projects, and installs the one rule that makes every future session behave. About twenty minutes, and it's done once.
When it asks for your projects folder, tell it where your work lives. That's the only thing it needs from you.
The prompt to paste
Click the box to select it, then press ⌘C (or Ctrl+C)
Build my Command Center.
Set up one shared folder that every project reads first and updates last. It should hold: what is in flight across all my projects and who owns each piece, the one to-do list of things that need me personally, a dated log per project, and a template for describing any new build in plain English before it starts.
Then look through my projects folder (ask me where it is), register every project you find, and install the rule that makes every future session read the Command Center at the start and update it at the end.
When you are done, show me the folder and prove it works by catching me up on everything you registered.
Search by what you want, not what it's called. Type "nothing happens" and you land on the workflow audit. Type "spreadsheet" and you get the contact export. The same library ships inside your install and works offline.
Every guide has the same five parts: what you'll get, say this, the pro prompt, good to know, and where people go wrong. "Proven live" on a prompt means that exact wording was run against a real GoHighLevel account before it was published.
Prompts
Say this, get that
Every prompt here was written for a real agency and run before it was published. Copy one, paste it to Claude, change the names.
Kits, checklists, decks and prompt packs as zip files. Everything on this page is the real thing, not a placeholder.
Kits and checklists
ZIP
The second-brain kit
The memory files and operating instructions that turn a free Claude account into an operator who knows your business. Ten minutes, no code. Open setup.html inside the folder and follow the four steps.
The seven places GoHighLevel breaks without ever showing you an error, and the five-minute manual check for each. Every one comes from a real broken account.
The five copy-paste prompts from Module 01 that build your Command Center, organise your projects and set the daily hand-off habit, plus the run-order sheet. 6 files.
12 real files. Anything marked "being packaged" is described in a module lesson and will appear here when it ships. Want something that is not here? Ask for it.
Client Builds · Command OS
Your client accounts, and where each build stands
Nothing here changes an account until you approve it. Every line on a handoff says one of three things: Checked, Done but not confirmed, or Waiting on someone else. Go-live stays locked until every line is either Checked or Waiting with a named check.
Physical therapy · built Aug 23 on the discovery call · stage 6 of 7
Waiting on someone else
Intake
Brief
Approve
Build
Verify
Manual tasks
Go-live
Handoff summary
Re-checked today, 7:40 AM
What was built, and whether we could read each thing back from the account afterwards.
Built in the account
"New Patient" pipeline, 5 stagesRead back from the account. Names and order match the plan you approved.
Checked
14 intake fieldsAll present, correct types, attached to the intake form.
Checked
New-lead follow-up, 9 stepsTexts, emails and waits in the approved order. Stops the moment someone replies. Audited before publish.
Checked
"Consult 30" booking calendarThe write succeeded, but the account wouldn't let us read calendars back yet. That clears once the Google sign-in below is done, and we re-check automatically.
Done, not confirmed
Intake form on the "Book a consult" pagePage is live at the client's address and a test submission arrived as a contact.
Checked
Manual tasks (things only a person can do)
Text-message approval (A2P)Submitted Aug 23; the phone carriers approve this, usually 1 to 3 business days. The check that clears it: the Connection section of the checkup turns green for texting.
Waiting on someone else
Google Calendar sign-inThe client's front-desk lead needs to sign in once. Reminder sent yesterday. Walkthrough attached to the handoff page.
Waiting on someone else
Two staff loginsCreated and confirmed; welcome emails delivered.
Checked
Business phone numberPurchased and attached to the account.
Checked
Go-live is locked until the calendar line reads Checked. The handoff page never says "Done" while any line is "Done, not confirmed"; it says exactly which line and why.
Med spa · live since Aug 12 · last re-check this morning, all Checked
Live
Intake
Brief
Approve
Build
Verify
Manual tasks
Go-live
NC
Northgate Chiropractic
Chiropractic · intake form sent Aug 25 · stage 1 of 7
Waiting on the client
Intake
Brief
Approve
Build
Verify
Manual tasks
Go-live
What the three states mean
Checked
We built it, then read it back from the account with a separate look, and the real value is shown. This is the only state that counts as done.
Done, not confirmed
The write went through, but we couldn't read it back, and the line says why. Go-live waits until it becomes Checked.
Waiting on someone else
Outside our control: a carrier approval, a sign-in, a domain change. Each one names the check that clears it and roughly when.
What a finished handoff looks like
See a real handoff page (test build, Practice Naturals)
A real handoff from a timed test build on Jerry's own brand, kept exactly as the client would have received it. Every line carries one of the three states above.
Something stood up. Say what, how long it took, and what surprised you.
DW
RO
Renee Okafor3 days ago
Command Center stood up in 22 minutes. One paste.
Ran prompt 01 from the Prompts Pack on a Sunday morning with coffee. It found my eleven client folders, registered every one, and caught me up on all of them before I'd finished the cup. Monday felt different.
229
LK
Lena Kowalski5 days ago
The weekly account report replaced my Monday meeting
One ask per client, five clients, ten minutes. Leads, pipeline, conversations, with the date range printed next to every number. I forward it as-is. Nobody has asked for the meeting back.
JRJerry· Host
This is the win I want more of. The report only says what it actually read, so when a number looks wrong, the date range next to it tells you why. Post one of them (names blurred) in Share Your Build?
185
MB
Marcus Bell2 hours ago · from Module 01, Lesson 3
Open
Checkup says forms are BROKEN, but I have six of them
Ran my first checkup this morning. Connection is green, most areas say working, but Forms says BROKEN. Did I do something wrong?
JRJerry· Host
Read the verdict, not the count. BROKEN means GoHighLevel rejected a read that should work. Your forms are still there. Run it again tonight and bring it to Thursday if it's still red.
74
SB
Sam Brooksyesterday
Open
Can I build a client account without the Workflow Builder login?
I'd rather not sign in to the builder for every client. Does the basic build still work?
JRJerry· Host
Short answer: the front door alone can't create workflows, pipelines or funnels, so a build that skips the Workflow Builder login would come out with no automations in it. Every step that needs the login shows a manual fallback on its spec sheet, so you always know what you'd be doing by hand instead.
123
AY
Aisha Yusuf2 days ago
Answered
Nurture sequence sends to nobody: what am I missing?
Comment-triggered flow, DM goes out fine, but the text step never fires.
TATom Alvarez
Commenters have no phone number yet, so the text goes to nobody. Module 04 Lesson 3 covers this: deliver in the DM, capture the number on the landing page, then text.
96
TA
Tom Alvarez2 days ago
Nine-step nurture for a med spa, stops the second they reply
Built from the "Build a nurture sequence" guide. Text, wait, email, wait, text. Separate exit flow so a reply pulls them out cleanly and tags them. Audited before it went live and it caught one dead link the old build had been silently skipping for months.
Attached: 2 screenshots (placeholder)
166
PN
Priya Nairlast week
My handoff page for a PT client (names blurred)
Sharing because the "Done, not confirmed" line is the part that sold the client. It said exactly what we couldn't see yet and why. They trusted the rest more because of it.
Attached: 1 image (placeholder)
248
Live Calls
Office hours, build-alongs, and module lives
Bring a real account. Every call ends with something working that wasn't working at the start. Recordings land here the same day.
September 2026
Thu3
Office Hours
11:00 AM Central · 45 min · Dr. Jerry Relth · Bring a broken workflow
Agency owners who run GHL and want AI to run operations
Operators, not spectators. Names and agencies below are placeholders for the layout.
12 online (illustrative)
JR
Dr. Jerry RelthElite DCS · founder and hostHost
DW
Dana WhitfieldClearwater Clinics Marketing · FloridaFounding member
PN
Priya NairNorthstar Growth · TexasFounding member
MB
Marcus BellBell Digital · OhioMember
TA
Tom AlvarezAlvarez Media · ArizonaMember
RO
Renee OkaforOkafor & Co. · GeorgiaFounding member
LK
Lena KowalskiBright Practice Marketing · IllinoisMember
SB
Sam BrooksBrooks Growth Partners · ColoradoMember
AY
Aisha YusufYusuf Creative · New JerseyMember
CH
Chris HaleHale Health Marketing · OregonMember
EM
Elena MoreauMoreau Agency · QuebecMember
JP
Jordan ParkPark & Partners · CaliforniaMember
Design notes
Why the hub is laid out this way. React to any of these.
Same shape as Circle, our own clothes. Top bar, spaces down the left, one wide column in the middle. Members already know this layout from every other community; the cream, navy and gold make it unmistakably ours.
Spaces are grouped by what a member is doing: Start, Learn, Do, Community. The nav reads as a path, not a pile of channels.
Start Here is a stepper, not a wall of text. Three moves, each with "done means" spelled out, so a new member always knows the next click.
Client Builds lives inside the hub. The seven-stage build and the handoff summary sit next to the course that teaches them. Same three states everywhere: Checked, Done not confirmed, Waiting on someone else. No tool names, no ids.
The Guide Library is searchable by plain words, and the same 35 guides ship inside the install, so the hub and the product tell one story.
Wins first. The Wins space is the default community tab and the right rail on Home surfaces recent wins, because that's the behaviour we want more of.
Big type by default, and adjustable. The A−/A+ control in the top bar remembers your choice. Light and dark both designed.
Everything on screen is a placeholder except the module names, guide titles, layer names and Jerry's own words. Member names, clients, counts and dates are invented for the layout.
Questions for Paul: does the Do group earn its own place in the nav, or should Client Builds sit under Learn? Is the right rail on Home useful or noise?