@elitedcs/ghl-mcp 3.93.1 → 3.94.0

package/guide/guide.html

@@ -4,7 +4,7 @@
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>GHL Command — User Guide</title>
-<!-- guides-hash: 00c802d51fe5e825 -->
+<!-- guides-hash: a0d59993c2403c19 -->
 <style>
 /* Deliberately light in every environment, including a dark-mode OS. This is a
    reference document people read at length, print, and save to PDF, and a page
@@ -1281,11 +1281,11 @@ Before you build: look up the real calendar, the real workflows you are removing
 <p class="gpara">Have these ready before you connect.</p>
 <ul>
 <li>A Google account with a calendar you can read.</li>
-<li>Google sign-in configured for this installation; Connect will tell you if it is unavailable.</li>
+<li>Google sign-in for GHL Command, which is not available yet.</li>
 </ul>
 <h3>How to connect</h3>
 <p class="gpara">Follow these steps to give this machine access.</p>
-<p class="gpara">Once Google sign-in is set up on this computer:</p>
+<p class="gpara">Google Calendar connect is not available yet. Choosing Connect says so and saves nothing. When Google sign-in arrives in an update, these are the steps:</p>
 <h4>3 steps</h4>
 <ol class="steps">
 <li>On the Google Calendar card on the Connections screen, choose Connect to open Google sign-in.</li>
@@ -1294,11 +1294,6 @@ Before you build: look up the real calendar, the real workflows you are removing
 </ol>
 <h3>What to say</h3>
 <p class="gpara">In a Claude chat you can say one of these to connect or use it.</p>
-<ul>
-<li>“Connect my own Google Calendar.”</li>
-<li>“Finish connecting my Google Calendar.”</li>
-<li>“Read my calendar for today.”</li>
-</ul>
 <h3>How to take access back</h3>
 <p class="gpara">Remove the saved connection or take back the provider's permission.</p>
 <p class="gpara">Choose Disconnect on this system's Connections card to remove the saved sign-in and request revocation with Google. You can also remove the app in your Google Account's third-party connections at myaccount.google.com/connections.</p>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elitedcs/ghl-mcp",
-  "version": "3.93.1",
+  "version": "3.94.0",
   "mcpName": "io.github.drjerryrelth/ghl-command",
   "description": "GoHighLevel MCP Server for Claude. 250 tools for CRM, automation and marketing, an account-wide workflow audit, live funnel-capture verification and a workflow builder, across client accounts.",
   "main": "dist/index.js",

package/skills/blueprint/examples/validate-plan.cjs

@@ -40,6 +40,15 @@ function resolvePreset(preset) {
     }
     return v;
   };
+  // A hand-off may come in two versions of one ref only when their conditions are exact opposites (identical except
+  // one "==" turned "!="), so exactly one reaches any plan: the texting-on and texting-off wording of the same job
+  // (ask first, 2026-10-29). The maximal plan keeps the first; any other repeat is still a duplicate below.
+  if (Array.isArray(sk.handoffs)) {
+    const parts = (h) => (typeof h.conditionalOn === 'string' ? h.conditionalOn.split(/(==|!=)/) : null);
+    const opposite = (x, y) => { const a = parts(x), b = parts(y); return !!a && !!b && a.length === b.length && a.filter((t, i) => t !== b[i]).length === 1 && a.every((t, i) => t === b[i] || (/^[!=]=$/.test(t) && /^[!=]=$/.test(b[i]))); };
+    const count = (ref) => sk.handoffs.filter((e) => e.ref === ref).length;
+    sk.handoffs = sk.handoffs.filter((h, i) => !(count(h.ref) === 2 && sk.handoffs.slice(0, i).some((e) => e.ref === h.ref && opposite(e, h))));
+  }
   const plan = strip(sk);
   plan.schemaVersion = preset.schemaVersion;
   plan.planId = `preset:${preset.presetId}`;

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

@@ -238,6 +238,11 @@
         "name": "missed-call",
         "conditionalOn": "channels.sms == true"
       },
+      {
+        "ref": "tag.returning_caller",
+        "name": "returning-caller",
+        "conditionalOn": "channels.sms == true"
+      },
       {
         "ref": "tag.no_show",
         "name": "no-show",
@@ -1217,6 +1222,45 @@
           }
         ]
       },
+      {
+        "ref": "workflow.missed_call_card",
+        "allowMultiple": false,
+        "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.",
+        "actions": [
+          {
+            "type": "find_opportunity",
+            "pipelineRef": "pipeline.patients",
+            "found": [
+              {
+                "type": "add_contact_tag",
+                "tagRef": "tag.returning_caller"
+              }
+            ],
+            "notFound": [
+              {
+                "type": "add_contact_tag",
+                "tagRef": "tag.lc_new_lead"
+              },
+              {
+                "type": "create_opportunity",
+                "pipelineRef": "pipeline.patients",
+                "stageRef": "stage.new_lead",
+                "name": "{{contact.name}} - Missed Call"
+              },
+              {
+                "type": "assign_user",
+                "userRef": "user.owner"
+              }
+            ]
+          }
+        ]
+      },
       {
         "ref": "workflow.lead_nurture",
         "allowMultiple": false,
@@ -1857,7 +1901,7 @@
         "owner": "OPERATOR-UI",
         "title": "Confirm your business phone and the name messages are signed with",
         "trigger": "always (30 seconds)",
-        "instruction": "Settings > Custom Values: set business_phone to the number customers should call or text back, and owner_first_name to the first name every email is signed with. The build pre-fills both from the intake when it can.",
+        "instruction": "Settings > Custom Values: set business_phone to the number customers should call, and owner_first_name to the first name every email is signed with. The build pre-fills both from the intake when it can.",
         "produces": "cv.owner_first_name",
         "successCheck": "business_phone and owner_first_name show real values, not blanks",
         "blocks": [
@@ -1936,7 +1980,7 @@
         "trigger": "always, before publishing",
         "instruction": "Open Marketing > Emails > Templates and Conversations > Snippets. The copy never names a condition, diagnosis, treatment or medication; confirm your edits keep it that way and match your own compliance rules (privacy, state advertising rules, insurance language). Ten minutes now saves a complaint later.",
         "produces": null,
-        "successCheck": "Every template read by a responsible person; no clinical detail in any text or email",
+        "successCheck": "Every template read by a responsible person; no clinical detail in any message",
         "blocks": [
           "workflow.speed_to_lead",
           "workflow.lead_nurture",
@@ -1989,7 +2033,7 @@
         "owner": "OPERATOR-UI",
         "title": "Paste the Google review link so review requests point somewhere",
         "trigger": "always (2 minutes)",
-        "instruction": "In Google Business Profile, open the profile, choose Ask for reviews and copy the short link. Then in the sub-account: Settings > Custom Values: set review_link to that link. Until it is set, the Review Request workflow sends a text with no link, so do this before the first visit is marked showed.",
+        "instruction": "In Google Business Profile, open the profile, choose Ask for reviews and copy the short link. Then in the sub-account: Settings > Custom Values: set review_link to that link. Until it is set, the Review Request workflow sends its message with no link, so do this before the first visit is marked showed.",
         "produces": "cv.review_link",
         "successCheck": "review_link shows a real https link, not a blank",
         "blocks": [
@@ -2003,7 +2047,7 @@
         "title": "Start Review Request by tagging service-complete when the work is done",
         "trigger": "always (1 minute to read)",
         "instruction": "The intake chose to ask for a review when the work is done, so Review Request starts from the tag service-complete, not from a visit. Add that tag on the contact when their care is finished. Each patient is asked for a review once.",
-        "successCheck": "A contact tagged service-complete receives the review text two hours later"
+        "successCheck": "A contact tagged service-complete receives the review request two hours later"
       },
       {
         "ref": "handoff.quote_tag",
@@ -2011,7 +2055,7 @@
         "title": "Start Quote Follow-up by tagging quote-sent when a treatment plan goes out",
         "trigger": "always (1 minute to read)",
         "instruction": "Quote Follow-up starts from the tag quote-sent. Add that tag to the contact whenever a treatment plan goes out: by hand on the contact, or, if the treatment plans are sent as GoHighLevel estimates, build one workflow in the UI with the Estimate trigger (status sent) whose only step adds the tag quote-sent. The follow-up removes the tag itself, so the next treatment plan starts it again.",
-        "successCheck": "A contact tagged quote-sent receives the next-day text"
+        "successCheck": "A contact tagged quote-sent receives the first follow-up message"
       }
     ]
   }

package/skills/blueprint/presets/coach.preset.json

@@ -239,6 +239,11 @@
         "name": "missed-call",
         "conditionalOn": "channels.sms == true"
       },
+      {
+        "ref": "tag.returning_caller",
+        "name": "returning-caller",
+        "conditionalOn": "channels.sms == true"
+      },
       {
         "ref": "tag.no_show",
         "name": "no-show",
@@ -1212,6 +1217,45 @@
           }
         ]
       },
+      {
+        "ref": "workflow.missed_call_card",
+        "allowMultiple": false,
+        "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.",
+        "actions": [
+          {
+            "type": "find_opportunity",
+            "pipelineRef": "pipeline.client_journey",
+            "found": [
+              {
+                "type": "add_contact_tag",
+                "tagRef": "tag.returning_caller"
+              }
+            ],
+            "notFound": [
+              {
+                "type": "add_contact_tag",
+                "tagRef": "tag.lc_new_lead"
+              },
+              {
+                "type": "create_opportunity",
+                "pipelineRef": "pipeline.client_journey",
+                "stageRef": "stage.new_lead",
+                "name": "{{contact.name}} - Missed Call"
+              },
+              {
+                "type": "assign_user",
+                "userRef": "user.owner"
+              }
+            ]
+          }
+        ]
+      },
       {
         "ref": "workflow.lead_nurture",
         "allowMultiple": false,
@@ -1835,7 +1879,7 @@
         "owner": "OPERATOR-UI",
         "title": "Confirm your business phone and the name messages are signed with",
         "trigger": "always (30 seconds)",
-        "instruction": "Settings > Custom Values: set business_phone to the number customers should call or text back, and owner_first_name to the first name every email is signed with. The build pre-fills both from the intake when it can.",
+        "instruction": "Settings > Custom Values: set business_phone to the number customers should call, and owner_first_name to the first name every email is signed with. The build pre-fills both from the intake when it can.",
         "produces": "cv.owner_first_name",
         "successCheck": "business_phone and owner_first_name show real values, not blanks",
         "blocks": [
@@ -1952,7 +1996,7 @@
         "owner": "OPERATOR-UI",
         "title": "Paste the Google review link so review requests point somewhere",
         "trigger": "always (2 minutes)",
-        "instruction": "In Google Business Profile, open the profile, choose Ask for reviews and copy the short link. Then in the sub-account: Settings > Custom Values: set review_link to that link. Until it is set, the Review Request workflow sends a text with no link, so do this before the first call is marked showed.",
+        "instruction": "In Google Business Profile, open the profile, choose Ask for reviews and copy the short link. Then in the sub-account: Settings > Custom Values: set review_link to that link. Until it is set, the Review Request workflow sends its message with no link, so do this before the first call is marked showed.",
         "produces": "cv.review_link",
         "successCheck": "review_link shows a real https link, not a blank",
         "blocks": [
@@ -1965,7 +2009,7 @@
         "title": "Start Quote Follow-up by tagging quote-sent when a proposal goes out",
         "trigger": "always (1 minute to read)",
         "instruction": "Quote Follow-up starts from the tag quote-sent. Add that tag to the contact whenever a proposal goes out: by hand on the contact, or, if the proposals are sent as GoHighLevel estimates, build one workflow in the UI with the Estimate trigger (status sent) whose only step adds the tag quote-sent. The follow-up removes the tag itself, so the next proposal starts it again.",
-        "successCheck": "A contact tagged quote-sent receives the next-day text"
+        "successCheck": "A contact tagged quote-sent receives the first follow-up message"
       },
       {
         "ref": "handoff.review_tag",
@@ -1973,7 +2017,7 @@
         "title": "Start Review Request by tagging service-complete when the work is done",
         "trigger": "always (1 minute to read)",
         "instruction": "Review Request starts from the tag service-complete. Add that tag when the job is finished and paid for: by hand on the contact, or from the pipeline's won stage with one small workflow whose only step adds the tag. It never starts from a consult, estimate or discovery call, so nobody who did not buy is asked for a review.",
-        "successCheck": "A contact tagged service-complete receives the review text two hours later"
+        "successCheck": "A contact tagged service-complete receives the review request two hours later"
       }
     ]
   }

package/skills/blueprint/presets/ecommerce.preset.json

@@ -219,6 +219,11 @@
         "name": "missed-call",
         "conditionalOn": "channels.sms == true"
       },
+      {
+        "ref": "tag.returning_caller",
+        "name": "returning-caller",
+        "conditionalOn": "channels.sms == true"
+      },
       {
         "ref": "tag.interest_best_sellers",
         "name": "interest-best-sellers"
@@ -953,6 +958,45 @@
           }
         ]
       },
+      {
+        "ref": "workflow.missed_call_card",
+        "allowMultiple": false,
+        "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.",
+        "actions": [
+          {
+            "type": "find_opportunity",
+            "pipelineRef": "pipeline.store_leads",
+            "found": [
+              {
+                "type": "add_contact_tag",
+                "tagRef": "tag.returning_caller"
+              }
+            ],
+            "notFound": [
+              {
+                "type": "add_contact_tag",
+                "tagRef": "tag.lc_new_lead"
+              },
+              {
+                "type": "create_opportunity",
+                "pipelineRef": "pipeline.store_leads",
+                "stageRef": "stage.new_subscriber",
+                "name": "{{contact.name}} - Missed Call"
+              },
+              {
+                "type": "assign_user",
+                "userRef": "user.owner"
+              }
+            ]
+          }
+        ]
+      },
       {
         "ref": "workflow.lead_nurture",
         "allowMultiple": false,
@@ -1308,7 +1352,7 @@
         "owner": "OPERATOR-UI",
         "title": "Confirm your business phone and the name messages are signed with",
         "trigger": "always (30 seconds)",
-        "instruction": "Settings > Custom Values: set business_phone to the number customers should call or text back, and owner_first_name to the first name every email is signed with. The build pre-fills both from the intake when it can.",
+        "instruction": "Settings > Custom Values: set business_phone to the number customers should call, and owner_first_name to the first name every email is signed with. The build pre-fills both from the intake when it can.",
         "produces": "cv.owner_first_name",
         "successCheck": "business_phone and owner_first_name show real values, not blanks",
         "blocks": [
@@ -1402,7 +1446,7 @@
         "trigger": "always",
         "instruction": "In your Google Business Profile, open Ask for reviews and copy the short link. Paste it into the review_link custom value. From then on, add the tag review-ask to a contact when an order has arrived (or automate it from the stage you use for finished work); the requests start from the tag and stop the moment they reply.",
         "produces": "cv.review_link",
-        "successCheck": "The review_link custom value opens your Google review form, and a test contact tagged review-ask receives the first text two hours later",
+        "successCheck": "The review_link custom value opens your Google review form, and a test contact tagged review-ask receives the first review request two hours later",
         "blocks": [
           "cv.review_link"
         ]

package/skills/blueprint/presets/generic-client.preset.json

@@ -222,6 +222,11 @@
         "name": "missed-call",
         "conditionalOn": "channels.sms == true"
       },
+      {
+        "ref": "tag.returning_caller",
+        "name": "returning-caller",
+        "conditionalOn": "channels.sms == true"
+      },
       {
         "ref": "tag.no_show",
         "name": "no-show",
@@ -1209,6 +1214,45 @@
           }
         ]
       },
+      {
+        "ref": "workflow.missed_call_card",
+        "allowMultiple": false,
+        "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.",
+        "actions": [
+          {
+            "type": "find_opportunity",
+            "pipelineRef": "pipeline.main",
+            "found": [
+              {
+                "type": "add_contact_tag",
+                "tagRef": "tag.returning_caller"
+              }
+            ],
+            "notFound": [
+              {
+                "type": "add_contact_tag",
+                "tagRef": "tag.lc_new_lead"
+              },
+              {
+                "type": "create_opportunity",
+                "pipelineRef": "pipeline.main",
+                "stageRef": "stage.new_lead",
+                "name": "{{contact.name}} - Missed Call"
+              },
+              {
+                "type": "assign_user",
+                "userRef": "user.owner"
+              }
+            ]
+          }
+        ]
+      },
       {
         "ref": "workflow.lead_nurture",
         "allowMultiple": false,
@@ -1856,7 +1900,7 @@
         "owner": "OPERATOR-UI",
         "title": "Confirm your business phone and the name messages are signed with",
         "trigger": "always (30 seconds)",
-        "instruction": "Settings > Custom Values: set business_phone to the number customers should call or text back, and owner_first_name to the first name every email is signed with. The build pre-fills both from the intake when it can.",
+        "instruction": "Settings > Custom Values: set business_phone to the number customers should call, and owner_first_name to the first name every email is signed with. The build pre-fills both from the intake when it can.",
         "produces": "cv.owner_first_name",
         "successCheck": "business_phone and owner_first_name show real values, not blanks",
         "blocks": [
@@ -1977,7 +2021,7 @@
         "trigger": "always",
         "instruction": "In your Google Business Profile, open Ask for reviews and copy the short link. Paste it into the review_link custom value. From then on, add the tag review-ask to a contact when the work is done (or automate it from the stage you use for finished work); the requests start from the tag and stop the moment they reply.",
         "produces": "cv.review_link",
-        "successCheck": "The review_link custom value opens your Google review form, and a test contact tagged review-ask receives the first text two hours later",
+        "successCheck": "The review_link custom value opens your Google review form, and a test contact tagged review-ask receives the first review request two hours later",
         "blocks": [
           "cv.review_link"
         ]
@@ -1989,7 +2033,7 @@
         "trigger": "always",
         "instruction": "When a quote goes out, add the tag quote-sent to the contact, by hand or automated from your quoting tool or a pipeline stage. The follow-up starts from the tag, asks one thing per touch, and stops the moment they reply.",
         "produces": null,
-        "successCheck": "A test contact tagged quote-sent receives the first text one day later",
+        "successCheck": "A test contact tagged quote-sent receives the first follow-up message",
         "blocks": []
       }
     ]

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

@@ -244,6 +244,11 @@
         "name": "missed-call",
         "conditionalOn": "channels.sms == true"
       },
+      {
+        "ref": "tag.returning_caller",
+        "name": "returning-caller",
+        "conditionalOn": "channels.sms == true"
+      },
       {
         "ref": "tag.no_show",
         "name": "no-show",
@@ -1222,6 +1227,45 @@
           }
         ]
       },
+      {
+        "ref": "workflow.missed_call_card",
+        "allowMultiple": false,
+        "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.",
+        "actions": [
+          {
+            "type": "find_opportunity",
+            "pipelineRef": "pipeline.jobs",
+            "found": [
+              {
+                "type": "add_contact_tag",
+                "tagRef": "tag.returning_caller"
+              }
+            ],
+            "notFound": [
+              {
+                "type": "add_contact_tag",
+                "tagRef": "tag.lc_new_lead"
+              },
+              {
+                "type": "create_opportunity",
+                "pipelineRef": "pipeline.jobs",
+                "stageRef": "stage.new_lead",
+                "name": "{{contact.name}} - Missed Call"
+              },
+              {
+                "type": "assign_user",
+                "userRef": "user.owner"
+              }
+            ]
+          }
+        ]
+      },
       {
         "ref": "workflow.lead_nurture",
         "allowMultiple": false,
@@ -1845,7 +1889,7 @@
         "owner": "OPERATOR-UI",
         "title": "Confirm your business phone and the name messages are signed with",
         "trigger": "always (30 seconds)",
-        "instruction": "Settings > Custom Values: set business_phone to the number customers should call or text back, and owner_first_name to the first name every email is signed with. The build pre-fills both from the intake when it can.",
+        "instruction": "Settings > Custom Values: set business_phone to the number customers should call, and owner_first_name to the first name every email is signed with. The build pre-fills both from the intake when it can.",
         "produces": "cv.owner_first_name",
         "successCheck": "business_phone and owner_first_name show real values, not blanks",
         "blocks": [
@@ -1962,7 +2006,7 @@
         "owner": "OPERATOR-UI",
         "title": "Paste the Google review link so review requests point somewhere",
         "trigger": "always (2 minutes)",
-        "instruction": "In Google Business Profile, open the profile, choose Ask for reviews and copy the short link. Then in the sub-account: Settings > Custom Values: set review_link to that link. Until it is set, the Review Request workflow sends a text with no link, so do this before the first appointment is marked showed.",
+        "instruction": "In Google Business Profile, open the profile, choose Ask for reviews and copy the short link. Then in the sub-account: Settings > Custom Values: set review_link to that link. Until it is set, the Review Request workflow sends its message with no link, so do this before the first appointment is marked showed.",
         "produces": "cv.review_link",
         "successCheck": "review_link shows a real https link, not a blank",
         "blocks": [
@@ -1975,7 +2019,7 @@
         "title": "Start Quote Follow-up by tagging quote-sent when a quote goes out",
         "trigger": "always (1 minute to read)",
         "instruction": "Quote Follow-up starts from the tag quote-sent. Add that tag to the contact whenever a quote goes out: by hand on the contact, or, if the quotes are sent as GoHighLevel estimates, build one workflow in the UI with the Estimate trigger (status sent) whose only step adds the tag quote-sent. The follow-up removes the tag itself, so the next quote starts it again.",
-        "successCheck": "A contact tagged quote-sent receives the next-day text"
+        "successCheck": "A contact tagged quote-sent receives the first follow-up message"
       },
       {
         "ref": "handoff.review_tag",
@@ -1983,7 +2027,7 @@
         "title": "Start Review Request by tagging service-complete when the work is done",
         "trigger": "always (1 minute to read)",
         "instruction": "Review Request starts from the tag service-complete. Add that tag when the job is finished and paid for: by hand on the contact, or from the pipeline's won stage with one small workflow whose only step adds the tag. It never starts from a consult, estimate or discovery call, so nobody who did not buy is asked for a review.",
-        "successCheck": "A contact tagged service-complete receives the review text two hours later"
+        "successCheck": "A contact tagged service-complete receives the review request two hours later"
       }
     ]
   }

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

@@ -230,6 +230,11 @@
         "name": "missed-call",
         "conditionalOn": "channels.sms == true"
       },
+      {
+        "ref": "tag.returning_caller",
+        "name": "returning-caller",
+        "conditionalOn": "channels.sms == true"
+      },
       {
         "ref": "tag.no_show",
         "name": "no-show",
@@ -1198,6 +1203,45 @@
           }
         ]
       },
+      {
+        "ref": "workflow.missed_call_card",
+        "allowMultiple": false,
+        "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.",
+        "actions": [
+          {
+            "type": "find_opportunity",
+            "pipelineRef": "pipeline.patient_journey",
+            "found": [
+              {
+                "type": "add_contact_tag",
+                "tagRef": "tag.returning_caller"
+              }
+            ],
+            "notFound": [
+              {
+                "type": "add_contact_tag",
+                "tagRef": "tag.lc_new_lead"
+              },
+              {
+                "type": "create_opportunity",
+                "pipelineRef": "pipeline.patient_journey",
+                "stageRef": "stage.new_lead",
+                "name": "{{contact.name}} - Missed Call"
+              },
+              {
+                "type": "assign_user",
+                "userRef": "user.owner"
+              }
+            ]
+          }
+        ]
+      },
       {
         "ref": "workflow.lead_nurture",
         "allowMultiple": false,
@@ -1821,7 +1865,7 @@
         "owner": "OPERATOR-UI",
         "title": "Confirm your business phone and the name messages are signed with",
         "trigger": "always (30 seconds)",
-        "instruction": "Settings > Custom Values: set business_phone to the number customers should call or text back, and owner_first_name to the first name every email is signed with. The build pre-fills both from the intake when it can.",
+        "instruction": "Settings > Custom Values: set business_phone to the number customers should call, and owner_first_name to the first name every email is signed with. The build pre-fills both from the intake when it can.",
         "produces": "cv.owner_first_name",
         "successCheck": "business_phone and owner_first_name show real values, not blanks",
         "blocks": [
@@ -1938,7 +1982,7 @@
         "owner": "OPERATOR-UI",
         "title": "Paste the Google review link so review requests point somewhere",
         "trigger": "always (2 minutes)",
-        "instruction": "In Google Business Profile, open the profile, choose Ask for reviews and copy the short link. Then in the sub-account: Settings > Custom Values: set review_link to that link. Until it is set, the Review Request workflow sends a text with no link, so do this before the first appointment is marked showed.",
+        "instruction": "In Google Business Profile, open the profile, choose Ask for reviews and copy the short link. Then in the sub-account: Settings > Custom Values: set review_link to that link. Until it is set, the Review Request workflow sends its message with no link, so do this before the first appointment is marked showed.",
         "produces": "cv.review_link",
         "successCheck": "review_link shows a real https link, not a blank",
         "blocks": [
@@ -1951,7 +1995,7 @@
         "title": "Start Quote Follow-up by tagging quote-sent when a quote goes out",
         "trigger": "always (1 minute to read)",
         "instruction": "Quote Follow-up starts from the tag quote-sent. Add that tag to the contact whenever a quote goes out: by hand on the contact, or, if the quotes are sent as GoHighLevel estimates, build one workflow in the UI with the Estimate trigger (status sent) whose only step adds the tag quote-sent. The follow-up removes the tag itself, so the next quote starts it again.",
-        "successCheck": "A contact tagged quote-sent receives the next-day text"
+        "successCheck": "A contact tagged quote-sent receives the first follow-up message"
       },
       {
         "ref": "handoff.review_tag",
@@ -1959,7 +2003,7 @@
         "title": "Start Review Request by tagging service-complete when the work is done",
         "trigger": "always (1 minute to read)",
         "instruction": "Review Request starts from the tag service-complete. Add that tag when the job is finished and paid for: by hand on the contact, or from the pipeline's won stage with one small workflow whose only step adds the tag. It never starts from a consult, estimate or discovery call, so nobody who did not buy is asked for a review.",
-        "successCheck": "A contact tagged service-complete receives the review text two hours later"
+        "successCheck": "A contact tagged service-complete receives the review request two hours later"
       }
     ]
   }