@elitedcs/ghl-mcp 3.96.0 → 3.97.0

package/skills/blueprint/presets/local-service.preset.json

@@ -1187,13 +1187,17 @@
           "callDirection": "inbound"
         },
         "stopOnResponse": true,
-        "_design": "Fires on an inbound call that was not answered (no-answer / busy / voicemail). Texts back within seconds, tags the contact, alerts a real person and creates a call-back task, then one more text an hour later. Stops the moment they reply.",
+        "_design": "Fires on an inbound call that was not answered (no-answer / busy / voicemail). Texts back within seconds, takes the missed-call tag off and puts it back on (so Missed Call - Pipeline Card starts on every missed call, W47), tags the contact, alerts a real person and creates a call-back task. W48 (2026-10-29): allowed to run again on every missed call; the closing 10-minute wait keeps the contact inside it, and GoHighLevel did not start it again for a contact still inside it (live call proof 2026-10-29), so a redial within 10 minutes gets no second text. The hour-later text is its own workflow, Missed Call - Follow-Up.",
         "actions": [
           {
             "type": "send_sms",
             "smsRef": "sms.mc_sms_1",
             "conditionalOn": "channels.sms == true"
           },
+          {
+            "type": "remove_contact_tag",
+            "tagRef": "tag.missed_call"
+          },
           {
             "type": "add_contact_tag",
             "tagRef": "tag.missed_call"
@@ -1217,26 +1221,21 @@
           },
           {
             "type": "wait",
-            "value": 1,
-            "unit": "hours"
-          },
-          {
-            "type": "send_sms",
-            "smsRef": "sms.mc_sms_2",
-            "conditionalOn": "channels.sms == true"
+            "value": 10,
+            "unit": "minutes"
           }
         ]
       },
       {
         "ref": "workflow.missed_call_card",
-        "allowMultiple": false,
+        "allowMultiple": true,
         "name": "Missed Call - Pipeline Card",
         "conditionalOn": "channels.sms == true",
         "trigger": {
           "type": "contact_tag",
           "tagRef": "tag.missed_call"
         },
-        "_design": "F6 (2026-10-29): a caller Missed Call Text-Back tagged missed-call, with no open card in this pipeline, gets one at the first stage, an owner and the new-lead tag, as a form lead does in Speed to Lead. A caller who already has a card keeps it. Its own workflow because find_opportunity must be the last step and cannot sit inside a shared account's If/Else gate.",
+        "_design": "W47 (2026-10-29 live call proof): started by the missed-call tag being added, and allowed to run again. The text-back takes the tag off and puts it straight back on every missed call, so the tag is newly added each time and a repeat caller is checked again (a contact who already had the tag, with re-entry off, never reached this workflow). A caller with no card in this pipeline gets one at the first stage, an owner and the new-lead tag, as a form lead does in Speed to Lead. A caller who already has a card in this pipeline keeps it and is tagged returning-caller. Not yet proven live: whether a closed (won or lost) card counts as found; Find Opportunity reads the latest card in the pipeline and the build sets no status filter. Started by the tag, not the call, because a shared account gates call-started workflows with an If/Else, and find_opportunity must be the last step and cannot sit inside one.",
         "actions": [
           {
             "type": "find_opportunity",
@@ -1266,6 +1265,35 @@
           }
         ]
       },
+      {
+        "ref": "workflow.missed_call_follow_up",
+        "allowMultiple": true,
+        "name": "Missed Call - Follow-Up",
+        "conditionalOn": "channels.sms == true",
+        "trigger": {
+          "type": "call_status",
+          "callStatuses": [
+            "no-answer",
+            "busy",
+            "voicemail"
+          ],
+          "callDirection": "inbound"
+        },
+        "stopOnResponse": true,
+        "_design": "W48 (2026-10-29): the hour-later text, split from the instant text-back so a second missed call inside the hour still gets an instant reply. Started by the same missed call; a redial while a contact is still waiting here gets no second follow-up. Stops the moment they reply.",
+        "actions": [
+          {
+            "type": "wait",
+            "value": 1,
+            "unit": "hours"
+          },
+          {
+            "type": "send_sms",
+            "smsRef": "sms.mc_sms_2",
+            "conditionalOn": "channels.sms == true"
+          }
+        ]
+      },
       {
         "ref": "workflow.lead_nurture",
         "allowMultiple": false,
@@ -1427,6 +1455,11 @@
             "workflowRef": "workflow.missed_call",
             "conditionalOn": "channels.sms == true"
           },
+          {
+            "type": "remove_from_workflow",
+            "workflowRef": "workflow.missed_call_follow_up",
+            "conditionalOn": "channels.sms == true"
+          },
           {
             "type": "remove_from_workflow",
             "workflowRef": "workflow.lead_nurture"
@@ -1568,6 +1601,11 @@
             "workflowRef": "workflow.missed_call",
             "conditionalOn": "channels.sms == true"
           },
+          {
+            "type": "remove_from_workflow",
+            "workflowRef": "workflow.missed_call_follow_up",
+            "conditionalOn": "channels.sms == true"
+          },
           {
             "type": "add_contact_tag",
             "tagRef": "tag.lc_booked"
@@ -1875,6 +1913,7 @@
         "blocks": [
           "workflow.speed_to_lead",
           "workflow.missed_call",
+          "workflow.missed_call_follow_up",
           "workflow.lead_nurture",
           "workflow.win_back",
           "workflow.appointment_booked",
@@ -1934,6 +1973,7 @@
         "blocks": [
           "workflow.speed_to_lead",
           "workflow.missed_call",
+          "workflow.missed_call_follow_up",
           "workflow.lead_nurture",
           "workflow.win_back",
           "workflow.appointment_booked",
@@ -1961,6 +2001,18 @@
         ],
         "_blocksNote": "Lists every SMS-bearing WORKFLOW ref (so they stay DRAFT) plus the sms.* asset refs. After conditional pruning, drop any entry whose workflow/asset was removed."
       },
+      {
+        "ref": "handoff.stop_line_check",
+        "conditionalOn": "channels.sms == true",
+        "owner": "OPERATOR-UI",
+        "title": "Check whether the account adds its own Reply STOP line",
+        "trigger": "channels.sms == true",
+        "instruction": "Your GoHighLevel account may already add its own 'Reply STOP' line to the first text each contact gets. If it does, a contact may see the opt-out line twice on that first text. That is safe. Remove the build's own line from a text only if you are sure the account's own line is switched on.",
+        "produces": null,
+        "successCheck": "You know whether the account adds its own Reply STOP line to first texts",
+        "blocks": [],
+        "_design": "W49 (command-center ruling 2026-10-30): a doubled opt-out line is cosmetic, a missing one is a compliance failure, so the build keeps its own STOP line and says so. No settings path is named because none has been seen on screen; the setting is to be checked live later."
+      },
       {
         "ref": "handoff.stripe",
         "conditionalOn": "flags includes stripe_not_connected",

package/skills/blueprint/presets/med-spa.preset.json

@@ -1163,13 +1163,17 @@
           "callDirection": "inbound"
         },
         "stopOnResponse": true,
-        "_design": "Fires on an inbound call that was not answered (no-answer / busy / voicemail). Texts back within seconds, tags the contact, alerts a real person and creates a call-back task, then one more text an hour later. Stops the moment they reply.",
+        "_design": "Fires on an inbound call that was not answered (no-answer / busy / voicemail). Texts back within seconds, takes the missed-call tag off and puts it back on (so Missed Call - Pipeline Card starts on every missed call, W47), tags the contact, alerts a real person and creates a call-back task. W48 (2026-10-29): allowed to run again on every missed call; the closing 10-minute wait keeps the contact inside it, and GoHighLevel did not start it again for a contact still inside it (live call proof 2026-10-29), so a redial within 10 minutes gets no second text. The hour-later text is its own workflow, Missed Call - Follow-Up.",
         "actions": [
           {
             "type": "send_sms",
             "smsRef": "sms.mc_sms_1",
             "conditionalOn": "channels.sms == true"
           },
+          {
+            "type": "remove_contact_tag",
+            "tagRef": "tag.missed_call"
+          },
           {
             "type": "add_contact_tag",
             "tagRef": "tag.missed_call"
@@ -1193,26 +1197,21 @@
           },
           {
             "type": "wait",
-            "value": 1,
-            "unit": "hours"
-          },
-          {
-            "type": "send_sms",
-            "smsRef": "sms.mc_sms_2",
-            "conditionalOn": "channels.sms == true"
+            "value": 10,
+            "unit": "minutes"
           }
         ]
       },
       {
         "ref": "workflow.missed_call_card",
-        "allowMultiple": false,
+        "allowMultiple": true,
         "name": "Missed Call - Pipeline Card",
         "conditionalOn": "channels.sms == true",
         "trigger": {
           "type": "contact_tag",
           "tagRef": "tag.missed_call"
         },
-        "_design": "F6 (2026-10-29): a caller Missed Call Text-Back tagged missed-call, with no open card in this pipeline, gets one at the first stage, an owner and the new-lead tag, as a form lead does in Speed to Lead. A caller who already has a card keeps it. Its own workflow because find_opportunity must be the last step and cannot sit inside a shared account's If/Else gate.",
+        "_design": "W47 (2026-10-29 live call proof): started by the missed-call tag being added, and allowed to run again. The text-back takes the tag off and puts it straight back on every missed call, so the tag is newly added each time and a repeat caller is checked again (a contact who already had the tag, with re-entry off, never reached this workflow). A caller with no card in this pipeline gets one at the first stage, an owner and the new-lead tag, as a form lead does in Speed to Lead. A caller who already has a card in this pipeline keeps it and is tagged returning-caller. Not yet proven live: whether a closed (won or lost) card counts as found; Find Opportunity reads the latest card in the pipeline and the build sets no status filter. Started by the tag, not the call, because a shared account gates call-started workflows with an If/Else, and find_opportunity must be the last step and cannot sit inside one.",
         "actions": [
           {
             "type": "find_opportunity",
@@ -1242,6 +1241,35 @@
           }
         ]
       },
+      {
+        "ref": "workflow.missed_call_follow_up",
+        "allowMultiple": true,
+        "name": "Missed Call - Follow-Up",
+        "conditionalOn": "channels.sms == true",
+        "trigger": {
+          "type": "call_status",
+          "callStatuses": [
+            "no-answer",
+            "busy",
+            "voicemail"
+          ],
+          "callDirection": "inbound"
+        },
+        "stopOnResponse": true,
+        "_design": "W48 (2026-10-29): the hour-later text, split from the instant text-back so a second missed call inside the hour still gets an instant reply. Started by the same missed call; a redial while a contact is still waiting here gets no second follow-up. Stops the moment they reply.",
+        "actions": [
+          {
+            "type": "wait",
+            "value": 1,
+            "unit": "hours"
+          },
+          {
+            "type": "send_sms",
+            "smsRef": "sms.mc_sms_2",
+            "conditionalOn": "channels.sms == true"
+          }
+        ]
+      },
       {
         "ref": "workflow.lead_nurture",
         "allowMultiple": false,
@@ -1403,6 +1431,11 @@
             "workflowRef": "workflow.missed_call",
             "conditionalOn": "channels.sms == true"
           },
+          {
+            "type": "remove_from_workflow",
+            "workflowRef": "workflow.missed_call_follow_up",
+            "conditionalOn": "channels.sms == true"
+          },
           {
             "type": "remove_from_workflow",
             "workflowRef": "workflow.lead_nurture"
@@ -1544,6 +1577,11 @@
             "workflowRef": "workflow.missed_call",
             "conditionalOn": "channels.sms == true"
           },
+          {
+            "type": "remove_from_workflow",
+            "workflowRef": "workflow.missed_call_follow_up",
+            "conditionalOn": "channels.sms == true"
+          },
           {
             "type": "add_contact_tag",
             "tagRef": "tag.lc_booked"
@@ -1851,6 +1889,7 @@
         "blocks": [
           "workflow.speed_to_lead",
           "workflow.missed_call",
+          "workflow.missed_call_follow_up",
           "workflow.lead_nurture",
           "workflow.win_back",
           "workflow.appointment_booked",
@@ -1910,6 +1949,7 @@
         "blocks": [
           "workflow.speed_to_lead",
           "workflow.missed_call",
+          "workflow.missed_call_follow_up",
           "workflow.lead_nurture",
           "workflow.win_back",
           "workflow.appointment_booked",
@@ -1937,6 +1977,18 @@
         ],
         "_blocksNote": "Lists every SMS-bearing WORKFLOW ref (so they stay DRAFT) plus the sms.* asset refs. After conditional pruning, drop any entry whose workflow/asset was removed."
       },
+      {
+        "ref": "handoff.stop_line_check",
+        "conditionalOn": "channels.sms == true",
+        "owner": "OPERATOR-UI",
+        "title": "Check whether the account adds its own Reply STOP line",
+        "trigger": "channels.sms == true",
+        "instruction": "Your GoHighLevel account may already add its own 'Reply STOP' line to the first text each contact gets. If it does, a contact may see the opt-out line twice on that first text. That is safe. Remove the build's own line from a text only if you are sure the account's own line is switched on.",
+        "produces": null,
+        "successCheck": "You know whether the account adds its own Reply STOP line to first texts",
+        "blocks": [],
+        "_design": "W49 (command-center ruling 2026-10-30): a doubled opt-out line is cosmetic, a missing one is a compliance failure, so the build keeps its own STOP line and says so. No settings path is named because none has been seen on screen; the setting is to be checked live later."
+      },
       {
         "ref": "handoff.stripe",
         "conditionalOn": "flags includes stripe_not_connected",

package/skills/blueprint/presets/wellness-clinic.preset.json

@@ -2345,13 +2345,17 @@
         },
         "stopOnResponse": true,
         "_source": "[NO REAL SOURCE: proposed] No live account has a missed-call text-back. Med-spa's 7-action shape.",
-        "_design": "An unanswered inbound call gets a text within seconds offering the trial link, a person is alerted with a call-back task, and the link follows an hour later. Stops on reply.",
+        "_design": "Fires on an inbound call that was not answered (no-answer / busy / voicemail). Texts back within seconds, takes the missed-call tag off and puts it back on (so Missed Call - Pipeline Card starts on every missed call, W47), tags the contact, alerts a real person and creates a call-back task. W48 (2026-10-29): allowed to run again on every missed call; the closing 10-minute wait keeps the contact inside it, and GoHighLevel did not start it again for a contact still inside it (live call proof 2026-10-29), so a redial within 10 minutes gets no second text. The hour-later text is its own workflow, Missed Call - Follow-Up.",
         "actions": [
           {
             "type": "send_sms",
             "smsRef": "sms.mc_sms_1",
             "conditionalOn": "channels.sms == true"
           },
+          {
+            "type": "remove_contact_tag",
+            "tagRef": "tag.missed_call"
+          },
           {
             "type": "add_contact_tag",
             "tagRef": "tag.missed_call"
@@ -2375,26 +2379,21 @@
           },
           {
             "type": "wait",
-            "value": 1,
-            "unit": "hours"
-          },
-          {
-            "type": "send_sms",
-            "smsRef": "sms.mc_sms_2",
-            "conditionalOn": "channels.sms == true"
+            "value": 10,
+            "unit": "minutes"
           }
         ]
       },
       {
         "ref": "workflow.missed_call_card",
-        "allowMultiple": false,
+        "allowMultiple": true,
         "name": "Missed Call - Pipeline Card",
         "conditionalOn": "channels.sms == true",
         "trigger": {
           "type": "contact_tag",
           "tagRef": "tag.missed_call"
         },
-        "_design": "F6 (2026-10-29): a caller Missed Call Text-Back tagged missed-call, with no open card in this pipeline, gets one at the first stage, an owner and the new-lead tag, as a form lead does in Speed to Lead. A caller who already has a card keeps it. Its own workflow because find_opportunity must be the last step and cannot sit inside a shared account's If/Else gate.",
+        "_design": "W47 (2026-10-29 live call proof): started by the missed-call tag being added, and allowed to run again. The text-back takes the tag off and puts it straight back on every missed call, so the tag is newly added each time and a repeat caller is checked again (a contact who already had the tag, with re-entry off, never reached this workflow). A caller with no card in this pipeline gets one at the first stage, an owner and the new-lead tag, as a form lead does in Speed to Lead. A caller who already has a card in this pipeline keeps it and is tagged returning-caller. Not yet proven live: whether a closed (won or lost) card counts as found; Find Opportunity reads the latest card in the pipeline and the build sets no status filter. Started by the tag, not the call, because a shared account gates call-started workflows with an If/Else, and find_opportunity must be the last step and cannot sit inside one.",
         "actions": [
           {
             "type": "find_opportunity",
@@ -2424,6 +2423,35 @@
           }
         ]
       },
+      {
+        "ref": "workflow.missed_call_follow_up",
+        "allowMultiple": true,
+        "name": "Missed Call - Follow-Up",
+        "conditionalOn": "channels.sms == true",
+        "trigger": {
+          "type": "call_status",
+          "callStatuses": [
+            "no-answer",
+            "busy",
+            "voicemail"
+          ],
+          "callDirection": "inbound"
+        },
+        "stopOnResponse": true,
+        "_design": "W48 (2026-10-29): the hour-later text, split from the instant text-back so a second missed call inside the hour still gets an instant reply. Started by the same missed call; a redial while a contact is still waiting here gets no second follow-up. Stops the moment they reply.",
+        "actions": [
+          {
+            "type": "wait",
+            "value": 1,
+            "unit": "hours"
+          },
+          {
+            "type": "send_sms",
+            "smsRef": "sms.mc_sms_2",
+            "conditionalOn": "channels.sms == true"
+          }
+        ]
+      },
       {
         "ref": "workflow.lead_nurture",
         "allowMultiple": false,
@@ -2673,6 +2701,11 @@
             "workflowRef": "workflow.missed_call",
             "conditionalOn": "channels.sms == true"
           },
+          {
+            "type": "remove_from_workflow",
+            "workflowRef": "workflow.missed_call_follow_up",
+            "conditionalOn": "channels.sms == true"
+          },
           {
             "type": "remove_from_workflow",
             "workflowRef": "workflow.lead_nurture"
@@ -3058,6 +3091,11 @@
             "workflowRef": "workflow.missed_call",
             "conditionalOn": "channels.sms == true"
           },
+          {
+            "type": "remove_from_workflow",
+            "workflowRef": "workflow.missed_call_follow_up",
+            "conditionalOn": "channels.sms == true"
+          },
           {
             "type": "add_contact_tag",
             "tagRef": "tag.lc_trial_booked"
@@ -3649,6 +3687,7 @@
         "blocks": [
           "workflow.speed_to_lead",
           "workflow.missed_call",
+          "workflow.missed_call_follow_up",
           "workflow.lead_nurture",
           "workflow.book_reply",
           "workflow.win_back",
@@ -3877,6 +3916,7 @@
         "blocks": [
           "workflow.speed_to_lead",
           "workflow.missed_call",
+          "workflow.missed_call_follow_up",
           "workflow.lead_nurture",
           "workflow.book_reply",
           "workflow.win_back",
@@ -3941,6 +3981,18 @@
           "sms.review_sms_1"
         ]
       },
+      {
+        "ref": "handoff.stop_line_check",
+        "conditionalOn": "channels.sms == true",
+        "owner": "OPERATOR-UI",
+        "title": "Check whether the account adds its own Reply STOP line",
+        "trigger": "channels.sms == true",
+        "instruction": "Your GoHighLevel account may already add its own 'Reply STOP' line to the first text each contact gets. If it does, a contact may see the opt-out line twice on that first text. That is safe. Remove the build's own line from a text only if you are sure the account's own line is switched on.",
+        "produces": null,
+        "successCheck": "You know whether the account adds its own Reply STOP line to first texts",
+        "blocks": [],
+        "_design": "W49 (command-center ruling 2026-10-30): a doubled opt-out line is cosmetic, a missing one is a compliance failure, so the build keeps its own STOP line and says so. No settings path is named because none has been seen on screen; the setting is to be checked live later."
+      },
       {
         "ref": "handoff.email_domain",
         "conditionalOn": "flags includes email_domain_needed",

package/skills/blueprint/references/copy-guide.md

@@ -102,7 +102,7 @@ Replace with a specific: what happened, what we noticed, what we can do, what to
 | Sequence | Touches | Span | Shape |
 |---|---|---|---|
 | Speed to Lead | 5 (3 texts, 2 emails) | 24 hours | instant text + email, call task, +20 min text (binary question), +3 h email (what happens next), +1 day text (not chasing), then the `nurture-start` hand-off as the LAST action |
-| Missed Call Text-Back | 2 texts | 1 hour | instant text-back (how can we help), tag, alert, call-back task, +1 h text (call-back time or booking link) |
+| Missed Call Text-Back + Missed Call - Follow-Up | 2 texts | 1 hour | instant text-back (how can we help), tag, alert, call-back task (at most once per 10 minutes per caller); the +1 h text (call-back time or booking link) is its own workflow, so a second missed call inside the hour still gets the instant text |
 | Lead Nurture (30 days) | 11 (6 emails, 5 texts) | 31 days of waits | day 1 reframe, 3 one-word question, 5 how it works + top objection, 8 free tip, 10 method as proof, 14 price/time head-on, 15 midpoint binary, 20 cost of waiting, 23 any question, 27 decision sheet, 30 last direct ask, then `lifecycle-lapsed` + `winback-start` |
 | Win-back (30 days) | 5 (3 emails, 2 texts) | 31 days of waits | day 0 one question, 7 binary text, 14 what changed, 22 concrete reason text, 30 the door stays open (says it is the last automatic message), then `lifecycle-lost` |
 | Appointment | confirm email + text; 24 h text + prep email; 2 h text | appointment-relative | confirmation restates time, what to bring, what they leave with, how to move it |