Command note: every unassigned record is a decision nobody made. Ownership is the quietest failure in a CRM. Nothing errors. The lead just sits there while everyone assumes someone else has it. Run this read on one sub-account: "List every contact created in the last 90 days with no assigned user, and every open opportunity with no owner. Group them by source and by pipeline stage, and show me the oldest ten of each." What it usually surfaces: • Form leads that never got routed because the assignment step depends on a tag that stopped firing • Opportunities created by hand, where nobody set an owner • Whole sources — one ad set, one landing page — where nothing has ever been assigned • Deals parked in a middle stage with no name attached and no activity for weeks Do this today: 1) Run the read on one account and change nothing yet 2) Sort by source, not by date — an unowned pattern beats an unowned record 3) Take the single source producing the most orphans and find the assignment step that should have fired 4) Fix that one route first, then work the existing backlog by hand 5) Add a fallback rule: if nothing matches, assign to a named person, never to nobody The backlog is the symptom. The missing route is the problem. An unassigned lead is not waiting. It is already gone.

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.