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.

Someone messaged me today asking how long it would take GHL Command to do a complete build from a system spec doc and approx how many tokens it would consume. She needs Voice AI, Conversational AI, chat widgets, multiple pipelines, multiple calendars, workflows… you name it. Good question! The spec doc was 31 pages written by an obvious IT specialist, a little over my head and about 3x the size of my typical client builds. So… let’s find out! I fed her spec doc into GHL Command and told it to make it happen. I am recording the whole thing, with a side by side view of Claude Code in the terminal and GHL. I also told it to use any new findings to build new features into GHL Command, so we walk away from this test with more functionality. I’ll drop the results and an edited video if we get enough interest. Drop a BUILD comment below if you want to see how it turned out!

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.