@elitedcs/ghl-mcp 3.62.0 → 3.63.0

package/guide/guide.html

@@ -4,7 +4,7 @@
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>GHL Command — User Guide</title>
-<!-- guides-hash: 95cbfe7f949954d7 -->
+<!-- guides-hash: 728bb13cf74de388 -->
 <style>
 :root{
   --bg:#F2F4F6; --surface:#FFFFFF; --ink:#1C2833; --muted:#5B6B78; --line:#DDE3E8;
@@ -169,40 +169,267 @@ main{max-width:1180px}
 <main>
   <div class="lead">
     <h1>What do you want to get done?</h1>
-    <p>Every guide is a job, in plain English: find it below, copy a prompt, paste it to Claude. This copy ships inside GHL Command and updates with the product — cards marked "Coming in an update" arrive automatically.</p>
+    <p>Every guide is a job, in plain English: find it below, copy a prompt, paste it to Claude. Every prompt marked "Proven live" was run against a real GoHighLevel account before it shipped. This copy updates with the product, so cards marked "Coming in an update" arrive automatically.</p>
   </div>
   <div class="catsec"><h2>Getting set up</h2><div class="cards"><a class="card pub" href="#g-install-ghl-command" data-k="install connect setup start windows mac workflow builder browser login step 2 full version"><h3>Install GHL Command</h3><p>One install, two short steps, whether you are on the Free plan or the full license. Nothing left to add later.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~6 minutes</span><span class="open">Read below &#8595;</span></div></a>
-<button class="card locked" type="button" data-k="switch subaccount location client account change" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Switch between client accounts. Coming in a product update."><h3>Switch between client accounts</h3><p>Point Claude at any of your sub-accounts by name, and confirm which one is active.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">seconds</span><span class="applabel">Coming in an update</span></div></button></div></div>
-<div class="catsec"><h2>Contacts and leads</h2><div class="cards"><a class="card pub" href="#g-count-and-report-contacts" data-k="count how many contacts report number leads week month total added"><h3>Count and report your contacts</h3><p>Ask for a number, get the real number, with the date range printed next to it.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~10 seconds</span><span class="open">Read below &#8595;</span></div></a>
-<button class="card locked" type="button" data-k="list find contacts export spreadsheet csv excel search" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Find and list contacts. Coming in a product update."><h3>Find and list contacts</h3><p>Pull a clean list into a spreadsheet you can open in Excel or Google Sheets.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~1 min</span><span class="applabel">Coming in an update</span></div></button>
-<button class="card locked" type="button" data-k="bulk tag untag update clean duplicates many contacts smart lists" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Bulk tag and clean up. Coming in a product update."><h3>Bulk tag and clean up</h3><p>Tag, untag, or update hundreds of contacts in one instruction.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~2 min</span><span class="applabel">Coming in an update</span></div></button>
-<button class="card locked" type="button" data-k="weekly report account snapshot health summary" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Weekly account report. Coming in a product update."><h3>Weekly account report</h3><p>One ask, a full snapshot of the account's week: leads, appointments, pipeline moves.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~1 min</span><span class="applabel">Coming in an update</span></div></button></div></div>
-<div class="catsec"><h2>Automations</h2><div class="cards"><a class="card pub" href="#g-build-nurture-sequence" data-k="nurture sequence drip texts emails follow up workflow build"><h3>Build a nurture sequence</h3><p>A follow-up machine that texts, emails, waits, and stops the second someone replies.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~15 minutes</span><span class="open">Read below &#8595;</span></div></a>
-<button class="card locked" type="button" data-k="exit workflow remove tag note notify replied" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Add an exit workflow. Coming in a product update."><h3>Add an exit workflow</h3><p>Cleanly pull people out of a sequence when they reply, tag them, and get notified.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 min</span><span class="applabel">Coming in an update</span></div></button>
-<button class="card locked" type="button" data-k="audit workflows broken silent failure check review existing validate" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Audit your workflows. Coming in a product update."><h3>Audit your workflows</h3><p>Find silent failures and dead ends in existing workflows before your client does.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~2 min</span><span class="applabel">Coming in an update</span></div></button>
-<button class="card locked" type="button" data-k="if else branch condition vip tag field split" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Branch on tags and fields. Coming in a product update."><h3>Branch on tags and fields</h3><p>If they are a VIP, send this. Otherwise, send that. Built correctly the first time.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 min</span><span class="applabel">Coming in an update</span></div></button></div></div>
-<div class="catsec"><h2>Pipelines and sales</h2><div class="cards"><button class="card locked" type="button" data-k="pipeline stages create new client setup opportunity" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Stand up a pipeline. Coming in a product update."><h3>Stand up a pipeline</h3><p>Stages, fields, and tags for a new client in one conversation.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 min</span><span class="applabel">Coming in an update</span></div></button>
-<button class="card locked" type="button" data-k="opportunities move deals track stuck value update" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Track and move opportunities. Coming in a product update."><h3>Track and move opportunities</h3><p>Move deals between stages, update values, and see what is stuck.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~1 min</span><span class="applabel">Coming in an update</span></div></button>
-<button class="card locked" type="button" data-k="invoices estimates payments send record coupons products" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Invoices and estimates. Coming in a product update."><h3>Invoices and estimates</h3><p>Create, send, and track invoices and estimates without opening GHL.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~3 min</span><span class="applabel">Coming in an update</span></div></button>
-<button class="card locked" type="button" data-k="documents contracts proposals signature send" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Documents and contracts. Coming in a product update."><h3>Documents and contracts</h3><p>Proposals and contracts sent for signature and tracked from Claude.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 min</span><span class="applabel">Coming in an update</span></div></button></div></div>
+<a class="card pub" href="#g-switch-between-client-accounts" data-k="switch subaccount sub-account location client account change which account wrong account"><h3>Switch between client accounts</h3><p>Point Claude at any of your sub-accounts by name, and confirm which one is active.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~10 seconds</span><span class="open">Read below &#8595;</span></div></a></div></div>
+<div class="catsec"><h2>Contacts and leads</h2><div class="cards"><a class="card pub" href="#g-bulk-tag-and-clean-up" data-k="bulk tag untag update clean duplicates many contacts segment mass"><h3>Bulk tag and clean up</h3><p>Tag, untag, or update hundreds of contacts in one instruction.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~2 minutes</span><span class="open">Read below &#8595;</span></div></a>
+<a class="card pub" href="#g-count-and-report-contacts" data-k="count how many contacts report number leads week month total added"><h3>Count and report your contacts</h3><p>Ask for a number, get the real number, with the date range printed next to it.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~10 seconds</span><span class="open">Read below &#8595;</span></div></a>
+<a class="card pub" href="#g-find-and-list-contacts" data-k="list find contacts export spreadsheet csv excel search leads who signed up"><h3>Find and list contacts</h3><p>Pull a clean list into a spreadsheet you can open in Excel or Google Sheets.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~1 minute</span><span class="open">Read below &#8595;</span></div></a>
+<a class="card pub" href="#g-weekly-account-report" data-k="weekly report account snapshot health summary how are we doing client report monday"><h3>Weekly account report</h3><p>One ask, a full snapshot of the account's week: leads, pipeline, and conversations.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~1 minute</span><span class="open">Read below &#8595;</span></div></a></div></div>
+<div class="catsec"><h2>Automations</h2><div class="cards"><a class="card pub" href="#g-add-an-exit-workflow" data-k="exit workflow remove stop replied tag note notify pull out stop texting"><h3>Add an exit workflow</h3><p>Cleanly pull people out of a sequence when they reply, tag them, and get you notified.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="open">Read below &#8595;</span></div></a>
+<a class="card pub" href="#g-audit-your-workflows" data-k="audit workflows broken silent failure check review existing validate not sending nothing happens"><h3>Audit your workflows</h3><p>Find silent failures and dead ends in existing workflows before your client does.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~2 minutes</span><span class="open">Read below &#8595;</span></div></a>
+<a class="card pub" href="#g-branch-on-tags-and-fields" data-k="if else branch condition vip tag field split two paths different message"><h3>Branch on tags and fields</h3><p>If they are a VIP, send this. Otherwise, send that. Built correctly the first time.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="open">Read below &#8595;</span></div></a>
+<a class="card pub" href="#g-build-nurture-sequence" data-k="nurture sequence drip texts emails follow up workflow build"><h3>Build a nurture sequence</h3><p>A follow-up machine that texts, emails, waits, and stops the second someone replies.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~15 minutes</span><span class="open">Read below &#8595;</span></div></a></div></div>
+<div class="catsec"><h2>Pipelines and sales</h2><div class="cards"><a class="card pub" href="#g-documents-and-contracts" data-k="documents contracts proposals signature send sign agreement esign template"><h3>Documents and contracts</h3><p>Proposals and contracts sent for signature and tracked from Claude.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="open">Read below &#8595;</span></div></a>
+<a class="card pub" href="#g-stand-up-a-pipeline" data-k="pipeline stages create new client setup opportunity sales process deal stages"><h3>Stand up a pipeline</h3><p>Stages, fields, and tags for a new client in one conversation.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="open">Read below &#8595;</span></div></a>
+<a class="card pub" href="#g-track-and-move-opportunities" data-k="opportunities deals move stage track stuck value won lost pipeline board"><h3>Track and move opportunities</h3><p>Move deals between stages, update values, and see what is stuck.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~1 minute</span><span class="open">Read below &#8595;</span></div></a>
+<button class="card locked" type="button" data-k="invoices estimates payments send record coupons products" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Invoices and estimates. Coming in a product update."><h3>Invoices and estimates</h3><p>Create, send, and track invoices and estimates without opening GHL.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~3 min</span><span class="applabel">Coming in an update</span></div></button></div></div>
 <div class="catsec"><h2>Client builds and pages</h2><div class="cards"><button class="card locked" type="button" data-k="blueprint client account build intake onboarding new complete template" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="The Blueprint: build a client account. Coming in a product update."><h3>The Blueprint: build a client account</h3><p>From intake form to a complete, reviewed account build you approve before it runs.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~1 hour</span><span class="applabel">Coming in an update</span></div></button>
 <button class="card locked" type="button" data-k="page studio compose website landing pages funnel" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Page Studio: pages and sites. Coming in a product update."><h3>Page Studio: pages and sites</h3><p>Compose landing pages and full sites that render correctly in GHL.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~20 min</span><span class="applabel">Coming in an update</span></div></button>
 <button class="card locked" type="button" data-k="clone site copy rebrand landing page existing url" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Clone and rebrand a site. Coming in a product update."><h3>Clone and rebrand a site</h3><p>Rebuild an existing page for a new client, with a rights check and a review report.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~30 min</span><span class="applabel">Coming in an update</span></div></button></div></div>
-<div class="catsec"><h2>Booking and calendars</h2><div class="cards"><button class="card locked" type="button" data-k="calendar create booking consult slots availability" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Set up a booking calendar. Coming in a product update."><h3>Set up a booking calendar</h3><p>A consult calendar with the right slots, buffers, and confirmation messages.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 min</span><span class="applabel">Coming in an update</span></div></button>
+<div class="catsec"><h2>Booking and calendars</h2><div class="cards"><a class="card pub" href="#g-set-up-a-booking-calendar" data-k="calendar create booking consult slots availability buffer appointment types schedule"><h3>Set up a booking calendar</h3><p>A consult calendar with the right slots, buffers, and the right person attached.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="open">Read below &#8595;</span></div></a>
 <button class="card locked" type="button" data-k="appointments today schedule upcoming who list" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="See and manage appointments. Coming in a product update."><h3>See and manage appointments</h3><p>Who is booked today, this week, or for a specific client, in one ask.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">seconds</span><span class="applabel">Coming in an update</span></div></button></div></div>
-<div class="catsec"><h2>Email and SMS</h2><div class="cards"><button class="card locked" type="button" data-k="send message text email contact conversation campaigns" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Send texts and emails. Coming in a product update."><h3>Send texts and emails</h3><p>Message any contact from Claude, in your voice, on the right channel.</p><div class="meta"><span class="pill full">Full license</span><span class="time">seconds</span><span class="applabel">Coming in an update</span></div></button>
-<button class="card locked" type="button" data-k="email template design create campaign builder" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Build email templates. Coming in a product update."><h3>Build email templates</h3><p>Reusable, branded templates created and edited without the GHL editor.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 min</span><span class="applabel">Coming in an update</span></div></button>
-<button class="card locked" type="button" data-k="conversations inbox read unread replies check messages" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Review your conversations. Coming in a product update."><h3>Review your conversations</h3><p>Catch up on replies and unread threads across every channel.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~1 min</span><span class="applabel">Coming in an update</span></div></button></div></div>
-<div class="catsec"><h2>Content and social</h2><div class="cards"><button class="card locked" type="button" data-k="social posts schedule planner facebook instagram queue" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Plan social posts. Coming in a product update."><h3>Plan social posts</h3><p>Queue and schedule posts across your connected social accounts.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 min</span><span class="applabel">Coming in an update</span></div></button>
-<button class="card locked" type="button" data-k="blog posts publish draft seo articles" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Publish blog posts. Coming in a product update."><h3>Publish blog posts</h3><p>Draft, format, and publish posts to your GHL blog.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 min</span><span class="applabel">Coming in an update</span></div></button>
+<div class="catsec"><h2>Email and SMS</h2><div class="cards"><a class="card pub" href="#g-build-email-templates" data-k="email template design create campaign builder reusable branded rename archive"><h3>Build email templates</h3><p>Reusable, branded templates created and edited without the GHL editor.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="open">Read below &#8595;</span></div></a>
+<a class="card pub" href="#g-review-your-conversations" data-k="conversations inbox read unread replies check messages who replied catch up missed"><h3>Review your conversations</h3><p>Catch up on replies and unread threads across every channel.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~1 minute</span><span class="open">Read below &#8595;</span></div></a>
+<a class="card pub" href="#g-send-texts-and-emails" data-k="send message text sms email contact reply conversation follow up one off"><h3>Send texts and emails</h3><p>Message any contact from Claude, in your voice, on the right channel.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~30 seconds</span><span class="open">Read below &#8595;</span></div></a></div></div>
+<div class="catsec"><h2>Content and social</h2><div class="cards"><a class="card pub" href="#g-social-posting" data-k="social posts schedule planner facebook instagram linkedin queue draft content calendar"><h3>Plan social posts</h3><p>Queue posts as drafts across your connected social accounts, ready for you to publish.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="open">Read below &#8595;</span></div></a>
+<button class="card locked" type="button" data-k="blog posts publish draft seo articles slug" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Plan and check blog posts. Coming in a product update."><h3>Plan and check blog posts</h3><p>See what is published, check a web address is free, and get the next post written ready to paste.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 min</span><span class="applabel">Coming in an update</span></div></button>
 <button class="card locked" type="button" data-k="courses memberships lessons offers community" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Courses and memberships. Coming in a product update."><h3>Courses and memberships</h3><p>Course outlines, lessons, and offers built in your membership area.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~20 min</span><span class="applabel">Coming in an update</span></div></button></div></div>
-<div class="catsec"><h2>Forms and reviews</h2><div class="cards"><button class="card locked" type="button" data-k="form create intake survey fields submissions" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Create forms and read submissions. Coming in a product update."><h3>Create forms and read submissions</h3><p>Intake forms built to spec, and submissions pulled into a clean summary.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 min</span><span class="applabel">Coming in an update</span></div></button>
-<button class="card locked" type="button" data-k="reviews reputation see ratings google respond" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Watch your reviews. Coming in a product update."><h3>Watch your reviews</h3><p>See new reviews across clients without logging into each account.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">seconds</span><span class="applabel">Coming in an update</span></div></button>
-<button class="card locked" type="button" data-k="trigger links tracking click automations" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Trigger links. Coming in a product update."><h3>Trigger links</h3><p>Create tracked links that fire automations when clicked.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~2 min</span><span class="applabel">Coming in an update</span></div></button></div></div>
-<div class="catsec"><h2>Account admin</h2><div class="cards"><button class="card locked" type="button" data-k="custom fields objects records associations create" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Custom fields and objects. Coming in a product update."><h3>Custom fields and objects</h3><p>The fields and records your niche needs, created correctly the first time.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 min</span><span class="applabel">Coming in an update</span></div></button>
+<div class="catsec"><h2>Forms and reviews</h2><div class="cards"><a class="card pub" href="#g-trigger-links" data-k="trigger links tracking click automations tracked link who clicked interest"><h3>Trigger links</h3><p>Create tracked links that fire automations when clicked.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~2 minutes</span><span class="open">Read below &#8595;</span></div></a>
+<button class="card locked" type="button" data-k="form create intake survey fields submissions" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Create forms and read submissions. Coming in a product update."><h3>Create forms and read submissions</h3><p>Intake forms built to spec, and submissions pulled into a clean summary.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 min</span><span class="applabel">Coming in an update</span></div></button>
+<button class="card locked" type="button" data-k="reviews reputation see ratings google respond" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Watch your reviews. Coming in a product update."><h3>Watch your reviews</h3><p>See new reviews across clients without logging into each account.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">seconds</span><span class="applabel">Coming in an update</span></div></button></div></div>
+<div class="catsec"><h2>Account admin</h2><div class="cards"><a class="card pub" href="#g-custom-fields-and-objects" data-k="custom fields objects records associations create field dropdown date field niche"><h3>Custom fields and objects</h3><p>The fields and records your niche needs, created correctly the first time.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="open">Read below &#8595;</span></div></a>
 <button class="card locked" type="button" data-k="users phone numbers media export snapshots webhooks admin settings" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Account admin basics. Coming in a product update."><h3>Account admin basics</h3><p>Users, phone numbers, media, and account exports without hunting through menus.</p><div class="meta"><span class="pill full">Full license</span><span class="time">seconds</span><span class="applabel">Coming in an update</span></div></button></div></div>
   <div class="noresults" id="noresults"><p><b>No guides match that yet.</b> Try a different word, like "contacts" or "workflow".</p></div>
   
+<section class="gview" id="g-add-an-exit-workflow">
+  <h1 class="gtitle serif">Add an exit workflow</h1>
+  <p class="gpromise">Cleanly pull people out of a sequence when they reply, tag them, and get you notified.</p>
+  <div class="gmeta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A small four-step workflow that runs the moment someone replies: it takes them out of the nurture, tags them, writes a note on their record, and pings you.</li>
+<li>No more robot follow-ups landing after a real conversation has started. That single embarrassment is what this exists to prevent.</li>
+<li>A pattern you can attach to any sequence you already have, not just new ones.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Add an exit workflow to my New Lead Nurture so people drop out when they reply.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Anyone who books a consult should stop getting the follow-up texts.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Build the exit workflow for the sequence we just made.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">Build an exit workflow in my [Radiance Med Spa] account called &quot;[New Lead Nurture] Exit&quot;.
+Trigger: when a contact replies to us on any channel while they are in [New Lead Nurture].
+Then, in this order: (1) remove them from [New Lead Nurture], (2) add a note on their record saying they replied and when, (3) tag them [warm-lead], (4) notify [me] so a human picks it up.
+Before you build: confirm the exact workflow you are removing them from by looking it up in my account, and confirm the real user you are notifying. If either one does not exist, stop and tell me instead of guessing.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The last paragraph is doing the heavy lifting. Exit workflows that point at the wrong thing fail in total silence.</p>
+</div>
+<div class="gsec"><h2>What Claude builds</h2>
+<div class="flow">
+<div class="fnode"><span class="tag wait">They reply on any channel</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Remove from the nurture</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Note on the contact record: what they said, when</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Tag: warm-lead</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Notify you, so a human takes it from here</span>then</div>
+</div>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude looks up the real workflow you want people removed from, and the real person to notify. Not names, actual records.</li>
+<li>It shows you the four steps for approval.</li>
+<li>It builds the exit workflow, then hands you the link to open it in GHL.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Build the main sequence first, then the exit workflow. The exit needs to point at a workflow that already exists.</li>
+<li>Four steps is the whole pattern: remove, note, tag, notify. Longer exits are where they start breaking.</li>
+<li>The notification has to name a real user in that account. GHL used to accept &quot;everyone&quot; and no longer does. Claude picks the user up from the account, so this is handled, but it is why an exit built by hand often fails.</li>
+<li>Needs the full license.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;People still got the next text after replying.&quot;</td><td>The main sequence also needs stop-on-reply switched on. The exit removes them; stop-on-reply prevents the message already in flight. Ask for both.</td></tr><tr><td>&quot;I deleted the nurture and the exit workflow broke.&quot;</td><td>They are a pair. If you delete or rebuild one, say &quot;update the exit workflow to match&quot; so it does not point at something gone.</td></tr><tr><td>&quot;The notification never arrived.&quot;</td><td>It was pointed at a user who is no longer in the account. Run an audit and Claude will find it.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>build-nurture-sequence</li>
+<li>audit-your-workflows</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-audit-your-workflows">
+  <h1 class="gtitle serif">Audit your workflows</h1>
+  <p class="gpromise">Find silent failures and dead ends in existing workflows before your client does.</p>
+  <div class="gmeta"><span class="pill free">Free plan</span><span class="time">~2 minutes</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>Every workflow in the account checked for the one thing GHL never tells you about: an action pointing at something that no longer exists.</li>
+<li>A ranked list of what is broken, what could not be checked, and what looks fine.</li>
+<li>The reason this matters: when a GHL action points at a deleted pipeline, stage, field, user, or form, that action fails without a word, and every action after it in that workflow can stop too.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Audit all the workflows in this account.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Is anything in my automations pointing at something that no longer exists?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Check this one workflow before I turn it on.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">Audit every workflow in my [Radiance Med Spa] account for silent failures.
+For each problem: name the workflow, the action inside it, what the action is pointing at that no longer exists, and what would actually happen to a contact who hits it.
+Sort the list worst first, where worst means it stops the rest of the workflow.
+Then tell me which ones you can fix safely and which ones need a decision from me. Do not change anything yet.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The last line keeps this a read-only check. Nothing moves until you say so.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude opens every workflow in the account and follows each action to whatever it references.</li>
+<li>Anything pointing at a missing pipeline, stage, custom field, user, form, calendar, survey, or other workflow gets flagged.</li>
+<li>Where it cannot be certain, it says &quot;could not verify&quot; instead of calling something broken. No false alarms.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>This is the first thing to run on an account you have just inherited. It finds in two minutes what takes an afternoon of clicking.</li>
+<li>The most common find by far is a workflow built before somebody deleted a pipeline stage. It looks perfectly healthy in GHL.</li>
+<li>Run it again after any big cleanup. Deleting things is exactly what creates these.</li>
+<li>This works fully on the Free plan. Fixing what it finds needs the full license.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The workflow looks fine in GHL, so I ignored the warning.&quot;</td><td>GHL shows the action. It does not show that what the action points at is gone. That is the whole problem.</td></tr><tr><td>&quot;It said could not verify, so I assumed broken.&quot;</td><td>Could not verify means exactly that. Ask Claude to open that one workflow and explain what it saw.</td></tr><tr><td>&quot;I fixed it by rebuilding the workflow.&quot;</td><td>Do not rebuild. Ask Claude to update the broken action in place, so triggers and history stay attached.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>build-nurture-sequence</li>
+<li>add-an-exit-workflow</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-branch-on-tags-and-fields">
+  <h1 class="gtitle serif">Branch on tags and fields</h1>
+  <p class="gpromise">If they are a VIP, send this. Otherwise, send that. Built correctly the first time.</p>
+  <div class="gmeta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A workflow that splits: one path for people who match, another for everyone else.</li>
+<li>Both paths written out and connected properly, which is the part that is fiddly to do by hand and easy to get subtly wrong.</li>
+<li>A condition based on what you actually know about the person: a tag, a custom field, where they came from.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>If they are tagged vip, send the VIP text. Otherwise send the standard one.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Split the follow-up: existing patients get one message, brand new leads get another.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Add a branch for anyone whose treatment interest field is Botox.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">In my [Radiance Med Spa] account, build a workflow called &quot;[New Lead Split]&quot;.
+Trigger: when the tag [new-lead] is added.
+Then branch on this question: does the contact have the tag [vip]?
+If yes: text &quot;[Hi {{first name}}, it is Dana. Since you are one of our regulars I saved you a priority slot this week. Want it?]&quot;
+If no: text &quot;[Hi {{first name}}, thanks for reaching out to Radiance. Want me to grab you a free consult this week?]&quot;
+Before you build: confirm both tags exist in my account, and show me the two paths side by side so I can check the split reads correctly. Build nothing until I approve.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. Ask for the two paths side by side every time. Reading them next to each other is how you catch a branch that is the wrong way round.</p>
+</div>
+<div class="gsec"><h2>What Claude builds</h2>
+<div class="flow">
+<div class="fnode"><span class="tag wait">Tag new-lead is added</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Question: are they tagged vip?</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag sms">Text</span>VIP path, priority slot</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag sms">Text</span>standard path, free consult offer</div>
+</div>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude checks the tag or field you want to branch on actually exists in the account.</li>
+<li>It shows you both paths, written out, before anything is built.</li>
+<li>It builds the branch with both sides properly connected, then gives you the link to review in GHL.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Use branches sparingly. Two clean linear sequences with a tag deciding which one someone enters are usually easier to read and to fix later than one workflow with branches inside branches.</li>
+<li>Branch on tags where you can. Tags are simple and visible. Custom-field conditions work too, but you have to keep the field filled in.</li>
+<li>A branch with nothing on one side is legal and almost always a mistake. Say what happens to the people who do not match.</li>
+<li>Needs the full license.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;Everyone went down the same path.&quot;</td><td>The tag is added later in the same workflow than the branch that checks it. Move the check after the tag, or trigger on the tag itself.</td></tr><tr><td>&quot;The branch does nothing at all.&quot;</td><td>The tag in the condition does not exist in that account, usually a typo or a different spelling. Run an audit.</td></tr><tr><td>&quot;It got complicated fast.&quot;</td><td>Stop nesting. Split into two workflows and let a tag decide which one people enter.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>build-nurture-sequence</li>
+<li>audit-your-workflows</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-build-email-templates">
+  <h1 class="gtitle serif">Build email templates</h1>
+  <p class="gpromise">Reusable, branded templates created and edited without the GHL editor.</p>
+  <div class="gmeta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A branded email template saved in the account, ready to drop into any workflow or campaign.</li>
+<li>Editing, renaming, and archiving templates from the chat, including the housekeeping the GHL editor makes tedious.</li>
+<li>Text templates too, for the short messages you send over and over.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Create an email template called Consult Confirmation.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>List the email templates in this account.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Rename the old welcome template and archive it.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">In my [MCP Testing] account, create an email template called &quot;[Consult Confirmation]&quot;.
+Subject: &quot;[You are booked, here is what happens next]&quot;. Three short paragraphs: confirm the appointment with the date and time merged in, say what to bring and where to park, and one line on how to reach a human if plans change. One button to [my booking link]. Warm, plain, no hype.
+Use the contact's first name at the top, and use merge fields for the appointment date and time so it works for everybody.
+When it saves, list the templates in the account so I can see it landed, and tell me exactly where in GHL I will find it.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. Ask for the list at the end. It proves the template is where you will look for it, not just that a save came back happy.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude writes the email and saves it as a template in the account.</li>
+<li>It lists the templates so you can confirm it is there under the name you chose.</li>
+<li>Edits are in place: &quot;change the second paragraph&quot; keeps the same template rather than creating a second copy.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Templates and workflow emails are different things. A template is a reusable asset. A workflow email is written into a specific step. Ask for a template when several sequences will use the same email.</li>
+<li>Claude writes the email in your voice if you give it one. Paste an email you have actually sent and say &quot;write like this&quot;.</li>
+<li>Actually sending a campaign to a list is done in GHL. What you get here is the writing, the template, and the housekeeping.</li>
+<li>Archiving beats deleting. An archived template stops cluttering the list without breaking anything that referenced it.</li>
+<li>Needs the full license.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The email arrived as one wall of text.&quot;</td><td>Say how you want it structured: short paragraphs, one button. Claude will lay it out.</td></tr><tr><td>&quot;The name did not merge.&quot;</td><td>The merge field name has to match this account's setup. Ask Claude to check the field exists before saving.</td></tr><tr><td>&quot;I have four versions of the same template.&quot;</td><td>Say &quot;update the existing template&quot; instead of describing it again. Repeating the description creates a new one.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>build-nurture-sequence</li>
+<li>send-texts-and-emails</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
 <section class="gview" id="g-build-nurture-sequence">
   <h1 class="gtitle serif">Build a nurture sequence</h1>
   <p class="gpromise">A follow-up machine that texts, emails, waits, and stops the second someone replies.</p>
@@ -271,6 +498,56 @@ Before you build anything: show me every message written out for my approval, an
   <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
 </section>
 
+<section class="gview" id="g-bulk-tag-and-clean-up">
+  <h1 class="gtitle serif">Bulk tag and clean up</h1>
+  <p class="gpromise">Tag, untag, or update hundreds of contacts in one instruction.</p>
+  <div class="gmeta"><span class="pill full">Full license</span><span class="time">~2 minutes</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>One instruction that tags, untags, or updates a whole group of contacts at once.</li>
+<li>A count of exactly who is about to be touched, before anything is touched.</li>
+<li>A report of what actually landed: how many succeeded, how many failed, out of how many.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Tag everyone who came in from the September ad as september-lead.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Remove the cold-lead tag from anyone who has replied to us.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Tag these twelve contacts as needs-follow-up.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">In my [Radiance Med Spa] account, find every contact tagged [website-lead] that also has [no tag of consult-booked].
+First: tell me how many there are and show me five examples, and stop there so I can approve.
+Once I say go: add the tag [needs-follow-up] to all of them, then tell me how many succeeded and how many failed.
+Do not delete anything, do not send anything, and do not change any other field.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The two safety lines matter more than the rest: Claude counts and stops before it touches anything, and the last line rules out everything you did not ask for.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude builds the group and tells you the size, with a few examples so you can spot a mistake.</li>
+<li>You approve, or you narrow it. Nothing has changed yet.</li>
+<li>Claude applies the change in batches and reports back what actually landed.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Ask for the count first, every time. It is the difference between tagging 40 people and tagging 4,000.</li>
+<li>Bulk delete is real, and it does not come back. Claude will make you confirm, and it is worth reading that message twice.</li>
+<li>Tags are the backbone of GHL automation. Tag now, and your workflows have something to trigger on later.</li>
+<li>Bulk changes need the full license. The Free plan can find and count the group, but not change it.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;It tagged more people than I meant.&quot;</td><td>Always ask for the count and the examples first. Approve after you see them, not before.</td></tr><tr><td>&quot;I asked for duplicates to be merged.&quot;</td><td>GHL does not merge from the outside. Claude can find likely duplicates and list them, then you merge in GHL.</td></tr><tr><td>&quot;The tags are not showing in GHL yet.&quot;</td><td>GHL's contact index lags a few seconds behind. The report of what succeeded is the truth; the list view catches up.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>find-and-list-contacts</li>
+<li>audit-your-workflows</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
 <section class="gview" id="g-count-and-report-contacts">
   <h1 class="gtitle serif">Count and report your contacts</h1>
   <p class="gpromise">Ask for a number, get the real number, with the date range printed next to it.</p>
@@ -320,6 +597,156 @@ Before you build anything: show me every message written out for my approval, an
   <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
 </section>
 
+<section class="gview" id="g-custom-fields-and-objects">
+  <h1 class="gtitle serif">Custom fields and objects</h1>
+  <p class="gpromise">The fields and records your niche needs, created correctly the first time.</p>
+  <div class="gmeta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>The fields this business actually needs on a contact: treatment interest, referral source, next review date, whatever the niche runs on.</li>
+<li>Custom records for the things that are not people, like a piece of equipment, a property, or a policy, and the link between those records and the contact.</li>
+<li>The field list read back to you, which is what every workflow you build afterwards depends on.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>What custom fields exist in this account?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Create a dropdown field called Treatment Interest with four options.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Add a date field for Next Review.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">In my [MCP Testing] account, first list the custom fields that already exist so we do not duplicate anything.
+Then create these on the contact record: [Treatment Interest] as a dropdown with the options [body contouring, injectables, skin, not sure]; [Referral Source] as a dropdown with [Google, Instagram, friend, walk in]; [Next Review Date] as a date.
+Read them back to me afterwards with their exact names and types, and tell me which ones I can now use as a condition inside a workflow.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. Ask for the existing list first. Half the messy GHL accounts in the world have three fields that mean the same thing.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude lists what already exists so you can see the duplicates before you make more.</li>
+<li>It creates the fields with the right types and options.</li>
+<li>It reads them back, and from then on every form, workflow, and branch you build can point at them properly.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Fields are the foundation. Build them before the forms and workflows that use them, and everything downstream stops failing silently.</li>
+<li>Dropdowns beat free text for anything you will filter on. Free text is where segmentation goes to die.</li>
+<li>Renaming a field is safe. Deleting one is not: anything pointing at it goes quiet. If a field is retired, leave it and stop using it.</li>
+<li>Custom objects are for things that are not people. Most accounts never need one, and that is fine.</li>
+<li>Needs the full license. Reading the field list is free.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;A workflow condition on my field never matches.&quot;</td><td>The field is free text and the values are spelled four different ways. Make it a dropdown and set the options.</td></tr><tr><td>&quot;I deleted a field and workflows broke.&quot;</td><td>Deleting a field kills anything referencing it, silently. Run an audit, and retire fields instead of deleting them.</td></tr><tr><td>&quot;There are three fields that mean the same thing.&quot;</td><td>List first, create second. Ask Claude which ones look like duplicates and it will tell you.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>create-forms-and-read-submissions</li>
+<li>audit-your-workflows</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-documents-and-contracts">
+  <h1 class="gtitle serif">Documents and contracts</h1>
+  <p class="gpromise">Proposals and contracts sent for signature and tracked from Claude.</p>
+  <div class="gmeta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>Your existing contract and proposal templates, listed by name, ready to send.</li>
+<li>A document sent to a named contact for signature without opening GHL.</li>
+<li>A read on what is out there: what has been sent, what is signed, what is still sitting unopened.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>List my contract templates.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Send the standard service agreement to Dana Miller.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Which contracts are still unsigned?</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">In my [Radiance Med Spa] account, list every document and contract that has gone out, with the contact it went to, the template it came from, and its current status.
+Group them: signed, sent but not signed, and anything older than [10] days with no signature.
+Do not send anything or resend anything. This is a read.
+Then tell me which ones I should chase, in order.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The unsigned pile older than ten days is where the money quietly leaks out of an agency.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude reads the documents in the account and the templates available to send.</li>
+<li>It groups them by status and names the contact on each.</li>
+<li>Sending is a separate, deliberate instruction, and it names the recipient back to you before it goes.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Build the templates in GHL. That editor handles signature fields and layout, and rebuilding that from the outside would give you a worse document.</li>
+<li>What Claude adds is everything around the template: choosing it, sending it to the right contact, and telling you what is outstanding.</li>
+<li>GHL hands documents over in modest batches, so on a busy account a full read takes a few passes. Claude will say when it is still fetching.</li>
+<li>A document sent to the wrong contact cannot be unsent. Say the full name or the email in the ask.</li>
+<li>Needs the full license.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;It sent to the wrong Dana.&quot;</td><td>Two contacts, same first name. Give the email address and Claude confirms the match before sending.</td></tr><tr><td>&quot;The template list is missing one.&quot;</td><td>It exists in a different sub-account. Confirm which account you are in first.</td></tr><tr><td>&quot;The client says the document is blank.&quot;</td><td>The template has no signature or content blocks filled in. That is fixed in the GHL template editor, then resent.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>invoices-and-estimates</li>
+<li>track-and-move-opportunities</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-find-and-list-contacts">
+  <h1 class="gtitle serif">Find and list contacts</h1>
+  <p class="gpromise">Pull a clean list into a spreadsheet you can open in Excel or Google Sheets.</p>
+  <div class="gmeta"><span class="pill free">Free plan</span><span class="time">~1 minute</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>The actual people, not a number: name, email, phone, tags, and the date they came in.</li>
+<li>A spreadsheet file you can open in Excel or Google Sheets, or a short list right in the chat.</li>
+<li>A search that looks across name, email, and phone at once, so a half-remembered detail is enough to find someone.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Show me the contacts we added this week.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Find the contact with the email dana@example.com.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>List everyone tagged new-lead and give me a spreadsheet.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">List the contacts added to my [Radiance Med Spa] account since [August 1], newest first.
+Give me a spreadsheet with these columns: first name, last name, email, phone, tags, date added.
+Show me the first ten rows in the chat so I can sanity check them before you write the file, and tell me the total number of rows you found.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The last line is what makes this trustworthy: you see the top of the list before the file is written.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude pulls the matching contacts from your account, in pages, until it has them all.</li>
+<li>It shows you the first few rows so you can confirm it found the right people.</li>
+<li>It writes the spreadsheet and tells you where the file is and how many rows it holds.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>For &quot;how many&quot;, ask for a count instead. A count is one call and one number. See the counting guide.</li>
+<li>Very large lists take longer because GHL hands them over a page at a time. Claude will say so rather than quietly stopping short.</li>
+<li>A brand-new contact can take up to half a minute to appear. If someone you just added is missing, ask again in a moment.</li>
+<li>This works fully on the Free plan.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;I got a number when I wanted the names.&quot;</td><td>Say &quot;show me&quot; or &quot;list&quot;, not &quot;how many&quot;.</td></tr><tr><td>&quot;The spreadsheet is missing a column I need.&quot;</td><td>Name the columns you want in the ask. Anything on the contact record can be a column.</td></tr><tr><td>&quot;It found a contact I did not expect.&quot;</td><td>The search looks at name, email, and phone together. Narrow it: &quot;find the contact whose email is exactly ...&quot;.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>count-and-report-contacts</li>
+<li>bulk-tag-and-clean-up</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
 <section class="gview" id="g-install-ghl-command">
   <h1 class="gtitle serif">Install GHL Command</h1>
   <p class="gpromise">One install, two short steps, whether you are on the Free plan or the full license. Nothing left to add later.</p>
@@ -354,10 +781,465 @@ Before you build anything: show me every message written out for my approval, an
 </div>
   <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
 </section>
+
+<section class="gview" id="g-review-your-conversations">
+  <h1 class="gtitle serif">Review your conversations</h1>
+  <p class="gpromise">Catch up on replies and unread threads across every channel.</p>
+  <div class="gmeta"><span class="pill free">Free plan</span><span class="time">~1 minute</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>Who has replied and not been answered, across text, email, and the rest of the inbox.</li>
+<li>The actual last message in a thread, not just a name and a timestamp.</li>
+<li>A catch-up you can do in a minute instead of scrolling the GHL inbox.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Who has replied to us and not been answered?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Show me the unread conversations in this account.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>What did Dana say in her last message?</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">In my [Radiance Med Spa] account, show me every conversation with an unanswered inbound message from the last [7] days.
+For each one: the contact name, which channel it came in on, when it arrived, and the last thing they actually said.
+Put the oldest unanswered at the top, because that is the one costing me money.
+Do not reply to anyone. This is a read.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. Oldest first is deliberate. The thread that has been waiting three days is worth more of your attention than the one from an hour ago.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude reads the account's conversations and finds the ones where they spoke last.</li>
+<li>It pulls the actual message text so you can triage without opening anything.</li>
+<li>It leaves everything untouched unless you ask it to reply or to mark something read.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>This is a read on every channel the account uses, not just text.</li>
+<li>It reads what is in GHL. A reply that went to a personal phone or an outside inbox is not in the account and cannot be found here.</li>
+<li>Reading conversations works fully on the Free plan. Replying needs the full license.</li>
+<li>Pair this with a nurture that stops on reply, and the unanswered list stays short by itself.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;It showed threads I have already handled.&quot;</td><td>You answered from your own phone, so GHL never saw the reply. Answer inside GHL and the record stays honest.</td></tr><tr><td>&quot;I only wanted texts.&quot;</td><td>Say the channel: &quot;unanswered texts only&quot;.</td></tr><tr><td>&quot;A conversation is missing.&quot;</td><td>The contact lives in a different sub-account. Confirm which account you are in first.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>send-texts-and-emails</li>
+<li>weekly-account-report</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-send-texts-and-emails">
+  <h1 class="gtitle serif">Send texts and emails</h1>
+  <p class="gpromise">Message any contact from Claude, in your voice, on the right channel.</p>
+  <div class="gmeta"><span class="pill full">Full license</span><span class="time">~30 seconds</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A single text or email to a named contact, written and sent from the chat.</li>
+<li>The message shown to you in full before it goes, with the recipient named.</li>
+<li>It lands in that contact's GHL conversation thread like any other message, so nothing is lost from the record.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Text Dana Miller that we have a 2pm slot open tomorrow.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Email Priya the parking details for her appointment.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Reply to the last message from Marc.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">Send a text from my [Radiance Med Spa] account to the contact [Dana Miller].
+The message: &quot;[Hi Dana, it is Sarah at Radiance. We had a cancellation at 2pm tomorrow if you want it. Just reply yes and it is yours.]&quot;
+Before you send: confirm the exact contact you matched, show me their phone number, and show me the message exactly as it will arrive. Then wait for me to say send.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The confirm-then-wait pattern is not optional courtesy. A sent message cannot be recalled.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude finds the contact and shows you the match, including the number or address the message would go to.</li>
+<li>It shows you the message exactly as written.</li>
+<li>It sends only when you say so, then confirms it went and where it landed in the thread.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Texting requires the sub-account to have a phone number and, in the United States and Canada, completed A2P registration. Without that, texts fail at the carrier and no tool can work around it.</li>
+<li>Sending from Claude uses the account's own number and inbox, so the client sees a normal conversation, not something from a robot.</li>
+<li>One-off messages are for one person. For a sequence to many people, build a nurture instead so replies stop it automatically.</li>
+<li>Compliance stays yours. Business hours, opt-out language, and consent are your responsibility, not the tool's.</li>
+<li>Needs the full license.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The text says sent but never arrived.&quot;</td><td>The sub-account is not fully registered for texting. Check A2P status in GHL. This is the most common cause by far.</td></tr><tr><td>&quot;It went to the wrong person.&quot;</td><td>Two contacts share a first name. Always give the full name or email and read the match Claude shows you.</td></tr><tr><td>&quot;I meant to send twenty of these.&quot;</td><td>Twenty one-off sends is a sequence in disguise. Build a nurture; it stops on reply and keeps you out of trouble.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>review-your-conversations</li>
+<li>build-nurture-sequence</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-set-up-a-booking-calendar">
+  <h1 class="gtitle serif">Set up a booking calendar</h1>
+  <p class="gpromise">A consult calendar with the right slots, buffers, and the right person attached.</p>
+  <div class="gmeta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A booking calendar with real opening hours, appointment length, and gaps between appointments.</li>
+<li>The right person attached to it, which is the step that quietly breaks calendars built in a hurry.</li>
+<li>A read-back of what actually saved, plus the next available slots so you know it is bookable.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Create a 30-minute consult calendar, weekdays 9 to 5, with a 15-minute gap between appointments.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Show me the calendars in this account.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>What slots are free on the consult calendar this week?</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">In my [MCP Testing] account, create a booking calendar called &quot;[Free Consult]&quot;.
+Appointments are [30] minutes, available [Monday to Friday, 9am to 5pm] in the account's timezone, with a [15] minute gap between appointments.
+Attach it to [me], and look up my real user record in this account rather than guessing at a name.
+When it saves, read the calendar back to me and show me the next five bookable slots so I know it is genuinely open for business.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. Asking for the next five slots at the end is the whole test. A calendar that saves but offers no slots looks perfect and books nobody.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude looks up the real user in the account so the calendar has an owner who exists.</li>
+<li>It creates the calendar with your hours, length, gaps, and notice period.</li>
+<li>It reads the calendar back and pulls the next available slots so you can see it is live.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Say who the appointments belong to. A calendar with nobody attached will happily save and then show no availability.</li>
+<li>Timezones follow the sub-account's setting. If the account is set to the wrong city, every slot is wrong. Check that first on a new client account.</li>
+<li>Round robin calendars, where several staff share the bookings, need each person listed. Name them all in the ask. On that type, a slot only opens if the calendar hours AND that person's own working hours both allow it, so a Saturday window needs somebody who works Saturdays.</li>
+<li>Two settings live in GHL's calendar screen and not here: how much notice someone must give before booking, and the confirmation and reminder messages. Set those once in GHL. If you want real control over reminder wording, ask Claude for a reminder workflow instead.</li>
+<li>Needs the full license.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The calendar exists but shows no times.&quot;</td><td>Nobody is attached to it, or the hours fall outside the account's timezone. Ask for the next five slots and Claude will show you which it is.</td></tr><tr><td>&quot;Clients are booking with no notice.&quot;</td><td>The minimum-notice setting is on GHL's calendar screen, not something Claude sets. Open the calendar in GHL and set it once.</td></tr><tr><td>&quot;Appointments are back to back.&quot;</td><td>Ask for a gap between appointments. Fifteen minutes is the usual answer for a clinic.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>see-and-manage-appointments</li>
+<li>build-nurture-sequence</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-social-posting">
+  <h1 class="gtitle serif">Plan social posts</h1>
+  <p class="gpromise">Queue posts as drafts across your connected social accounts, ready for you to publish.</p>
+  <div class="gmeta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A week or a month of posts written and loaded into the GHL Social Planner as drafts.</li>
+<li>The captions written for the business, with the accounts they are aimed at named.</li>
+<li>A list of which social accounts are actually connected, which is usually where the surprises are.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Which social accounts are connected to this client?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Write me five posts for next week and load them as drafts.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Show me what is already in the social queue.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">In my [MCP Testing] account, first list which social accounts are actually connected and which ones are healthy.
+Then write [five] posts for [Radiance Med Spa] for next week: [one patient result story, one myth we hear all the time, one behind the scenes, one offer, one question to the audience]. Write for [women 35 to 55 in Austin], warm and plain, no hype and no medical claims.
+Load all five into the Social Planner as DRAFTS only. Do not schedule them and do not publish anything.
+Then confirm back to me, one line each, that every post saved as a draft and which account it is aimed at.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. Keep the drafts-only line. Publishing is a decision a human should make with their eyes open, especially on an account that carries somebody's real name.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude checks which social accounts are connected and flags any whose connection has expired.</li>
+<li>It writes the posts and loads them into the planner as drafts.</li>
+<li>You review them in GHL, adjust anything, and publish or schedule from there.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Connections expire quietly. Instagram in particular drops its connection every so often, and the planner will happily hold posts for an account that cannot post. Ask for the health check first, every time.</li>
+<li>Review the drafts in the Social Planner itself. Asking Claude to list them back is a poor substitute: the planner mixes drafts in with everything already scheduled and orders them by the date shown on the post, so a draft made today sits below posts queued for next month.</li>
+<li>Images are not written by this. Attach them in the planner, or ask Claude to build an image separately and add it.</li>
+<li>Publishing straight from the chat is possible, and this guide deliberately does not teach it. A misfired post on a client's real page is not a mistake you can quietly fix.</li>
+<li>Needs the full license.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The posts went nowhere.&quot;</td><td>The account connection had expired. Reconnect it in GHL, then the queue drains normally.</td></tr><tr><td>&quot;The captions sound like a robot.&quot;</td><td>Give Claude two real posts from the client and say &quot;write like these&quot;. Voice comes from examples, not adjectives.</td></tr><tr><td>&quot;It posted to the wrong page.&quot;</td><td>Name the exact page or profile in the ask, and check the account list Claude prints first.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>blog-posting</li>
+<li>weekly-account-report</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-stand-up-a-pipeline">
+  <h1 class="gtitle serif">Stand up a pipeline</h1>
+  <p class="gpromise">Stages, fields, and tags for a new client in one conversation.</p>
+  <div class="gmeta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A pipeline with stages named the way this business actually sells, not GHL's defaults.</li>
+<li>The custom fields and tags the pipeline depends on, created at the same time so nothing points at a field that does not exist.</li>
+<li>The real stage IDs written down, which is what everything you build later has to reference.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Set up a pipeline for a med spa: new lead, consult booked, consult done, treatment scheduled, treated.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Add a stage called Deposit Paid between consult done and treatment scheduled.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Show me the pipelines in this account with their stages.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">In my [Radiance Med Spa] account, create a pipeline called &quot;[Patient Journey]&quot; with these stages in order: [New Lead], [Consult Booked], [Consult Completed], [Treatment Scheduled], [Treated], [Lost].
+Also create the custom fields this needs: [Consult Date] as a date, and [Quoted Value] as a number.
+When you are done, read the pipeline back to me from the account and show me the real stage names in order, so I know it saved the way I asked.
+Do not add any contacts or deals to it yet.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The read-back line is the one that matters: you are being shown what GHL actually stored, not what Claude intended to store.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude creates the pipeline and its stages in order.</li>
+<li>It creates any custom fields you asked for alongside it.</li>
+<li>It reads the whole thing back out of the account so you can see what really landed.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Name stages after what the business does, not after sales jargon. &quot;Consult Booked&quot; beats &quot;Qualified&quot; for a clinic, every time.</li>
+<li>Fewer stages is better. Six is plenty. Ten stages means nobody keeps the board clean.</li>
+<li>Keep the pipeline. When stages change, ask Claude to update the pipeline in place. Deleting and recreating gives every stage a new ID, and every workflow that referenced the old ones goes silently dead.</li>
+<li>Needs the full license.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;I recreated the pipeline and all my automations stopped.&quot;</td><td>Recreating changes every stage ID. Say &quot;update the existing pipeline&quot; instead, and Claude keeps the IDs alive.</td></tr><tr><td>&quot;A workflow that moves deals does nothing.&quot;</td><td>It is pointing at a stage that no longer exists. Run a workflow audit; this is the single most common find.</td></tr><tr><td>&quot;The stage order came out wrong.&quot;</td><td>Say the stages in order in one line and ask for the read-back. The read-back shows you the true order.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>track-and-move-opportunities</li>
+<li>audit-your-workflows</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-switch-between-client-accounts">
+  <h1 class="gtitle serif">Switch between client accounts</h1>
+  <p class="gpromise">Point Claude at any of your sub-accounts by name, and confirm which one is active.</p>
+  <div class="gmeta"><span class="pill free">Free plan</span><span class="time">~10 seconds</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>Every sub-account you can reach, listed by name, not by a string of letters and numbers.</li>
+<li>One instruction to move Claude from one client to another.</li>
+<li>A straight answer to &quot;which account am I working in right now&quot;, any time you want to check.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Which GHL account am I working in right now?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>List all the sub-accounts I can reach.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Switch to the Radiance Med Spa account.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>What it looks like</h2>
+<div class="chat"><span class="chat-cap">Your Claude conversation</span>
+<div class="msg user">Which account am I in?</div>
+<div class="msg claude">You are in <b>MCP Testing</b>. Want me to list the other sub-accounts you can reach?</div>
+<div class="msg user">Switch to Radiance Med Spa.</div>
+<div class="msg claude">Done. Active account is now <b>Radiance Med Spa</b>. Everything from here runs against that account until you switch again.</div>
+</div>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude reads the account it is pointed at and says the name back to you.</li>
+<li>When you name a different account, it swaps in that account's saved key and confirms the switch by name.</li>
+<li>If an account has no key saved yet, Claude tells you which one is missing instead of quietly working in the wrong place.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Every sub-account needs its own key saved once. The installer does this for the first account. To add another, say &quot;add my Radiance Med Spa account&quot; and Claude walks you through it.</li>
+<li>Your license covers unlimited sub-accounts. Adding another client costs nothing extra.</li>
+<li>Get in the habit of asking &quot;which account am I in&quot; before any build. It takes two seconds and it is the cheapest insurance there is.</li>
+<li>This works fully on the Free plan.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;It built something in the wrong client's account.&quot;</td><td>Always confirm the account first. Ask &quot;which account am I in&quot;, then build.</td></tr><tr><td>&quot;I switched accounts an hour ago, and now it is back on my default.&quot;</td><td>When the product updates itself in the background, the active account can fall back to your default. Ask &quot;which account am I in&quot; again before you build.</td></tr><tr><td>&quot;It says it cannot find that account.&quot;</td><td>Use the name exactly as it appears in GHL, or say &quot;list my sub-accounts&quot; and pick from the list.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>install-ghl-command</li>
+<li>weekly-account-report</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-track-and-move-opportunities">
+  <h1 class="gtitle serif">Track and move opportunities</h1>
+  <p class="gpromise">Move deals between stages, update values, and see what is stuck.</p>
+  <div class="gmeta"><span class="pill full">Full license</span><span class="time">~1 minute</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>The board read out loud: what is in every stage, what it is worth, and what has not moved in weeks.</li>
+<li>Deals moved, marked won or lost, or re-valued without opening the pipeline view.</li>
+<li>The question nobody asks often enough, answered in one line: what is stuck?</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>What is in my pipeline right now, by stage?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Move Dana Miller to Consult Booked.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Which deals have not moved in 14 days?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Mark the Miller deal won at 2400.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">Look at the [Patient Journey] pipeline in my [Radiance Med Spa] account.
+Give me: how many deals are in each stage, the total value sitting in each stage, and every deal that has not moved in [14] days with the contact name and how long it has been sitting.
+Then tell me which three deals you would chase first and why, in one sentence each.
+Do not move anything. This is a read.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. Run this Monday morning. It is a five-second read that usually pays for the month.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude reads the pipeline and groups every deal by stage.</li>
+<li>It works out what has gone quiet and how long it has been quiet for.</li>
+<li>If you asked it to move something, it confirms the exact deal and stage first, then moves it and reads the result back.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Say the contact's name and Claude finds the deal. You do not need to know a deal ID.</li>
+<li>Won and lost are a different thing from stages. A deal can sit in &quot;Treatment Scheduled&quot; and be marked won. Ask for both when you want the true picture.</li>
+<li>If a deal you expect is missing, it may live on a different pipeline in the same account. Ask &quot;which pipelines exist here&quot; first.</li>
+<li>Needs the full license. The Free plan can read the board but not move deals.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;It moved the wrong deal.&quot;</td><td>Two contacts with the same first name. Give the full name or the email, and Claude confirms the match before moving.</td></tr><tr><td>&quot;The value did not update.&quot;</td><td>Value and status are separate. Say &quot;mark it won at 2400&quot; to set both in one go.</td></tr><tr><td>&quot;Nothing shows up in the pipeline.&quot;</td><td>You are looking at a different pipeline than the deals are on. Ask Claude to list the pipelines in the account.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>stand-up-a-pipeline</li>
+<li>weekly-account-report</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-trigger-links">
+  <h1 class="gtitle serif">Trigger links</h1>
+  <p class="gpromise">Create tracked links that fire automations when clicked.</p>
+  <div class="gmeta"><span class="pill full">Full license</span><span class="time">~2 minutes</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A tracked link, created in the account and ready to drop into any text or email.</li>
+<li>A record of who clicked it, on the contact, in GHL.</li>
+<li>A hook your workflows can use: clicked the link means interested, and interested people should get a different follow-up.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Create a trigger link for the pricing page.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>List the trigger links in this account.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Tag anyone who clicks the pricing link as price-curious.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">In my [MCP Testing] account, create a trigger link called &quot;[Pricing Page]&quot; that points to [https://example.com/pricing].
+Then list the trigger links in the account, and show me exactly what I paste into a message to use it.
+Tell me plainly what happens on my side when somebody clicks it, and what I would need to build next if I want clickers tagged automatically.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. Ask for the thing you paste, in those words. It is not what most people expect. See below.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude creates the trigger link and hands you what to paste.</li>
+<li>Clicks are recorded against the contact who clicked, inside GHL.</li>
+<li>From there a workflow can act on it: tag them, notify you, or move them into a different sequence.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>What you paste is not a web address. GHL gives each trigger link a merge tag that looks like this: {{trigger_link.abc123}}. You drop that into the text or email, and GHL turns it into the tracked link, for that person, when it sends. Paste your original web address instead and you get a working link that records nothing.</li>
+<li>Because it is a merge tag, it only works inside GHL messages, emails, texts, and workflows. It is not something you can put on a printed flyer.</li>
+<li>The click is the signal. Somebody who opened your pricing page twice is worth a personal message, not the next automated text.</li>
+<li>A trigger link is per sub-account. Build one for each client rather than reusing yours.</li>
+<li>Keep the names obvious. Six links called &quot;Link 1&quot; through &quot;Link 6&quot; is a reporting problem you have given yourself.</li>
+<li>Needs the full license.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;No clicks are recorded.&quot;</td><td>The plain web address went out instead of the merge tag. Ask Claude for the exact thing to paste and use that.</td></tr><tr><td>&quot;The workflow that watches for clicks does nothing.&quot;</td><td>It points at a link that was deleted or rebuilt. Run a workflow audit.</td></tr><tr><td>&quot;Clicks are recorded but nothing happens.&quot;</td><td>Recording a click is not an automation. Ask for the workflow that acts on it.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>build-nurture-sequence</li>
+<li>create-forms-and-read-submissions</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
+
+<section class="gview" id="g-weekly-account-report">
+  <h1 class="gtitle serif">Weekly account report</h1>
+  <p class="gpromise">One ask, a full snapshot of the account's week: leads, pipeline, and conversations.</p>
+  <div class="gmeta"><span class="pill free">Free plan</span><span class="time">~1 minute</span><span class="time">Works in Claude Desktop and Claude Code</span></div>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>New leads for the week, total contacts, open and won and lost deals, and how many conversations are live in the account.</li>
+<li>Every figure labelled with the window it covers, so a week number is never mistaken for an all-time number.</li>
+<li>Anything that cannot be read is reported as unavailable, not as a zero. A zero you cannot trust is worse than no number.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Give me the account report for the last 7 days.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>How is the Radiance account doing this month?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Compare this week to last week.</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>The pro prompt</h2>
+<div class="pro"><div class="pro-head"><b>The exact ask we run on real client accounts</b><span class="pill full">Proven live</span><button class="copy" type="button">Copy</button></div><p class="pro-body">Give me a weekly report for my [Radiance Med Spa] account covering the last [7] days.
+I want: new contacts this window, total contacts all time, open deals, won deals, lost deals, and how many conversations are in the account.
+Label every number with the exact window it covers, and say &quot;unavailable&quot; for anything you cannot read rather than showing a zero.
+Then give me the three things you would look at first if this were your account.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. That last line turns a list of numbers into something you can act on Monday morning.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude reads the account: contacts, deals by status, conversations, phone numbers.</li>
+<li>It labels every figure as either &quot;in this window&quot; or &quot;all time&quot; and prints the dates.</li>
+<li>Anything it could not read comes back marked unavailable, with the reason.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Revenue and appointment totals are not in this report. GHL does not hand those over in a form we would trust, and a made-up number is worse than a missing one. For appointments, ask separately. See the appointments guide.</li>
+<li>The report runs across any sub-account you can reach. Say the client's name and Claude will point at that account first.</li>
+<li>Paste the result straight into a client email. It is written to be read by a human, not by an analyst.</li>
+<li>This works fully on the Free plan.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Where people go wrong</h2>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The new-lead number looks low.&quot;</td><td>Check the window Claude printed. Seven days from today is not the same as this calendar week. Name the dates if it matters.</td></tr><tr><td>&quot;It says conversations unavailable.&quot;</td><td>That account has messaging switched off, or the key does not reach it. Claude names the reason next to the word.</td></tr><tr><td>&quot;I wanted revenue in the report.&quot;</td><td>Ask for orders and transactions separately. Payment figures come from the payments side of the account.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>count-and-report-contacts</li>
+<li>track-and-move-opportunities</li>
+</ul>
+</div>
+  <p class="gfoot"><a class="back" href="#top">&#8593; All guides</a> &nbsp;&middot;&nbsp; Stuck? Email support@ghlcommand.com and a human answers.</p>
+</section>
 </main>
 </div>
 <footer class="foot"><div class="foot-in">
-  <span>GHL Command runs your GoHighLevel account from Claude. This guide library ships with every install, free or paid.</span>
+  <span>GHL Command runs your GoHighLevel account from Claude. This guide library ships with every install, free or paid, and grows with the product.</span>
   <a href="https://ghlcommand.com/skills/">Web version</a><a href="https://ghlcommand.com">ghlcommand.com</a>
 </div></footer>
 <div class="toast" id="toast" role="status"></div>