@elitedcs/ghl-mcp 3.84.9 → 3.85.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +12 -0
- package/README.md +1 -1
- package/dist/index.js +2418 -884
- package/guide/guide.html +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,17 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 3.85.0 — the secret shopper: see what a new lead actually gets, and what every workflow step really did
|
|
4
|
+
|
|
5
|
+
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.
|
|
6
|
+
|
|
7
|
+
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.
|
|
8
|
+
|
|
9
|
+
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.
|
|
10
|
+
|
|
11
|
+
## 3.84.10 — confirming a call's numbers no longer files the call twice
|
|
12
|
+
|
|
13
|
+
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.
|
|
14
|
+
|
|
3
15
|
## 3.84.9 — build steps you can read
|
|
4
16
|
|
|
5
17
|
Each client's build now shows a progress bar, the next step across the full width with one clear button, and one readable row per step, instead of seven narrow columns. Nothing about how building works changed: the same steps, checks and typed confirmations. Step descriptions now say what each step really does. Verify checks the links between workflows, pipelines and fields and tests the form, and reports anything it cannot check.
|
package/README.md
CHANGED