@elitedcs/ghl-mcp 3.94.2 → 3.96.0

package/CHANGELOG.md

@@ -1,5 +1,37 @@
 # Changelog
 
+## 3.96.0: Choose which of your numbers a text goes out from, and send it exactly once
+
+**You can now say which of an account's phone numbers a text goes out from.** Ask Claude to send a text from a specific number, for example "text Jane from +15555550100". GHL Command first checks that the number is one of that account's own lines. If it is not, nothing is sent and the answer lists the account's real numbers. If the check cannot run, nothing is sent either, and the answer says why.
+
+**After the text goes out, GHL Command checks which number GoHighLevel reports it used.** The answer says whether it matches the number you asked for. If GoHighLevel used a different number, the answer says so plainly and tells you not to report it as sent from the number you asked for. If GoHighLevel names the sender only by the account's name instead of a number, the answer says the sender could not be confirmed.
+
+**A text can be sent exactly once, with no automatic resend.** Normally, if the connection drops, GoHighLevel says it is busy, or GoHighLevel has an error of its own, GHL Command tries again. For a text that is a risk: the first try may already have gone out, and the person gets it twice. Ask for a single attempt and GHL Command never resends. If that one try fails, the answer says which of two things happened:
+- **Not sent.** GoHighLevel refused it, or GHL Command stopped it before it left. Safe to send again.
+- **May have gone out.** The connection dropped, the try timed out, or GoHighLevel had an error of its own, so there is no way to tell whether it went. Check the conversation before sending again.
+
+**Nothing changes unless you ask for it.** Texts that use neither option work exactly as before.
+
+## 3.95.0: The brain checks a message against the lead's record before it goes out
+
+**The brain can now check a message against the lead's record before it goes out.** You add one asking step in front of an SMS or email in a workflow. When a lead reaches it, the brain reads that lead's GoHighLevel record (contact, appointments, invoices and recent messages), its own notes on the lead, your business's path and your past rulings, and answers send or hold. If the brain cannot check it, a reminder still goes out and a message asking the lead for something is held for a person.
+
+**Turn it on in three steps.** First, ask Claude to set your business's path for the judge: the steps a lead goes through, what each costs and what counts as done. Second, run the brain's wiring, which shows the ask key once. Keep it. Third, ask Claude to add the brain's step in front of the message, naming the workflow and the message step, and say whether it is a reminder. Claude shows you the workflow's full new step list first and changes nothing until you say yes. For the first brain step in an account, give Claude the ask key that wiring showed you once; after that the tool finds it on the existing brain step, so you do not paste it again. The tool can take the step out again while the workflow is unchanged.
+
+**Every answer arrives within 6 seconds.** If anything is slower than that, the account's fail rule answers instead, and a reminder is still held when the brain or GoHighLevel already shows the lead opted out or on do-not-disturb. The brain records its judgment just after it answers. If that recording fails, the judgment shows as not judged.
+
+**If the brain cannot be reached, reminders still go out and other messages are held.** A held message does not go out unless someone sends it by hand. A reminder is held only when the brain answers no; a message asking the lead for something goes out only when the brain answers yes.
+
+**When the brain says not to send, its reason stays out of the workflow.** The answer says the brain is recording its reason and will try to add it to the contact as a note. The reason never appears in the workflow's run history.
+
+**A wrong or replaced ask key holds every message.** A step still carrying an old key is held, reminders included, until it carries the current one.
+
+**Know the limits before you rely on it.**
+- For now it works only on accounts on this computer's sandbox list.
+- A reminder the brain could not check goes out unless the brain already knows the lead opted out or is on do-not-disturb.
+- It checks about 4 messages every 10 seconds per account. A workflow that sends to a whole list at once will have most messages decided by the fail rule: asks held for a person and reminders sent unchecked. A speed-up is planned.
+- Anyone who can see the workflow's run history can see the ask key. Repeated fake requests could use up the judge's half of the day's GoHighLevel allowance. After that, reminders go out unchecked for the rest of the day. Drafts are not affected.
+
 ## 3.94.2: A signed-out Claude Code is named as signed out, and a Build waiting on you says so
 
 **Signed out means signed out.** If Claude Code is signed out on your computer, a step now says so and how to fix it: sign in to Claude Code again (type /login in Claude Code). Before, the start-up check read Claude Code's "Not logged in" answer as a sign that an update had changed something, and said so.

package/README.md

@@ -904,7 +904,7 @@ Built by **[Elite DCs, LLC](https://elitedcs.com)** — a digital marketing and
 
 **Tech stack:** TypeScript, Node.js, esbuild, MCP SDK, Zod, GHL API v2, Firebase Auth
 
-**Version:** 3.94.2
+**Version:** 3.96.0
 
 ---