Pinned
19d •
Claude Said Charge More. I Said No.
The biggest GHL Command upgrade yet is almost here, and it won't be $97. It's called Command OS, and it's built for agency owners who are done being the bottleneck: - The Cockpit: every client on one screen, a step-by-step account build, and a work queue of what's waiting on you. It runs today on Command OS licenses. - In the next release, now in testing: workflow audits with fix buttons, and a Secret Shopper that tests a client's lead flow like a real prospect. - Coming later: a brain for each client, and campaign templates. When Command OS opens to new members, it sells at its own price, well above $97. So does Command Pro, the version for solo owners. Here's the part my Business Council hates: if you're subscribed to GHL Command at $97 on the day Command OS opens, you get Command OS for that same $97, for as long as you stay subscribed. Lurking here, or on the free read-only version? This is your window. One honest filter: you need GoHighLevel's $297/mo plan or above, because GHL Command needs the API access that plan includes. If you build client accounts yourself, you know the week. You close a client, then do the math on your calendar and realize you sold more of yourself than you have available. The list of what's waiting lives in your head, and only you can finish it. In my own experience, a small account takes me about 6 hours by hand. A med spa, 10 to 12 hours minimum. On October 14, GHL Command built a med spa account in about 19 minutes of Claude working time: a 7-stage pipeline, a calendar, a form, 9 workflows and the message templates. Blueprint writes the build plan first and stops for your OK before it builds anything. The workflows come in as drafts, so nothing fires on a client until you switch it on. That build is in the $97 plan you'd be buying today. ”I've already set it up, I'm using it and it works perfectly." Andres G., agency owner Why $97? My Business Council, the AI advisors in the Claude skills I run my business on, told me on October 14 to charge more for the top tier. I agreed. But our founding rate promises every update included, so $97 members don't pay that price. I gave away free care for years as a chiropractor. Old habits die hard.
Pinned
Aug 12 •
Say "open the user guide" and the whole library opens
Every install of GHL Command now carries the guide library inside the product. Free or paid, same library. Say this to Claude: open the user guide It opens in your browser as a single page that works offline. Searchable job cards, plain-English guides, and copy-paste prompts with a Copy button on each one. Three moves to try it: 1) Say "open the user guide." 2) Type count in the search box. 3) Hit Copy on the prompt, paste it to Claude, and check the answer against your own account. That is the same on the free tier. Nothing there is held back for paid. Not every card has its guide written yet, and I would rather tell you that than let you find it. The ones that are written carry a "Proven live" mark, and that mark means something specific: the prompt was executed against a real account before we published it. It is enforced by the build, not by good intentions. Change a prompt without proving it live again and the release fails. The rest read "Coming in an update" and arrive on a normal restart. Nothing to reinstall, nothing to download, and no date I am going to promise you and then miss. There is also a new lesson in Start Here: "Get a verified answer in 10 seconds." It walks the whole thing end to end, using a real question a member got a bad answer to, and the three prompt rules that would have prevented it. Already installed? Fully quit Claude once and reopen it. Mac: Cmd+Q. Windows: right-click the tray icon and quit. On Claude Code: /mcp reconnect. Not installed yet? Some of the guides are open to everyone at ghlcommand.com/skills/. Read those first and decide from there. Tell me which guide you opened first.
Pinned
Jun 2 •
Start here — Welcome to GHL Command
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's free in here, plainly: - The Classroom, including the course that gets you a real win in about 15 minutes. - The war stories and prompts I post most days. Run them on your own account. - Monday Build Hour, live every week. Anyone can watch, members get the chair. What costs money is the tool itself. All 250 tools, $97/mo, every sub-account, every update included while you're a member. Seven days for $7 if you'd rather drive it before you decide: ghlcommand.com. Billing runs through Stripe, not Skool. To change or cancel, reply to your welcome email and I'll take care of it. One honest filter: you need GoHighLevel's $297/mo plan or above, because GHL Command needs the API access that plan includes. Your first 20 minutes: 1. Open Start Here in the Classroom. It gets GHL Command installed and gives you a real win in about 15 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. Put Monday Build Hour on your calendar. Bring the thing from step 2 and we'll work on it live. That third answer is the one I actually read. Every Monday I build whatever the most of you are tired of doing by hand. Jerry
5h •
Find the Conversations Nobody Answered
Command note: A lead who wrote in and never heard back is the most expensive record in your account. Most agencies audit what the automations send. Almost nobody audits what came in and went unanswered. Those threads are warm, and they are invisible until someone goes looking. Where they hide: • Inbound texts that arrived after hours or between workflow steps • Replies to automated messages that nobody reads • Chat widget and form follow-ups that landed in a thread with no owner • Conversations where the last message is from the contact Prompt to run today (read-only): "Search recent conversations for this sub-account. List every thread where the last message is inbound and nothing has been sent back. Group by channel and by age: under 2 days, 3 to 7 days, older than a week. For each group, show the contact's tags and who owns the contact. Do not send or change anything." Do it now: 1) Run the prompt for one sub-account — start with your busiest. 2) Read the oldest group first — those are the real misses. 3) Reply by hand to the ones still worth saving — a human sentence beats a template. 4) Find the pattern — same channel, same hour, same missing owner. 5) Fix the cause once — an owner rule, an alert, or an after-hours reply. Claude only reads the threads. The replies, and the judgment about which are worth sending, stay with you. An unanswered message is a decision someone made by accident.
0
0
6d •
Name Why Nothing Arrived
Command note: "Nothing happened" is not a test result. "Nothing happened because the test lead has no phone" is. Built Today: the latest Workflow Audit Pro release (3.92.2) changes how a failed check reads. When a test lead goes into a workflow and nothing arrives, the heading now names the cause instead of just saying nothing arrived. A text step skipped because the test lead has no phone is called out as exactly that. A failed step is reported as failed, not as "the workflows ran." The takeaway for your own QA: • A silent test teaches you nothing • "Did not run" and "ran and failed" are different problems • The cause belongs in the heading, not buried in a log Do it now on one live workflow: 1) Create a test lead with every channel filled in: phone, email, name. 2) Push it through and write down what each step did: sent, skipped, or failed. 3) For every skip, write the reason in one plain sentence. 4) Fix the test lead first, then the workflow, in that order. Half of "broken automation" is a test record that was never set up to receive anything. A test that can't say why it failed isn't a test yet.
1-30 of 182
Suggested communities
Powered by