@elitedcs/ghl-mcp 3.84.10 → 3.86.0

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## 3.86.0 — fast-forward: test a two-week nurture in minutes
+
+Tick "Fast-forward" when you start the secret shopper and it makes a temporary, clearly named copy of each workflow you chose, with every step kept and every wait cut to 1 minute, runs the test lead through the copy, and deletes the copy afterwards. A nurture that takes two weeks in real life is checked in about ten minutes, step by step, with every finding named after your original workflow and step. The original is only ever read, never changed, and the report lists how long each wait really is and any quiet hours the copy skipped.
+
+Nothing reaches your staff during the test. Staff alerts (in-app or by email), tasks, and lead or card assignments go to one person you choose, marked TEST. The start screen reads the chosen workflows and lists every outside service they send the lead to (a CRM, Zapier, a sheet) as a tick box with a plain explanation; the test lead is only sent to the ones you tick. For now fast-forward handles straight-line workflows with time waits; a workflow with if/else branches, hand-offs to other workflows, other kinds of waits, text-message staff alerts, or a webhook address built from a merge field is refused with the reason, before anything is created. Temporary copies left by an interrupted check are cleaned up automatically, and only ever the ones this computer recorded making.
+
+Also fixed in the secret shopper: GoHighLevel sometimes lets a lead out of a wait several minutes late. The check now waits up to 10 extra minutes for a wait that should already be over, and anything still held behind it is reported as "held by GoHighLevel, run it again", never as "never sent", and the headline never reads all-clear while messages are held.
+
+## 3.85.0 — the secret shopper: see what a new lead actually gets, and what every workflow step really did
+
+Pick a client, tick the workflows a new lead goes through, and press Start. It makes a clearly marked test lead with your own email address and no first name, adds it to those workflows, and watches until the last planned message is due. Then it reads back every text and email the account actually sent, word for word, and shows what a customer would have seen wrong: a blank name ("Hi , "), template code left showing, another of your accounts' business names, a link that doesn't open, a message sent twice, or a planned message that never came.
+
+It also reads GoHighLevel's own execution log, so every workflow step is checked, not just the messages: tags, fields, pipeline cards, owners, staff alerts, tasks, notes, webhooks and branches. Each step shows as ran, skipped (with GoHighLevel's reason in plain words), did nothing, failed, or waiting. Two failures it catches that GoHighLevel never warns about: a "move the card" step for a lead with no card does nothing and carries on, and a webhook to an address that doesn't answer holds every later step until GoHighLevel gives up (about 50 minutes on our test account). It also warns when a chosen workflow is still a draft: GoHighLevel accepts the lead and runs nothing.
+
+The test lead is removed when the check finishes, unless you ask to keep it. It never opens an unsubscribe or tracked link, never uses a customer's details, and never runs on an account you have locked. Anything that looks like a key in a message is hidden. In the cockpit it is "Secret shopper" in the sidebar; in chat, say "run the secret shopper on this client". Texts are checked when you give a test phone you own. What it does not check yet: booking a time, replying as the lead, phone calls, and whether the wording persuades.
+
 ## 3.84.10 — confirming a call's numbers no longer files the call twice
 
 When you answered "confirm all" after bringing in a client call, the call was filed a second time: a duplicate call file marked "(2)" and the same call added to "Client understanding" twice. Now the confirmation adds one dated "Confirmed by you" section to the call you already filed, and to Client understanding, listing the numbers that saved. If the first call was never filed, the whole call is filed then, so nothing is lost. The reply says the numbers saved only when they actually did.

package/README.md

@@ -897,7 +897,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.84.10
+**Version:** 3.86.0
 
 ---