Write something
Pinned
5d •
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.
0
0
Pinned
Jul 11 •
Read/write vs. build: GHL Command and the official HighLevel MCP
HighLevel now ships an official MCP for Claude. It is free, it is genuinely good, and several of you asked where that leaves GHL Command. This post is the permanent answer. The one-line version: the official MCP reads and writes your CRM. GHL Command builds and fixes it. They stack fine together. The side-by-side, verified against HighLevel's own docs: • Build, edit, and publish workflows: official MCP, no. GHL Command, yes, the full builder. • Deep workflow cloning with every internal ID remapped: official, no. GHL Command, yes. • The silent-failure audit, catching actions that point at deleted stages and fields, which GHL skips with no error: official, no. GHL Command, yes. • Funnels and landing pages: official, no. GHL Command, yes, and recently proven live. • Forms: official reads them only. GHL Command builds them, fields, logic, auto-responder. • Pipelines: official lists them. GHL Command creates and edits them. • Whole-account provisioning: official, no. GHL Command, yes. Blueprint builds a client sub-account from one intake. • Setup: the official MCP wins here, one-click OAuth. Ours is a token plus a one-time Firebase step, and that extra setup is exactly what powers the builders. • Cost: the official MCP is included with your GHL plan. GHL Command is $97 a month for unlimited sub-accounts, with a free read-only tier that includes the audit. Why the difference exists: the public API has no write access to workflows, funnels, or forms, and never has. The official MCP is built on the public API, so it inherits that ceiling. GHL Command works the same internal routes GHL's own builders use, which is harder to maintain and worth it, because building is the part that eats your week. If you only need Claude to read and write your CRM, use the official MCP. It is excellent and free. If you want Claude to actually build and fix your automations, funnels, forms, and whole client accounts, that is GHL Command, and today it is the only thing that does it. And if you want to see what "we maintain the hard part" looks like in practice, the Green Doesn't Mean Working course in the classroom walks a real bug from customer email to shipped fix in one day.
Pinned
Jun 2 •
Start here — Welcome to GHL Command
Welcome in. You're a founding member, 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, 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: - The GHL Command tool (your license) at the founding rate of $97/mo, locked as long as you stay subscribed. - This community: the build-in-public room, the prompts and templates, and me answering questions. - Every new tool we ship, automatically, at no extra cost while you're a member. Billing lives in your account, not here. You can manage or cancel anytime. If you cancel, the license 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
21h •
Pick One Number for Every Account
Command note: an account with ten dashboards and no owner metric is not measured, it is decorated. Every sub-account you run should have exactly one number that answers "is this working this week." Everything else is diagnostics you only open when that number moves. Pick it from what the client actually sells: • Local service: booked appointments that showed • Coach or consultant: qualified calls held • Product or ecom: first-time orders • Retainer client: leads answered inside 15 minutes Rules that keep the number honest: • It counts an outcome, not an action. Sends and opens are not it. • One number per account. Two numbers means no number. • It has to be readable inside GHL without a spreadsheet. Do it now: 1) Ask the client what they would count if they could only count one thing. 2) Find where that event already lives: a pipeline stage, an appointment status, an order. 3) Make the CRM record it every time, not sometimes. Fix the gap before you trust the number. 4) Write the number and this week's value at the top of your account notes. 5) Report it the same way every week, good or bad. The point is not the reporting. It is that one number tells you which workflow to fix next. Ten charts tell you to schedule a meeting about it. If you cannot name the account's one number, you are running the account blind.
0
0
2d •
Find the Custom Fields Nobody Fills
Command note: every account collects custom fields nobody ever fills in. They pile up from snapshots, old campaigns, and forms that got rebuilt. Then your automations reference fields that are empty on almost every contact, and your AI reads them as signal when they are noise. The prompt I run: "List every custom field in this sub-account, then tell me how many contacts have a value in each one. Sort by lowest fill rate." What comes back: • Fields inherited from a snapshot that were never wired to a form • Duplicates: two fields collecting the same answer under different names • Fields with real data that no workflow actually uses Clean it up today: 1) Run it on your messiest sub-account, usually the oldest one. 2) Anything under 5% fill, check whether a form or workflow writes to it. If nothing does, it is dead. 3) Before you delete, search the field name across your workflows and forms. Removing a live field breaks things silently. 4) Merge duplicates into the one your forms actually write to. 5) Save the list of what you cut and why, so the next person does not add it back. A short field list makes every automation easier to write and every AI answer easier to trust. Empty fields are not harmless. They are noise your automations are reading as signal.
0
0
1-30 of 89
Suggested communities
Powered by