@elitedcs/ghl-mcp 3.78.1 → 3.80.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: 2c4ea9b2d39b9c6c -->
+<!-- guides-hash: d7139518cd7d5f00 -->
 <style>
 /* Deliberately light in every environment, including a dark-mode OS. This is a
    reference document people read at length, print, and save to PDF, and a page
@@ -226,12 +226,12 @@ body.app.reading #indexview{display:none}
   <p class="eyebrow">GHL Command</p>
   <h1>What do you want to get done?</h1>
   <p class="sub">Every guide is a job, in plain English: open one, copy a prompt, paste it to Claude. A job is not a button, so one guide usually puts a dozen of GHL Command's tools to work at once. Every prompt marked "Proven live" was run against a real GoHighLevel account before it shipped.</p>
-  <div class="badges"><span class="badge on">32 guides</span><span class="badge">10 categories</span><span class="badge">Updates with the product</span></div>
+  <div class="badges"><span class="badge on">41 guides</span><span class="badge">10 categories</span><span class="badge">Updates with the product</span></div>
 </div></section>
 <div class="shell">
 <main>
   <nav class="catnav" aria-label="Guide categories"><a href="#cat-getting-set-up">Getting set up</a><a href="#cat-contacts-and-leads">Contacts and leads</a><a href="#cat-automations">Automations</a><a href="#cat-pipelines-and-sales">Pipelines and sales</a><a href="#cat-client-builds-and-pages">Client builds and pages</a><a href="#cat-booking-and-calendars">Booking and calendars</a><a href="#cat-email-and-sms">Email and SMS</a><a href="#cat-content-and-social">Content and social</a><a href="#cat-forms-and-reviews">Forms and reviews</a><a href="#cat-account-admin">Account admin</a></nav>
-  <div class="catsec" id="cat-getting-set-up"><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">Open guide &#8594;</span></div></a>
+  <div class="catsec" id="cat-getting-set-up"><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 desktop app claude code terminal api access which claude"><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">Open guide &#8594;</span></div></a>
 <a class="card pub" href="#g-run-a-checkup" data-k="checkup check up health is it working am i using it all broken what am i missing audit the tool ghl update broke review my setup everything working"><h3>Give your setup a checkup</h3><p>One command answers both questions: is everything still working, and what am I not using yet?</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~1 minute</span><span class="open">Open guide &#8594;</span></div></a>
 <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">Open guide &#8594;</span></div></a></div></div>
 <div class="catsec" id="cat-contacts-and-leads"><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 smart list saved list view"><h3>Bulk tag and clean up</h3><p>Tag, untag, or update hundreds of contacts in one instruction, then save the group as a list.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~2 minutes</span><span class="open">Open guide &#8594;</span></div></a>
@@ -243,30 +243,36 @@ body.app.reading #indexview{display:none}
 <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">Open guide &#8594;</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">Open guide &#8594;</span></div></a>
 <a class="card pub" href="#g-build-nurture-sequence" data-k="nurture sequence drip texts emails follow up workflow build quiet hours sending window contact hours"><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">Open guide &#8594;</span></div></a>
+<a class="card pub" href="#g-missed-call-text-back" data-k="missed call text back missed call text back voicemail no answer phone rings out call back reception after hours lost calls"><h3>Text back every missed call</h3><p>The phone rings out, a text goes back within seconds, and the caller is still yours.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="open">Open guide &#8594;</span></div></a>
 <a class="card pub" href="#g-send-data-to-other-apps" data-k="webhook zapier make integromat slack google sheets api send data integration notify push connect n8n other app"><h3>Send GHL data to another app</h3><p>Push contacts into Slack, Sheets, Zapier, Make or your own software the moment something happens in GHL.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~2 minutes</span><span class="open">Open guide &#8594;</span></div></a>
+<a class="card pub" href="#g-speed-to-lead" data-k="speed to lead instant reply new lead respond fast five minutes first response lead response time form submission auto reply text back a lead"><h3>Answer a new lead in seconds</h3><p>The text goes out the moment the form lands, the deal card appears, and a real person gets the task.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="open">Open guide &#8594;</span></div></a>
+<a class="card pub" href="#g-win-back-a-cold-list" data-k="win back winback reactivation database reactivation cold list dead leads old leads dormant wake up the list re-engage"><h3>Win back a cold list</h3><p>Wake up the contacts a client already paid for, over thirty days, without burning the list.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~15 minutes</span><span class="open">Open guide &#8594;</span></div></a>
 <a class="card pub" href="#g-workflows-that-will-not-save" data-k="cannot save will not save invalid uuid action validation failed step id legacy snapshot day days wait unit notification recipient 400 rejected edit workflow parked mid-sequence"><h3>When a workflow runs fine but will not save</h3><p>Understand the error that names steps you never touched, and fix it without dropping anyone mid-sequence.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~3 minutes</span><span class="open">Open guide &#8594;</span></div></a></div></div>
-<div class="catsec" id="cat-pipelines-and-sales"><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">Open guide &#8594;</span></div></a>
+<div class="catsec" id="cat-pipelines-and-sales"><h2>Pipelines and sales</h2><div class="cards"><a class="card pub" href="#g-confirm-a-booking-and-move-the-deal" data-k="booked confirm booking move the deal pipeline stage stop the nurture appointment booked consult booked opportunity stage"><h3>Confirm a booking and move the deal</h3><p>They book, the chasing stops, the deal moves up the pipeline, and the confirmation goes out.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="open">Open guide &#8594;</span></div></a>
+<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">Open guide &#8594;</span></div></a>
 <a class="card pub" href="#g-invoices-and-payments" data-k="invoice bill billing payment paid product price coupon promo code discount transactions orders revenue estimate"><h3>Bill a client and see what you were paid</h3><p>Products, invoices, coupons, and the money reads, without opening the billing screen.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="open">Open guide &#8594;</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">Open guide &#8594;</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">Open guide &#8594;</span></div></a></div></div>
-<div class="catsec" id="cat-client-builds-and-pages"><h2>Client builds and pages</h2><div class="cards"><a class="card pub" href="#g-build-a-funnel-from-a-template" data-k="funnel template landing page website client funnel brand designed gohighlevel templates build a funnel rebrand a funnel"><h3>Build a client funnel from a real GoHighLevel template</h3><p>Search the 900+ designed funnels GoHighLevel already ships, install the one that fits your client, and have it arrive in their brand.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="open">Open guide &#8594;</span></div></a>
+<div class="catsec" id="cat-client-builds-and-pages"><h2>Client builds and pages</h2><div class="cards"><a class="card pub" href="#g-blueprint-build-a-client-account" data-k="blueprint client account build intake onboarding new client complete template from scratch"><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="open">Open guide &#8594;</span></div></a>
+<a class="card pub" href="#g-build-a-funnel-from-a-template" data-k="funnel template landing page website client funnel brand designed gohighlevel templates build a funnel rebrand a funnel"><h3>Build a client funnel from a real GoHighLevel template</h3><p>Search the 900+ designed funnels GoHighLevel already ships, install the one that fits your client, and have it arrive in their brand.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="open">Open guide &#8594;</span></div></a>
 <a class="card pub" href="#g-clone-and-rebrand-a-site" data-k="clone site copy rebrand landing page existing url duplicate make one like this mirror"><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 minutes</span><span class="open">Open guide &#8594;</span></div></a>
-<a class="card pub" href="#g-snapshots-and-reusing-a-build" data-k="snapshot template reuse clone account new client share link import rollout onboarding"><h3>Reuse a build across client accounts</h3><p>Find your snapshots, share one, and know exactly what does not travel with it.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="open">Open guide &#8594;</span></div></a>
-<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></div></div>
-<div class="catsec" id="cat-booking-and-calendars"><h2>Booking and calendars</h2><div class="cards"><a class="card pub" href="#g-see-and-manage-appointments" data-k="appointments today schedule upcoming who is booked list no show cancel reschedule diary"><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">~10 seconds</span><span class="open">Open guide &#8594;</span></div></a>
+<a class="card pub" href="#g-page-studio-pages-and-sites" data-k="page studio compose website landing page funnel build page site sections hero"><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 minutes</span><span class="open">Open guide &#8594;</span></div></a>
+<a class="card pub" href="#g-snapshots-and-reusing-a-build" data-k="snapshot template reuse clone account new client share link import rollout onboarding"><h3>Reuse a build across client accounts</h3><p>Find your snapshots, share one, and know exactly what does not travel with it.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="open">Open guide &#8594;</span></div></a></div></div>
+<div class="catsec" id="cat-booking-and-calendars"><h2>Booking and calendars</h2><div class="cards"><a class="card pub" href="#g-appointment-reminders" data-k="reminder appointment reminder day before 2 hours before confirm appointment reduce no shows booking reminder text reminder"><h3>Remind people about their appointment</h3><p>A reminder the day before and two hours ahead, timed off the booking itself rather than off the tag.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="open">Open guide &#8594;</span></div></a>
+<a class="card pub" href="#g-rescue-a-no-show" data-k="no show no-show missed appointment did not turn up rebook reschedule empty chair cancellation recover a booking"><h3>Rescue a no-show</h3><p>The appointment is missed, the rebook offer goes out the same hour, and somebody is told to ring them.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="open">Open guide &#8594;</span></div></a>
+<a class="card pub" href="#g-see-and-manage-appointments" data-k="appointments today schedule upcoming who is booked list no show cancel reschedule diary"><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">~10 seconds</span><span class="open">Open guide &#8594;</span></div></a>
 <a class="card pub" href="#g-set-up-a-booking-calendar" data-k="calendar create booking consult slots availability buffer appointment types schedule daily limit notice same day"><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">Open guide &#8594;</span></div></a></div></div>
 <div class="catsec" id="cat-email-and-sms"><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">Open guide &#8594;</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">Open guide &#8594;</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">Open guide &#8594;</span></div></a></div></div>
 <div class="catsec" id="cat-content-and-social"><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">Open guide &#8594;</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" id="cat-forms-and-reviews"><h2>Forms and reviews</h2><div class="cards"><a class="card pub" href="#g-create-forms-and-read-submissions" data-k="form create intake survey fields submissions responses questions who filled in"><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 minutes</span><span class="open">Open guide &#8594;</span></div></a>
 <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">Open guide &#8594;</span></div></a>
 <a class="card pub" href="#g-watch-your-reviews" data-k="reviews reputation ratings google stars new review negative feedback review link"><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">~30 seconds</span><span class="open">Open guide &#8594;</span></div></a></div></div>
 <div class="catsec" id="cat-account-admin"><h2>Account admin</h2><div class="cards"><a class="card pub" href="#g-account-admin-basics" data-k="users phone numbers media export snapshot admin settings who has access compare offboarding offboard a client client is leaving exit package handoff who owns the domain asset ownership transfer an account cancel a client rotate keys"><h3>Account admin basics</h3><p>Users, phone numbers, exports, and the whole exit package the day a client leaves.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~1 minute</span><span class="open">Open guide &#8594;</span></div></a>
-<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">Open guide &#8594;</span></div></a></div></div>
+<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">Open guide &#8594;</span></div></a>
+<a class="card pub" href="#g-take-over-an-inherited-account" data-k="inherited took over taken over previous agency someone else built new client account what is in this account audit an account clean up handover"><h3>Take over an account someone else built</h3><p>Find out what is in there, what is actually running, and what is quietly broken, before you touch anything.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~20 minutes</span><span class="open">Open guide &#8594;</span></div></a></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>
 </main>
 </div>
@@ -429,7 +435,7 @@ Before you build: confirm the exact workflow you are removing them from by looki
 <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>A notification aimed at one person has to name a real user in that account. Aim it at somebody and leave the recipient blank and it saves, runs, and notifies nobody, which is why an exit built by hand often looks fine and is not. Notifying everyone is a different shape and is fine. Claude picks the user up from the account, so this is handled for you.</li>
 <li>Needs the full license.</li>
 </ul>
 </div>
@@ -512,6 +518,80 @@ Do not change anything. This is a read.</p></div>
   </main></div>
 </section>
 
+<section class="gpage" id="g-appointment-reminders">
+  <div class="hero"><div class="hero-in">
+    <p class="eyebrow">GHL Command User Guide</p>
+    <h1>Remind people about their appointment</h1>
+    <p class="sub">A reminder the day before and two hours ahead, timed off the booking itself rather than off the tag.</p>
+    <div class="badges"><span class="badge on">Full license</span><span class="badge">~10 minutes</span><span class="badge">Booking and calendars</span></div>
+  </div></div>
+  <div class="shell"><main class="gview">
+  <a class="back" href="#top">&#8592; All guides</a>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A reminder the day before and another two hours out, both counted from the appointment time, not from when the workflow started.</li>
+<li>Fewer empty chairs, which is the cheapest revenue in the whole account.</li>
+<li>Messages that carry the time, the address and a way to move the booking, so a reminder does not create a phone call.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Set up appointment reminders on my client's consult calendar.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Remind people the day before and again two hours ahead.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>We are getting too many no-shows. Start with reminders.</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 appointment reminder workflow in my [Radiance Med Spa] account.
+Trigger: an appointment is booked on the [Consult] calendar.
+Then: wait until [24 hours before] the appointment and send a text and an email; wait until [2 hours before] the appointment and send one short text.
+Every message must carry the appointment date and time from the booking itself, the address, and one line on how to move it if they need to.
+Write them for [someone who booked a week ago and has half forgotten], warm and plain, and keep the two-hour text to one line.
+Before you build: confirm the [Consult] calendar exists and scope the trigger to it. Use waits that count back from the appointment time, not fixed delays after the booking, and tell me if that is not possible rather than substituting a fixed wait.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The last sentence matters more than it reads: a fixed delay after booking sends the day-before reminder at whatever time they happened to book, which for a booking made three weeks out is a reminder three weeks early.</p>
+</div>
+<div class="gsec"><h2>What Claude builds</h2>
+<div class="flow">
+<div class="fnode"><span class="tag wait">Appointment booked on the Consult calendar</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Wait until 24 hours before the appointment</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Text and email: date, time, address, how to move it</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Wait until 2 hours before the appointment</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">One short text</span>then</div>
+</div>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude confirms the calendar and ties the trigger to it.</li>
+<li>It uses appointment-relative waits, so the reminders track the booking rather than the enrolment.</li>
+<li>It writes the messages with the real booking fields in them and shows you first.</li>
+<li>It builds as a draft; you publish it.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Two reminders is the sweet spot. One is not enough for a booking made a fortnight ahead, and three starts to feel like nagging.</li>
+<li>Put the address in the day-before message. A surprising share of no-shows are people who could not find you.</li>
+<li>Give them a way to move it. A rescheduled appointment is worth far more than a silent no-show, and people will only move it if you make it easy.</li>
+<li>Pair it with a no-show rescue. Reminders reduce misses; they never eliminate them.</li>
+<li>Same rule as every appointment trigger: scope it to one calendar.</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 reminder arrived three weeks early.&quot;</td><td>Fixed delays were used instead of appointment-relative waits. Rebuild the waits to count back from the appointment.</td></tr><tr><td>&quot;It reminded people about the wrong appointment type.&quot;</td><td>The trigger was not scoped to a calendar.</td></tr><tr><td>&quot;They got a reminder after they cancelled.&quot;</td><td>Add an exit so cancellations drop out of the sequence.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>rescue-a-no-show</li>
+<li>set-up-a-booking-calendar</li>
+<li>see-and-manage-appointments</li>
+</ul>
+</div>
+  <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
+  </main></div>
+</section>
+
 <section class="gpage" id="g-audit-your-workflows">
   <div class="hero"><div class="hero-in">
     <p class="eyebrow">GHL Command User Guide</p>
@@ -568,6 +648,68 @@ Then tell me which ones you can fix safely and which ones need a decision from m
   </main></div>
 </section>
 
+<section class="gpage" id="g-blueprint-build-a-client-account">
+  <div class="hero"><div class="hero-in">
+    <p class="eyebrow">GHL Command User Guide</p>
+    <h1>The Blueprint: build a client account</h1>
+    <p class="sub">From intake form to a complete, reviewed account build you approve before it runs.</p>
+    <div class="badges"><span class="badge on">Full license</span><span class="badge">~1 hour</span><span class="badge">Client builds and pages</span></div>
+  </div></div>
+  <div class="shell"><main class="gview">
+  <a class="back" href="#top">&#8592; All guides</a>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>One intake form your new client fills in, and a complete build plan for their account written from their answers.</li>
+<li>A two-part checklist: everything GHL Command builds for you, and the short list only you can do, in order.</li>
+<li>A hard stop before the build. You read the plan, you change what you want, and not one pipeline, field, message or workflow is created until you approve it. The one thing written before that gate is the intake form itself, because your client cannot answer a form that does not exist yet.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Run the Blueprint for a new client.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Build my Blueprint from the intake this client just submitted.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Show me the plan first. Do not build anything yet.</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">Run the GHL Command Blueprint for a new client.
+The business: [Radiance Med Spa], a [med spa] in [Austin, Texas]. What they sell: [body contouring and injectables]. Their main goal for the next 90 days: [fill the consult calendar].
+Install the intake form in my [MCP Testing] account, give me the link to send them, and once their answers are in, build the plan from those answers.
+Show me the full plan before anything is created: pipeline and stages, custom fields, tags, calendar, form, funnel, the emails and texts written out, and every workflow. Mark clearly which items you will build and which ones I have to do myself in GHL.
+Build nothing until I say approved.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The last line is the gate. The Blueprint is designed to stop there and wait for a human.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude installs the intake form in the account and gives you the link to send the client.</li>
+<li>When their answers land, it turns them into a build plan: pipeline, fields, tags, calendar, form, funnel, messages, workflows. Every message written out in full. The answers arrive as a <b>contact</b> in the account, tagged <code>blueprint-intake</code>, carrying every question as a field on that contact. That is where Claude reads them from.</li>
+<li>You read it and change anything in plain English. Then you approve, and only then does it start building. Before your approval the plan is a dry run: it resolves every reference and reports what it would do, and writes none of it.</li>
+<li>It builds in order, checks each piece exists after it creates it, and hands you the manual checklist for the parts that need a human in GHL.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Triggers get scoped to the thing you actually meant. An appointment trigger can be tied to one calendar, so a caregiver interview does not start the family consultation sequence. A reply trigger can be narrowed to a tag or to whether the reply was a yes or a no, instead of firing on every inbound message. Missed calls can be caught by call outcome, and failed phone-number checks by validation state. Say which one you mean in plain English and the plan carries it through.</li>
+<li>If a workflow step moves a deal to a new stage, the plan makes it find the deal first. That pairing is checked before the build runs, because a stage move on its own saves cleanly and then does nothing at all.</li>
+<li>The manual list is short but real: connecting a payment provider, phone and A2P registration, connecting social accounts, and domain settings. Those need a human with account access, and no tool can honestly do them for you.</li>
+<li><b>If you are told there are no submissions, the answers are not lost.</b> GoHighLevel does not report submissions for forms created outside its own editor, which is every intake form this installs, so the tool that reads submissions will say there are none even after your client has filled it in. The answers are on the contact tagged <code>blueprint-intake</code>. Say &quot;read the intake from the contact&quot; and Claude will pull it from there with the ordinary contact tools and carry on into the plan.</li>
+<li>Run it on a fresh sub-account, or one you are happy to have built into. It creates a lot. On an account that has been built before, it refuses to quietly compose a second, different plan. That refusal is deliberate: it is what stops you ending up with duplicate pipelines and duplicate workflows.</li>
+<li>The build plan is worth keeping. It is the document you walk your client through on the kickoff call.</li>
+<li>Budget an hour end to end, most of it your review time. The building itself is minutes.</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 built into the wrong client's account.&quot;</td><td>Confirm the account before you approve. Ask &quot;which account am I in&quot; and say the account name inside the prompt.</td></tr><tr><td>&quot;I approved without reading the messages.&quot;</td><td>The messages are the client's voice going out to their patients. Read them. Editing takes minutes; a bad send costs a relationship.</td></tr><tr><td>&quot;Some workflows are not live.&quot;</td><td>Built is not published. Blueprint leaves things reviewable on purpose. Publish them yourself once you have read them.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>stand-up-a-pipeline</li>
+<li>page-studio-pages-and-sites</li>
+</ul>
+</div>
+  <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
+  </main></div>
+</section>
+
 <section class="gpage" id="g-branch-on-tags-and-fields">
   <div class="hero"><div class="hero-in">
     <p class="eyebrow">GHL Command User Guide</p>
@@ -973,6 +1115,80 @@ When you are done, give me the review list of everything still belonging to the
   </main></div>
 </section>
 
+<section class="gpage" id="g-confirm-a-booking-and-move-the-deal">
+  <div class="hero"><div class="hero-in">
+    <p class="eyebrow">GHL Command User Guide</p>
+    <h1>Confirm a booking and move the deal</h1>
+    <p class="sub">They book, the chasing stops, the deal moves up the pipeline, and the confirmation goes out.</p>
+    <div class="badges"><span class="badge on">Full license</span><span class="badge">~10 minutes</span><span class="badge">Pipelines and sales</span></div>
+  </div></div>
+  <div class="shell"><main class="gview">
+  <a class="back" href="#top">&#8592; All guides</a>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>The follow-up sequences switched off the instant somebody books, so nobody gets chased for a thing they have already done.</li>
+<li>The deal card moved to the booked stage, so the client's pipeline reflects reality without anyone dragging cards.</li>
+<li>A confirmation text and email, and the team told.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>When someone books, stop the follow-ups and move their deal.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Our pipeline is always out of date. Fix it when they book.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Build the booking confirmation workflow.</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 a booking confirmation workflow in my [Radiance Med Spa] account.
+Trigger: an appointment is booked on the [Consult] calendar.
+Then, in this order: remove them from [Speed to Lead], [Lead Nurture] and [Win-back] so no more chasing goes out; tag them [consult-booked]; find their existing deal and move it to stage [Consult Booked] on [the main pipeline]; notify [me]; and send a confirmation text and email with the date, time and address.
+Before you build: look up the real calendar, the real workflows you are removing them from, and the real pipeline and stage. If the deal move cannot find an existing deal for the contact, say so rather than building a step that silently does nothing. Stop and show me the plan first.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The line about finding the deal first is doing real work: a stage move on its own saves cleanly, runs, and changes nothing, because there was no card to move.</p>
+</div>
+<div class="gsec"><h2>What Claude builds</h2>
+<div class="flow">
+<div class="fnode"><span class="tag wait">Appointment booked on the Consult calendar</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Remove from Speed to Lead, Lead Nurture and Win-back</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Tag: consult-booked</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Find their deal, then move it to Consult Booked</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Notify the team</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Confirmation text and email: date, time, address</span>then</div>
+</div>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude looks up every workflow you are removing them from by name, in the account, and tells you if one does not exist.</li>
+<li>It pairs the stage move with a find step, so the move has something to act on.</li>
+<li>It shows you the plan and the confirmation messages before building.</li>
+<li>It builds as a draft; you publish it.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>This is the piece that makes the rest trustworthy. Speed to lead and nurture sequences are only safe to run if something reliably switches them off.</li>
+<li>Name every sequence they should be removed from. Missing one is how a booked customer keeps getting &quot;are you still interested&quot;.</li>
+<li>A stage move without a find step is the quietest failure in GoHighLevel. It looks built, it runs, nothing moves.</li>
+<li>Keep the confirmation short and factual. The persuasion is over; they said yes.</li>
+<li>If the client also books by phone, the front desk needs to create the appointment in GoHighLevel or none of this fires.</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 deal never moved.&quot;</td><td>The move had no find step, or the stage does not exist. Ask Claude to check both and rebuild.</td></tr><tr><td>&quot;They booked and still got chased.&quot;</td><td>One of the sequences was not in the removal list. Name them all.</td></tr><tr><td>&quot;Nothing fires for phone bookings.&quot;</td><td>Those appointments are not being created in GoHighLevel. That is a front desk habit, not a workflow problem.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>track-and-move-opportunities</li>
+<li>add-an-exit-workflow</li>
+<li>appointment-reminders</li>
+</ul>
+</div>
+  <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
+  </main></div>
+</section>
+
 <section class="gpage" id="g-count-and-report-contacts">
   <div class="hero"><div class="hero-in">
     <p class="eyebrow">GHL Command User Guide</p>
@@ -1202,7 +1418,7 @@ Then tell me which ones I should chase, in order.</p></div>
 </div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
-<li>invoices-and-estimates</li>
+<li>invoices-and-payments</li>
 <li>track-and-move-opportunities</li>
 </ul>
 </div>
@@ -1274,7 +1490,14 @@ Show me the first ten rows in the chat so I can sanity check them before you wri
   </div></div>
   <div class="shell"><main class="gview">
   <a class="back" href="#top">&#8592; All guides</a>
-  <div class="gsec"><h2>What you'll get</h2>
+  <div class="gsec"><h2>Before you start: what you need</h2>
+<ul>
+<li><b>A GoHighLevel plan that includes API access.</b> That is GoHighLevel Unlimited ($297 a month) or Agency Pro ($497). The $97 Starter plan has no API, so nothing can connect to it, GHL Command included. Check under Settings, then Billing, in GoHighLevel before you install.</li>
+<li><b>Claude on this computer.</b> GHL Command runs inside the Claude Desktop app or inside Claude Code in a terminal. It cannot run in a claude.ai tab in your browser. Not sure which you have? The Members Hub page Which Claude do I use? settles it in two minutes, and with it every later question about restarts.</li>
+<li><b>A Private Integration token</b> from the sub-account you want to work in, and that sub-account's location ID (the part of its GoHighLevel web address after /location/). Claude asks for both during setup, not the installer. GoHighLevel shows the token under Settings, then Private Integrations.</li>
+</ul>
+</div>
+<div class="gsec"><h2>What you'll get</h2>
 <ul>
 <li>GHL Command connected to your GoHighLevel account, ready to work from Claude.</li>
 <li>The same install whether you are on the Free plan or the full license. Upgrading later is just pasting a new license key. Nothing to reinstall.</li>
@@ -1283,24 +1506,26 @@ Show me the first ten rows in the chat so I can sanity check them before you wri
 </div>
 <div class="gsec"><h2>The two steps</h2>
 <ol class="steps">
-<li><b>Paste one command.</b> Open a terminal (Mac) or Command Prompt (Windows) and run: <code>npx -y @elitedcs/ghl-mcp cli install</code>. The installer walks you through connecting your account and your license key. When it finishes, Claude will tell you: &quot;Step 1 of 2 done.&quot;</li>
-<li><b>One 60-second browser login.</b> Say to Claude: &quot;Unlock the Workflow Builder.&quot; A Chrome window opens, you log into GoHighLevel like you always do, and you are done. This is how GHL itself trusts the workflow tools. Then restart Claude once. One restart, not two.</li>
+<li><b>Paste one command, once.</b> Open a terminal. On a Mac press Cmd+Space, type Terminal and press Return. On Windows press the Windows key, type cmd and press Enter. Paste <code>npx -y @elitedcs/ghl-mcp cli install</code> and press Enter. That one command writes GHL Command into the Claude Desktop app's settings for you, so there is no JSON to hand-edit and anything else already in there is left alone. Your account and your license are connected in the next breath, inside Claude, not in the terminal. <b>Using Claude Code instead?</b> Paste this line instead of the installer: <code>claude mcp add --scope user -t stdio ghl -- npx -y @elitedcs/ghl-mcp@latest</code>. Then quit Claude fully and open it again (Desktop app: Cmd+Q on a Mac, not just closing the window; on Windows close it from the system tray too. Claude Code: start a new session). The new tools only load on a fresh start. Now say to Claude: &quot;Set up GHL Command with my license key.&quot; Claude asks for your email, your license key and that sub-account's Private Integration token and location ID, then answers: &quot;Step 1 of 2 done.&quot;</li>
+<li><b>One 60-second browser login.</b> Say to Claude: &quot;Unlock the Workflow Builder.&quot; A Chrome window opens and you log into GoHighLevel like you always do. This is how GHL itself trusts the workflow tools. One last step: quit Claude fully and open it once more so the workflow tools load. That is two restarts in all, thirty seconds each, and the install is finished.</li>
 </ol>
 </div>
 <div class="gsec"><h2>Say this</h2>
 <div class="prompt"><q>Set up GHL Command with my license key.</q><button class="copy" type="button">Copy</button></div>
 <div class="prompt"><q>Unlock the Workflow Builder.</q><button class="copy" type="button">Copy</button></div>
 <div class="prompt"><q>Run a health check on my GHL Command install.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Which account am I in?</q><button class="copy" type="button">Copy</button></div>
 </div>
 <div class="gsec"><h2>Good to know</h2>
 <ul>
+<li><b>Done means:</b> you asked &quot;Which account am I in?&quot; and Claude answered with the right account name. That is the whole test.</li>
 <li>Step 2 is part of the install, not an extra. Until it is done, Claude will keep reminding you the install is one step from finished. Nothing will pretend to be complete when it is not.</li>
 <li>If anything says &quot;not working&quot; afterward, say &quot;run a health check&quot;: it tests every connection and tells you in plain English what, if anything, needs attention.</li>
 <li>Stuck at any point? Email support@ghlcommand.com and a human answers.</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 said step 1 of 2 done. Is it broken?&quot;</td><td>No, it is honest. Do step 2 (the browser login) and you are finished.</td></tr><tr><td>&quot;The workflow tools give errors after the login.&quot;</td><td>Restart Claude completely. Quit and reopen. The new login only loads on a fresh start.</td></tr><tr><td>&quot;I upgraded to paid. Do I reinstall?&quot;</td><td>No. Say &quot;set up GHL Command&quot; and paste only your email and new key. Everything you set up before is kept.</td></tr></table></div>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;I use Claude on the website. Where do I paste the command?&quot;</td><td>The install needs the Claude Desktop app or Claude Code on this computer. A browser tab cannot run it. The Members Hub page Which Claude do I use? shows the difference.</td></tr><tr><td>&quot;I ran the installer and Claude says it has no GHL Command tools.&quot;</td><td>Quit Claude fully (Cmd+Q on a Mac; system tray on Windows) and open it again. The tools load on a fresh start, never into a window that was already open.</td></tr><tr><td>&quot;GoHighLevel says API access is not on my plan.&quot;</td><td>Only Unlimited ($297) and Agency Pro ($497) include the API. On Starter ($97) nothing can connect, so upgrade the plan first.</td></tr><tr><td>&quot;It said step 1 of 2 done. Is it broken?&quot;</td><td>No, it is honest. Do step 2 (the browser login) and you are finished.</td></tr><tr><td>&quot;The workflow tools give errors after the login.&quot;</td><td>Restart Claude completely. Quit and reopen. The new login only loads on a fresh start.</td></tr><tr><td>&quot;I upgraded to paid. Do I reinstall?&quot;</td><td>No. Say &quot;set up GHL Command&quot; and paste only your email and new key. Everything you set up before is kept.</td></tr></table></div>
 </div>
   <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
   </main></div>
@@ -1371,6 +1596,221 @@ Do not send it. I will send it myself once I have read it.</p></div>
   </main></div>
 </section>
 
+<section class="gpage" id="g-missed-call-text-back">
+  <div class="hero"><div class="hero-in">
+    <p class="eyebrow">GHL Command User Guide</p>
+    <h1>Text back every missed call</h1>
+    <p class="sub">The phone rings out, a text goes back within seconds, and the caller is still yours.</p>
+    <div class="badges"><span class="badge on">Full license</span><span class="badge">~10 minutes</span><span class="badge">Automations</span></div>
+  </div></div>
+  <div class="shell"><main class="gview">
+  <a class="back" href="#top">&#8592; All guides</a>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A text that goes out the moment a call is missed, so the caller is answered instead of ringing your competitor next.</li>
+<li>The call logged on the contact, tagged, with a real person told to call back.</li>
+<li>One polite follow-up an hour later, and nothing more, because two texts about a missed call is help and three is harassment.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Set up missed call text back for my client.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>If nobody answers the phone, text them straight away.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>We are losing calls after hours. Fix 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">Build a Missed Call Text-Back workflow in my [Radiance Med Spa] account.
+Trigger: an inbound call is missed. Include no answer, busy and voicemail, and only inbound calls.
+Immediately: send a text apologising for missing them and asking what they need, tag them [missed-call], tag them [needs-callback], notify [me], and raise a call task for [me] due today.
+Then wait one hour and, if they have not replied, send one more short text offering a time to talk. Nothing after that.
+Write both texts for [a busy person who just wanted an answer], warm and plain, no marketing, and sign them from [the clinic] rather than from a system.
+Before you build: confirm the account has a phone number that can send texts, and confirm the real user you are notifying. If there is no SMS-capable number, stop and tell me, because every text step will fail silently.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The check for an SMS-capable number is the one that saves you: a texting workflow in an account with no number builds perfectly and sends nothing.</p>
+</div>
+<div class="gsec"><h2>What Claude builds</h2>
+<div class="flow">
+<div class="fnode"><span class="tag wait">Inbound call missed: no answer, busy, or voicemail</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Text back, straight away</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Tag: missed-call</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Tag: needs-callback</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Notify you, and raise a call task due today</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Wait one hour</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">One more text, if they still have not replied</span>then</div>
+</div>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude checks the account can actually send a text before it builds anything that sends one.</li>
+<li>It writes both messages for the caller you described and shows you them first.</li>
+<li>It builds the workflow as a draft and hands you the link to read it in GoHighLevel.</li>
+<li>You publish it.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>This is the automation most local businesses buy on the spot, because the loss it prevents is one they can feel. A missed call is a customer who is already trying to give you money.</li>
+<li>It covers no answer, busy and voicemail. Leaving voicemail out is the usual mistake, and voicemail is where the intent is highest.</li>
+<li>Restrict it to inbound. Without that, your own outbound calls that ring out will text your customers.</li>
+<li>Send it from the business, not from a person who might leave. Use the business number and sign with the business name.</li>
+<li>After hours is where this earns its keep, so do not put a time restriction on it unless the client insists.</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 fires on calls we made.&quot;</td><td>The direction filter is missing. Restrict the trigger to inbound calls only.</td></tr><tr><td>&quot;Nothing sends and there is no error.&quot;</td><td>The account has no SMS-capable number, or A2P registration is not finished. Ask Claude to check the account's numbers.</td></tr><tr><td>&quot;It texts people who reached us fine.&quot;</td><td>Voicemail is being counted as missed when the caller left a message and got a callback. Decide which statuses you want and say so.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>speed-to-lead</li>
+<li>send-texts-and-emails</li>
+<li>add-an-exit-workflow</li>
+</ul>
+</div>
+  <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
+  </main></div>
+</section>
+
+<section class="gpage" id="g-page-studio-pages-and-sites">
+  <div class="hero"><div class="hero-in">
+    <p class="eyebrow">GHL Command User Guide</p>
+    <h1>Page Studio: pages and sites</h1>
+    <p class="sub">Compose landing pages and full sites that render correctly in GHL.</p>
+    <div class="badges"><span class="badge on">Full license</span><span class="badge">~20 minutes</span><span class="badge">Client builds and pages</span></div>
+  </div></div>
+  <div class="shell"><main class="gview">
+  <a class="back" href="#top">&#8592; All guides</a>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A landing page or a multi-page site built inside GHL, section by section, that actually renders in the GHL editor rather than breaking it.</li>
+<li>Copy written for the business, not filler, and a form that posts into the right account.</li>
+<li>The saved page read back and measured, plus a rendered preview image of the finished page you can look at before anyone else does.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Build me a consult landing page for a med spa.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Build a four-page site: home, services, about, contact.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Show me the preview of the page you just built.</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, build a new landing page for [Radiance Med Spa] in a funnel called &quot;[Consult Funnel]&quot;.
+The page: a hero with the headline offer [free body contouring consult this week], three benefit blocks, a short form asking name, email, phone, and treatment interest, and a set of FAQs that answer the objections.
+Write the copy for [women aged 35 to 55 in Austin who have been thinking about this for months], warm and plain, no hype and no medical claims.
+Build it onto a brand new page, not over an existing one. When it is done, read the page back to confirm the copy saved, and show me the preview image so I can see it before I publish it.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The &quot;brand new page&quot; line is not a stylistic preference, it is the rule that keeps this working. See below.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude composes the page section by section, writing the copy as it goes. For a single landing page that is topbar, hero, three value cards, the form with its consent disclosures, FAQs and footer; a multi-page site gets the sections each page's role needs instead.</li>
+<li>It saves the whole page into the account in one pass, as a <b>draft</b>, and reads it back to confirm the save landed.</li>
+<li>It gives you the preview image GHL renders of the finished page, so you can check the desktop layout and the copy before anybody sees it.</li>
+<li><b>You publish it.</b> Publishing is a click in the GHL page editor, and a public web address needs a domain connected to that funnel. Neither can be done from here, and the guide will not pretend otherwise.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Always compose onto a fresh page. GHL accepts the first save onto a page and quietly ignores later attempts to replace that content. Building a new page takes seconds; fighting an already-populated one wastes an evening.</li>
+<li>To change a page after it is built, say what you want changed and let Claude build the revised version as a new page, then point the funnel step at it.</li>
+<li>The editor preview and the live page are not the same renderer. The preview image is enough to judge copy and layout; judge the finished thing on the live URL once you have published it and pointed a domain at the funnel.</li>
+<li>A single landing page is a fixed set of sections: topbar, hero, three value cards, the form, FAQs, footer. There is no testimonial or social-proof section on a landing page, so put your proof in the FAQ answers or the hero subhead rather than asking for a section that cannot be built. A multi-page site is composed differently, with the sections each page's role calls for, so this fixed list is about landing pages only.</li>
+<li>Images: the hero and the logo come from the built-in template until you supply your own. The tool says so every time it runs, and those two are the first things to replace before a client sees the page.</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 asked it to replace the content on my existing page and nothing changed.&quot;</td><td>That is GHL, not Claude. Build a new page and repoint the funnel step at it.</td></tr><tr><td>&quot;The page looks fine in the editor but wrong when I visit it.&quot;</td><td>The editor and the published page are different renderers. Check the preview image first, then judge the published page once it is live on your domain.</td></tr><tr><td>&quot;I cannot find the live URL.&quot;</td><td>There is not one yet. The page saves as a draft: publish it in the GHL page editor, and connect a domain to that funnel. Until both are done the page has no public address.</td></tr><tr><td>&quot;The form submits nowhere.&quot;</td><td>Once the page is published on a real domain, ask Claude to verify the funnel. It submits a test lead and reads GHL back to prove the contact was really created.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>clone-and-rebrand-a-site</li>
+<li>create-forms-and-read-submissions</li>
+</ul>
+</div>
+  <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
+  </main></div>
+</section>
+
+<section class="gpage" id="g-rescue-a-no-show">
+  <div class="hero"><div class="hero-in">
+    <p class="eyebrow">GHL Command User Guide</p>
+    <h1>Rescue a no-show</h1>
+    <p class="sub">The appointment is missed, the rebook offer goes out the same hour, and somebody is told to ring them.</p>
+    <div class="badges"><span class="badge on">Full license</span><span class="badge">~10 minutes</span><span class="badge">Booking and calendars</span></div>
+  </div></div>
+  <div class="shell"><main class="gview">
+  <a class="back" href="#top">&#8592; All guides</a>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A same-day text and email that offer a new time instead of asking why they did not come.</li>
+<li>The front desk told immediately, with a call task, because a no-show recovered by phone beats one recovered by text.</li>
+<li>Two more attempts over the following week, then a clean stop with the contact tagged so the client can see the real number.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Build a no-show follow-up for my client's consult calendar.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>When someone misses their appointment, text them to rebook.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>How many people are not turning up, and what happens when they do not?</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 a No-Show Rescue workflow in my [Radiance Med Spa] account.
+Trigger: an appointment on the [Consult] calendar is marked no-show.
+Straight away: tag them [no-show], notify [me], raise a call task for [me] due today, then send a text and an email that offer a new time and do not ask them to explain themselves.
+Then wait 4 days and text again, wait to day 7 and email once more, then write a note on the contact and tag them [no-show-lapsed]. Stop there.
+Write everything for [someone who probably felt awkward about missing it], warm and plain, no guilt, and make rebooking one tap.
+Before you build: confirm the [Consult] calendar exists in this account and scope the trigger to that calendar only, so a different appointment type does not start this sequence. Confirm the real user for the notification and the task.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. Scoping the trigger to one calendar is what stops a missed staff interview from sending a patient a rebooking offer.</p>
+</div>
+<div class="gsec"><h2>What Claude builds</h2>
+<div class="flow">
+<div class="fnode"><span class="tag wait">Appointment marked no-show on the Consult calendar</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Tag: no-show</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Notify the team, and raise a call task due today</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Text and email: here is a new time</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Wait 4 days, text again</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Wait to day 7, email once more</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Note on the contact, tag: no-show-lapsed</span>then</div>
+</div>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude confirms the calendar exists and ties the trigger to it, rather than to every appointment in the account.</li>
+<li>It writes the messages and shows you them before building.</li>
+<li>It builds as a draft and hands you the link.</li>
+<li>You publish it, and from then on the empty chair has a process attached to it.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>No guilt anywhere in the copy. People miss appointments because life happened, and a message that makes them feel caught does not get answered.</li>
+<li>The call task is the part that actually recovers bookings. The messages buy you permission; a person makes the appointment.</li>
+<li>Tie it to one calendar. This is the single most common mistake with appointment triggers and it is invisible until a client complains.</li>
+<li>Tag the ones who never come back. The client wants that number, and it is the honest measure of whether the recovery works.</li>
+<li>Someone has to be marking no-shows in GoHighLevel. If nobody does, this workflow is perfect and never fires.</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 fired for the wrong kind of appointment.&quot;</td><td>The trigger was not scoped to a calendar. Point it at one and rebuild.</td></tr><tr><td>&quot;It never runs.&quot;</td><td>Nobody is marking appointments as no-show. Fix the front desk habit first, the workflow second.</td></tr><tr><td>&quot;It went out while they were sitting in reception.&quot;</td><td>They were marked no-show too early. Agree how long after the start time the mark happens.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>appointment-reminders</li>
+<li>see-and-manage-appointments</li>
+<li>add-an-exit-workflow</li>
+</ul>
+</div>
+  <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
+  </main></div>
+</section>
+
 <section class="gpage" id="g-review-your-conversations">
   <div class="hero"><div class="hero-in">
     <p class="eyebrow">GHL Command User Guide</p>
@@ -1835,7 +2275,6 @@ Then confirm back to me, one line each, that every post saved as a draft and whi
 </div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
-<li>blog-posting</li>
 <li>weekly-account-report</li>
 </ul>
 </div>
@@ -1843,6 +2282,88 @@ Then confirm back to me, one line each, that every post saved as a draft and whi
   </main></div>
 </section>
 
+<section class="gpage" id="g-speed-to-lead">
+  <div class="hero"><div class="hero-in">
+    <p class="eyebrow">GHL Command User Guide</p>
+    <h1>Answer a new lead in seconds</h1>
+    <p class="sub">The text goes out the moment the form lands, the deal card appears, and a real person gets the task.</p>
+    <div class="badges"><span class="badge on">Full license</span><span class="badge">~10 minutes</span><span class="badge">Automations</span></div>
+  </div></div>
+  <div class="shell"><main class="gview">
+  <a class="back" href="#top">&#8592; All guides</a>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A text and an email that leave the moment a lead fills in the form, not whenever somebody next checks the inbox.</li>
+<li>A deal card created on the pipeline and the lead assigned to a real person, so nothing sits in an unowned pile.</li>
+<li>Two more nudges over the next day, and all of it stops the second they answer.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Build a speed to lead workflow for my new client.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>When someone fills in the contact form, text them straight away and tell me.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Why is nothing happening when a lead comes in?</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 a Speed to Lead workflow in my [Radiance Med Spa] account.
+Trigger: someone submits the form [New Client Inquiry].
+Immediately, in this order: tag them [new-lead], create a deal on [the main pipeline] in stage [New Lead], assign the contact to [me], send a text, send an email, notify [me], and create a call task due today.
+Then follow up: wait 20 minutes and text again if they have not replied, wait until the next day and email again.
+Write the text and the email for [women 35 to 55 who just asked about a consult], warm and plain, and keep the first text under 160 characters so it lands as one message.
+Before you build: look up the real form, the real pipeline and stage, and the real user in my account, and stop and tell me if any of them do not exist rather than guessing. Leave it as a draft so I can read it before it goes live.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The last paragraph is the important one: a workflow pointed at a pipeline stage that does not exist saves cleanly and then does nothing at all.</p>
+</div>
+<div class="gsec"><h2>What Claude builds</h2>
+<div class="flow">
+<div class="fnode"><span class="tag wait">They submit the form</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Tag: new-lead</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Create the deal card, stage New Lead</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Assign the contact to a real person</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Text, straight away</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Email, straight away</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Notify you, and raise a call task due today</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Wait 20 minutes, then text again</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Wait until tomorrow, then email again</span>then</div>
+</div>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude looks up the real form, pipeline, stage and user in the account. Not names you typed, actual records.</li>
+<li>It writes the messages for the audience you described and shows you every one of them before anything is built.</li>
+<li>It builds the workflow as a draft, checks each piece exists after it creates it, and hands you the link.</li>
+<li>You read the messages, then publish it yourself.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Speed is the whole product here. The industry research everyone quotes is about the first few minutes, and the reason this works is that it removes the human from the first reply entirely.</li>
+<li>Two different things stop the chasing and you want both. &quot;Stop on response&quot; ends the sequence when they reply, and Claude sets it on this workflow. An exit workflow covers everything a reply does not: they booked, they paid, somebody spoke to them. Without the second one, your third nudge lands after the customer has already booked, which is worse than sending nothing.</li>
+<li>The call task matters more than it looks. The text opens the conversation; a person has to close it.</li>
+<li>The assign step needs a real user in that account. So does a notification addressed to one person: name somebody and leave the recipient blank and the workflow saves, publishes, runs, and simply never notifies anyone. A notification set to everyone is a different shape and works fine.</li>
+<li>Keep the first text short. Long first texts read as marketing, and marketing gets ignored.</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, but no deal card appears.&quot;</td><td>The stage id was wrong or the pipeline did not exist. Ask Claude to check the pipeline and stage in the account, then rebuild that step.</td></tr><tr><td>&quot;The texts keep going after they replied.&quot;</td><td>Check &quot;stop on response&quot; is on. If they booked rather than replied, that is an exit workflow's job instead.</td></tr><tr><td>&quot;It never fires.&quot;</td><td>Built is not published, and a draft never runs on real leads. Publish it once you have read the messages.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>add-an-exit-workflow</li>
+<li>build-nurture-sequence</li>
+<li>stand-up-a-pipeline</li>
+</ul>
+</div>
+  <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
+  </main></div>
+</section>
+
 <section class="gpage" id="g-stand-up-a-pipeline">
   <div class="hero"><div class="hero-in">
     <p class="eyebrow">GHL Command User Guide</p>
@@ -1960,6 +2481,68 @@ Do not add any contacts or deals to it yet.</p></div>
   </main></div>
 </section>
 
+<section class="gpage" id="g-take-over-an-inherited-account">
+  <div class="hero"><div class="hero-in">
+    <p class="eyebrow">GHL Command User Guide</p>
+    <h1>Take over an account someone else built</h1>
+    <p class="sub">Find out what is in there, what is actually running, and what is quietly broken, before you touch anything.</p>
+    <div class="badges"><span class="badge on">Full license</span><span class="badge">~20 minutes</span><span class="badge">Account admin</span></div>
+  </div></div>
+  <div class="shell"><main class="gview">
+  <a class="back" href="#top">&#8592; All guides</a>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>An inventory of everything in the account, so you know what you have taken on before you promise anything.</li>
+<li>A list of what is actually live versus sitting in draft, which is almost never what the client believes.</li>
+<li>The broken things named specifically: workflows pointing at deleted stages, steps that will never fire, messages with nobody to send them.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>I just took over this account. Tell me what is in it.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>What is actually running in here, and what is broken?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Audit this account before I touch anything.</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">I have just taken over the [Radiance Med Spa] account and I did not build it. Do not change anything.
+First: confirm which account I am in, then inventory it. Pipelines and their stages, custom fields, tags, calendars, forms, funnels, workflows, and how many contacts.
+Then tell me what is actually live: which workflows are published and which are still drafts.
+Then audit the workflows for things that will fail quietly: steps pointing at pipelines, stages, fields, calendars or users that no longer exist; stage moves that cannot move anything; and notifications aimed at a person with nobody selected.
+Finally, give me the three things I should fix first and why, in plain English I could read to the client.
+Change nothing. This is a read.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The two &quot;change nothing&quot; lines are not decoration. The first hour on an inherited account is the one where a well-meaning fix breaks the thing that was earning money.</p>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude confirms the account first, because the most expensive mistake here is auditing the wrong one.</li>
+<li>It reads the account and lists what exists, without writing anything.</li>
+<li>It runs the workflow audit and reports the silent failures by name, with the reason each one will not work.</li>
+<li>It hands you a short prioritised list you can take to the client.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Do this before the kickoff call, not after. Walking in already knowing what is broken changes the whole relationship.</li>
+<li>Published versus draft is the first thing to check. Clients routinely believe a sequence is running when it was never turned on. The audit can tell you published from draft; it cannot tell you when a workflow last actually ran, so if that matters, look at recent contacts rather than asking for a number nothing can give you.</li>
+<li>Invalid ids are the usual cause of silent failure. A workflow that points at a deleted stage saves, runs, and does nothing, and GoHighLevel will not tell you.</li>
+<li>Take the export before you change anything. It is your restore point and it costs one instruction.</li>
+<li>Resist fixing as you read. Finish the audit, agree the list, then work through 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;I fixed a workflow and leads stopped arriving.&quot;</td><td>Something depended on it. Audit and agree the list before editing, and keep the export.</td></tr><tr><td>&quot;The client said it was all working.&quot;</td><td>Published is not the same as working. Check the audit findings, then look at whether recent contacts actually moved.</td></tr><tr><td>&quot;I audited the wrong account.&quot;</td><td>Confirm the account by name before anything else, every time.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>audit-your-workflows</li>
+<li>workflows-that-will-not-save</li>
+<li>account-admin-basics</li>
+<li>run-a-checkup</li>
+</ul>
+</div>
+  <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
+  </main></div>
+</section>
+
 <section class="gpage" id="g-track-and-move-opportunities">
   <div class="hero"><div class="hero-in">
     <p class="eyebrow">GHL Command User Guide</p>
@@ -2193,6 +2776,83 @@ Then give me the three things you would look at first if this were your account.
   </main></div>
 </section>
 
+<section class="gpage" id="g-win-back-a-cold-list">
+  <div class="hero"><div class="hero-in">
+    <p class="eyebrow">GHL Command User Guide</p>
+    <h1>Win back a cold list</h1>
+    <p class="sub">Wake up the contacts a client already paid for, over thirty days, without burning the list.</p>
+    <div class="badges"><span class="badge on">Full license</span><span class="badge">~15 minutes</span><span class="badge">Automations</span></div>
+  </div></div>
+  <div class="shell"><main class="gview">
+  <a class="back" href="#top">&#8592; All guides</a>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>A thirty-day sequence that goes out to contacts who went quiet, spread across email and text so it does not read as a blast.</li>
+<li>A segment built first, so you know exactly who is getting it and how many before a single message leaves.</li>
+<li>A clean ending: everyone who does not answer is tagged and left alone, which is what keeps the list usable next year.</li>
+</ul>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Build a win-back campaign for my client's old leads.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>We have 900 contacts who went cold. Wake them up.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Who has not heard from us in six months?</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 win-back campaign for contacts who have gone quiet.
+First, before building anything: find the contacts who have not replied or booked in the last [six] months, tell me how many there are, and show me ten of them so I can check the segment is right.
+Then build a thirty-day workflow triggered by the tag [winback-start]: an email on day 0, a text on day 3, an email on day 7, a text on day 14, and a final email on day 30. At the end, write a note on the contact and tag them [winback-no-answer].
+Write the messages for [past enquiries who never booked], warm and plain. The first one asks a single question and does not pitch. The last one says plainly that it is the last message and leaves the door open.
+Do not add anyone to the workflow yet. Build it, show me the messages, and stop.</p></div>
+<p class="gpara">Everything in [brackets] is yours to change. The first paragraph is deliberate: you look at the segment before you build the campaign, because the fastest way to destroy a client's sending reputation is to mail the wrong nine hundred people.</p>
+</div>
+<div class="gsec"><h2>What Claude builds</h2>
+<div class="flow">
+<div class="fnode"><span class="tag wait">Tag added: winback-start</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag em">Email</span>one question, no pitch</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Wait 3 days, then a text</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Wait to day 7, then an email</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Wait to day 14, then a text</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Wait to day 30, the last email, and say it is the last</span>then</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">Note on the contact, tag: winback-no-answer</span>then</div>
+</div>
+</div>
+<div class="gsec"><h2>What happens when you ask</h2>
+<ol class="steps">
+<li>Claude builds the segment first and tells you the count, so you approve a number before you approve a campaign.</li>
+<li>It writes all five messages and shows you every one.</li>
+<li>It builds the workflow as a draft. Nobody is enrolled.</li>
+<li>You read it, publish it, then add the tag to the segment in batches.</li>
+</ol>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Add the tag in batches, not to nine hundred people at once. A few hundred a day keeps you out of spam folders and keeps the replies answerable by a human.</li>
+<li>The first message should not sell anything. It asks one question. Replies are the point; bookings come after.</li>
+<li>Say plainly in the last message that it is the last one. It lifts response and it is the honest thing to do.</li>
+<li>&quot;Stop on response&quot; ends the sequence the moment they reply, and Claude sets it here. Add an exit workflow as well for the cases a reply does not cover, such as booking straight from a link.</li>
+<li>Check the account's sending domain is set up before you send a five-email sequence to a cold list, or you will find out the hard way.</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;Open rates collapsed and now everything goes to spam.&quot;</td><td>The list went out all at once, cold. Enrol in batches, and warm the domain first.</td></tr><tr><td>&quot;People replied and kept getting the campaign.&quot;</td><td>Check &quot;stop on response&quot; is on. For people who booked without replying, add an exit workflow pointed at this campaign.</td></tr><tr><td>&quot;It went to customers, not old leads.&quot;</td><td>The segment was wrong. Rebuild it and read the sample of ten before enrolling anyone.</td></tr></table></div>
+</div>
+<div class="gsec"><h2>Related guides</h2>
+<ul>
+<li>bulk-tag-and-clean-up</li>
+<li>add-an-exit-workflow</li>
+<li>build-nurture-sequence</li>
+</ul>
+</div>
+  <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
+  </main></div>
+</section>
+
 <section class="gpage" id="g-workflows-that-will-not-save">
   <div class="hero"><div class="hero-in">
     <p class="eyebrow">GHL Command User Guide</p>