@elitedcs/ghl-mcp 3.65.0 → 3.65.1

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # Changelog
 
+## 3.65.1 — the guide caught up with the product
+
+No code changes. The built-in user guide ships inside the install, so it goes
+out as its own release.
+
+- **Fix: the booking-calendar guide was telling you to do something by hand that
+  the product now does.** It said minimum booking notice lived on GHL's calendar
+  screen "and not here", and sent you there to set it. 3.65.0 made it settable
+  directly. Anyone following that page yesterday was sent clicking through GHL
+  for no reason.
+- **Booking calendars**: daily caps and minimum notice are now in the guide, in
+  the same ask that sets your hours and slot length. Plus what to do if an older
+  version reset your slot lengths or opening hours when you changed something
+  else.
+- **Nurture sequences**: quiet hours. What they are, why every workflow that
+  texts needs its own, and the one thing to go check: if you set quiet hours
+  before 3.65.0, they were dropped the next time that workflow was saved. Open
+  anything that texts and set them once more.
+- **Contact lists**: how to save a group as a list you can reopen, rather than
+  rebuilding the same filter every Monday. These tools never worked before
+  3.65.0, so if you tried this and found nothing in GHL, that is why.
+- **Blueprint**: how appointment, reply, missed-call and number-check triggers
+  get scoped to the thing you actually meant, and why a stage move needs to find
+  its deal first.
+
+Every prompt in the guide is bound to a run that actually happened in a real
+sub-account. The three new ones were proven live before this shipped.
+
 ## 3.65.0 — nine calls that reported success and did the wrong thing
 
 Found while building a 139-requirement home-care front office end to end. Every

package/dist/index.js

@@ -2854,7 +2854,7 @@ var require_package = __commonJS({
   "package.json"(exports2, module2) {
     module2.exports = {
       name: "@elitedcs/ghl-mcp",
-      version: "3.65.0",
+      version: "3.65.1",
       mcpName: "io.github.drjerryrelth/ghl-command",
       description: "GoHighLevel MCP Server for Claude. 238 tools \u2014 full CRM, automation, marketing control, account-wide workflow audit, live funnel-capture verification, and the only programmatic GHL workflow builder, now multi-tenant across client accounts.",
       main: "dist/index.js",

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: 6ffc57aa1224244f -->
+<!-- guides-hash: f8bcba4d92d295fa -->
 <style>
 :root{
   --bg:#F2F4F6; --surface:#FFFFFF; --ink:#1C2833; --muted:#5B6B78; --line:#DDE3E8;
@@ -173,14 +173,14 @@ main{max-width:1180px}
   </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>
 <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>
+<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 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">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>
+<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">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>
@@ -189,7 +189,7 @@ main{max-width:1180px}
 <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"><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">Read below &#8595;</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"><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></div></div>
+<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">Read below &#8595;</span></div></a></div></div>
 <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>
@@ -490,16 +490,19 @@ When it saves, list the templates in the account so I can see it landed, and tel
 <ul>
 <li>A ready-to-review workflow in your GHL account: texts, emails, and waits in the right order, every message written out.</li>
 <li>Stop-on-reply built in, so nobody gets a robot follow-up after a human conversation has started.</li>
+<li>Quiet hours, so the sequence never texts somebody at two in the morning because a wait timer landed there.</li>
 <li>A matching exit workflow: when someone replies, they leave the nurture, get tagged, and you get notified.</li>
 </ul>
 </div>
 <div class="gsec"><h2>Quick start</h2>
 <div class="prompt"><q>Build a 7-day nurture for new leads: text right away, email an hour later, then follow up daily until they reply.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Only let this workflow send between 8am and 9pm.</q><button class="copy" type="button">Copy</button></div>
 <div class="prompt"><q>Show me the full plan first. Do not build anything until I approve 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 nurture workflow in my [Radiance Med Spa] account called &quot;New Lead Nurture 7 Day&quot;. Trigger: when the tag [new-lead] is added.
 The sequence: (1) Immediately, text: &quot;Hi {{first name}}, this is [Dana] from [Radiance Med Spa]. Thanks for reaching out about our [body contouring special]! Want me to grab you a free consult this week?&quot; (2) Wait 1 hour, then send an email, subject &quot;Your consult is waiting&quot;, friendly, three short paragraphs, one button to my booking link. (3) Wait 1 day, then text a soft check-in. (4) Wait 2 days, then email a before-and-after story from a real client. (5) Wait 3 days, then text a last-call message about the special ending.
+Set quiet hours on this workflow: it may only send between [8am] and [9pm], [every day]. Nothing goes out outside that window.
 Stop the sequence the moment they reply on any channel. Also build the exit workflow: when they reply, remove them from the nurture, tag them [warm-lead], add a note with what they said, and notify me.
 Before you build anything: show me every message written out for my approval, and verify my account's real pipeline, tag, and calendar IDs so nothing fails silently.</p></div>
 <p class="gpara">Everything in [brackets] is yours to change. The last paragraph is the safety net: it makes Claude plan first and check your account's real setup before touching it.</p>
@@ -521,6 +524,8 @@ Before you build anything: show me every message written out for my approval, an
 <div class="fnode"><span class="tag em">Email</span>before-and-after story</div>
 <div class="fconn"></div>
 <div class="fnode"><span class="tag sms">Text</span>last call</div>
+<div class="fconn"></div>
+<div class="fnode"><span class="tag wait">QUIET HOURS: nothing sends outside 8am to 9pm, whenever a wait timer lands</span>then</div>
 <div class="fstop">the whole track stops the moment they reply, on any channel</div>
 </div>
 </div>
@@ -533,13 +538,17 @@ Before you build anything: show me every message written out for my approval, an
 </div>
 <div class="gsec"><h2>Good to know</h2>
 <ul>
+<li>Ask for quiet hours on anything that sends texts. Wait timers do not care what time it is: a one-day wait started at 11pm fires at 11pm. A window of 8am to 9pm is the common answer, and it is set per workflow, so every sequence that texts needs its own.</li>
+<li>Quiet hours are the only place a sending window lives. There is no time-of-day setting inside the AI agent builders, so if a bot hands off to a workflow, this is what protects the handoff.</li>
+<li>Once set, quiet hours stay set. Edit a message or add a step later and the window comes through untouched.</li>
 <li>GHL's editor struggles past about 40 steps in one workflow. Claude knows this and splits long sequences automatically.</li>
 <li>Messages come out in your voice if you give Claude a sample first: paste one text you would actually send and say &quot;write like this&quot;.</li>
 <li>The nurture and its exit workflow are a pair. If you ever remove one, ask Claude to update the other, so nothing points at a workflow that is gone.</li>
+<li>If a step in your sequence moves a deal to a new stage, it needs to find that deal first. Say &quot;look up the opportunity, then move it&quot; and Claude wires both. A move on its own saves cleanly and then does nothing.</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 the workflow but nothing ever sends.&quot;</td><td>Say &quot;audit this workflow&quot;. GHL fails silently when something inside is misconfigured; the audit finds it in seconds.</td></tr><tr><td>&quot;The messages sound generic.&quot;</td><td>Give Claude your voice before building: paste a real text you have sent and say &quot;write like this&quot;.</td></tr><tr><td>&quot;I want to change one message.&quot;</td><td>Say &quot;update step 3's text to...&quot; and never rebuild from scratch. Updates keep everything connected.</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;It built the workflow but nothing ever sends.&quot;</td><td>Say &quot;audit this workflow&quot;. GHL fails silently when something inside is misconfigured; the audit finds it in seconds.</td></tr><tr><td>&quot;A text went out at 3am.&quot;</td><td>The workflow has no quiet hours. Say &quot;only let this workflow send between 8am and 9pm&quot; and Claude sets the window.</td></tr><tr><td>&quot;I set quiet hours and later they were gone.&quot;</td><td>Versions before 3.65.0 dropped the window whenever the workflow was saved again. Open any workflow that texts, check its window, and set it once more. From 3.65.0 on it survives every later edit.</td></tr><tr><td>&quot;The messages sound generic.&quot;</td><td>Give Claude your voice before building: paste a real text you have sent and say &quot;write like this&quot;.</td></tr><tr><td>&quot;I want to change one message.&quot;</td><td>Say &quot;update step 3's text to...&quot; and never rebuild from scratch. Updates keep everything connected.</td></tr></table></div>
 </div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
@@ -552,19 +561,21 @@ Before you build anything: show me every message written out for my approval, an
 
 <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>
+  <p class="gpromise">Tag, untag, or update hundreds of contacts in one instruction, then save the group as a list.</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>
+<li>The group saved as a list you can open in GHL any day, instead of rebuilding the same filter every week.</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 class="prompt"><q>Save everyone tagged needs-follow-up as a list called 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].
@@ -573,11 +584,19 @@ Once I say go: add the tag [needs-follow-up] to all of them, then tell me how ma
 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>Save the group as a list</h2>
+<p class="gpara">Tagging answers &quot;who needs chasing today&quot;. A saved list answers it again next Monday without you rebuilding the filter. Once a group is tagged, ask Claude to save it.</p>
+<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, save a contact list called &quot;[Needs Follow Up]&quot; that shows everyone tagged [needs-follow-up].
+Read it back to me once it is saved so I know it exists, and tell me where to find it in GHL.
+Do not change any contact, and do not delete any list that is already there.</p></div>
+<p class="gpara">The list appears in your contacts view in GHL like any other saved list. Ask Claude to delete one by name when a campaign is over.</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>
+<li>If you asked for a saved list, it creates it and reads it back so you can see it exists.</li>
 </ol>
 </div>
 <div class="gsec"><h2>Good to know</h2>
@@ -585,11 +604,13 @@ Do not delete anything, do not send anything, and do not change any other field.
 <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>Saved lists are built from conditions, not from a frozen set of names. Tag somebody tomorrow and they appear in the list on their own.</li>
+<li>Saving lists needs version 3.65.0 or later. In every version before it, the list tools reported success and quietly created nothing, so if you tried this before and found nothing in GHL, that is why. Ask Claude &quot;what version are you running&quot; if you are not sure.</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 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 saved a list before and it never showed up in GHL.&quot;</td><td>Versions before 3.65.0 could not actually save lists, though they said they had. Update, then ask again.</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>
@@ -1040,18 +1061,21 @@ Before you send: confirm the exact contact you matched, show me their phone numb
   <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>A daily booking cap and a minimum notice period, so a full day stays full and nobody books your next hour.</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>Cap the consult calendar at 6 bookings a day and require 24 hours notice.</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.
+Cap it at [6] bookings a day, and require at least [24] hours notice so nobody books the same morning.
 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>
@@ -1059,21 +1083,23 @@ When it saves, read the calendar back to me and show me the next five bookable s
 <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 creates the calendar with your hours, length, gaps, daily cap, 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>Ask for the daily cap and the notice period in the same breath as the hours. Six bookings protects a clinic day that also has patients in it, and twenty-four hours notice is what stops someone taking your next open slot while you are still in a room.</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>Changing one setting later leaves the others alone. Rename a calendar or raise its daily cap and the slot length, the gaps and the opening hours all stay exactly as you left them.</li>
+<li>Confirmation and reminder messages still live on GHL's calendar screen. 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 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>Say how much notice you want and Claude sets it on the calendar. Twenty-four hours is the usual answer for a consult.</td></tr><tr><td>&quot;One busy day swallowed my whole week.&quot;</td><td>Ask for a daily cap. It limits how many bookings a single day can take, no matter how many hours are open.</td></tr><tr><td>&quot;My slot lengths and opening hours went back to defaults on their own.&quot;</td><td>Versions before 3.65.0 could reset untouched settings when you changed a different one. Ask Claude to read the calendar back and set them again. From 3.65.0 on, settings you do not mention are left alone.</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>

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@elitedcs/ghl-mcp",
-  "version": "3.65.0",
+  "version": "3.65.1",
   "mcpName": "io.github.drjerryrelth/ghl-command",
-  "description": "GoHighLevel MCP Server for Claude. 238 tools \u2014 full CRM, automation, marketing control, account-wide workflow audit, live funnel-capture verification, and the only programmatic GHL workflow builder, now multi-tenant across client accounts.",
+  "description": "GoHighLevel MCP Server for Claude. 238 tools — full CRM, automation, marketing control, account-wide workflow audit, live funnel-capture verification, and the only programmatic GHL workflow builder, now multi-tenant across client accounts.",
   "main": "dist/index.js",
   "bin": {
     "ghl-mcp": "dist/index.js"