@elitedcs/ghl-mcp 3.72.3 → 3.73.1
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 +50 -0
- package/dist/assessment.html +789 -0
- package/dist/index.js +1555 -483
- package/guide/guide.html +1 -1
- package/package.json +6 -4
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,55 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 3.73.1 — the cockpit points at the right hub
|
|
4
|
+
|
|
5
|
+
The member hub is Command OS only and now lives at its own address behind a licence
|
|
6
|
+
gate. The cockpit was still sending you to the build host it was published from, which
|
|
7
|
+
is not where a licensee should land. One link, corrected.
|
|
8
|
+
|
|
9
|
+
Both hub addresses are also added to the list of hosts the product refuses to place a
|
|
10
|
+
client's status page on. That list exists because a client's page on a host we run would
|
|
11
|
+
mean we are holding a customer's data, and the hub moving is exactly the kind of change
|
|
12
|
+
that quietly leaves such a list out of date.
|
|
13
|
+
|
|
14
|
+
## 3.73.0 — the assessment, for Command OS licensees
|
|
15
|
+
|
|
16
|
+
An agency's first paid conversation with a prospect, and the document that comes out of
|
|
17
|
+
it. This is Command OS only: on the $97 licence these five tools answer with upgrade
|
|
18
|
+
information, and nothing about the GoHighLevel product changes.
|
|
19
|
+
|
|
20
|
+
You sit down with a business owner and go through forty-six questions across eleven
|
|
21
|
+
areas — what a job is worth, what happens to the phone, what happens after a quote goes
|
|
22
|
+
out, who is sitting in their database doing nothing. Each question has the words to say
|
|
23
|
+
out loud and a follow-up for when the answer is vague. At the end you have their numbers,
|
|
24
|
+
what those numbers are costing them each month, how many hours a week are going into work
|
|
25
|
+
a system should do, and a report you hand over with your name on it and nothing of ours.
|
|
26
|
+
|
|
27
|
+
Three rules are enforced in the code rather than left to good intentions, because all
|
|
28
|
+
three are the kind that quietly stop being true when a report needs to look impressive:
|
|
29
|
+
|
|
30
|
+
- **An answer nobody knows omits its finding.** It is never defaulted, estimated, or
|
|
31
|
+
filled in from an industry average. The report says which numbers were missing and what
|
|
32
|
+
to measure first.
|
|
33
|
+
- **Assumptions are yours and they print beside the figure they moved**, not in a footnote.
|
|
34
|
+
Set one to zero and its finding disappears rather than falling back to a default.
|
|
35
|
+
- **There is no minimum number of findings**, and "there is not much here" is a verdict the
|
|
36
|
+
tool will actually reach and say plainly. A report that always finds something will
|
|
37
|
+
invent something.
|
|
38
|
+
|
|
39
|
+
`save_assessment` puts the whole thing in **your own** GoHighLevel — the prospect as a
|
|
40
|
+
contact, the answers as a note you can read in plain English, the deal on an Assessments
|
|
41
|
+
pipeline. We store none of it. That is also what lets someone else on your team pick it
|
|
42
|
+
up: they open the GoHighLevel they already log into.
|
|
43
|
+
|
|
44
|
+
`read_assessment_transcript` turns a recording into answers, and refuses anything the
|
|
45
|
+
owner did not say: every answer must carry their verbatim words, and those words are
|
|
46
|
+
checked against the transcript. Anything worked out rather than heard — "two or three a
|
|
47
|
+
week" becoming eleven a month — is held for you to confirm.
|
|
48
|
+
|
|
49
|
+
`write_assessment_report` writes the finished document to your machine, self-contained so
|
|
50
|
+
it opens anywhere, with a random filename and no-index because it holds another business's
|
|
51
|
+
revenue and customer numbers. We publish it nowhere; the host is yours.
|
|
52
|
+
|
|
3
53
|
## 3.72.3 — the waits in a built account can actually go live
|
|
4
54
|
|
|
5
55
|
Blueprint builds a client's account and then asks whether to publish the workflows or
|