@elitedcs/ghl-mcp 3.71.0 → 3.72.0

package/skills/blueprint/presets/ecommerce.md

@@ -0,0 +1,54 @@
+# Preset: Ecommerce
+
+**File:** `ecommerce.preset.json` · **id:** `ecom` · **version:** 2.0.0 · **default:** no
+**Source:** Built from the intake industry pack "ecommerce" (store_platform, aov, abandoned_cart) and the welcome-series pattern; v2 depth per the owner review of 2026-08-26.
+
+## When it is selected
+Routes from the "Ecommerce" business type (online store, Shopify store, DTC brand) and the `ecom` / `ecommerce` / `online_store` / `shopify` / `dtc` aliases.
+
+## What it builds (skeleton, v2 depth)
+- **Users** — one per `brief.team.staff[]` entry. Every alert, task and assignment step points at a `userRef`; in the skeleton that is the role placeholder `user.owner`, resolved at fill time from `team.notifyName` (alerts) and `team.callsName` (tasks, assignment). No staff yet → the steps stay, pointed at `user.__pending__`, and the build reports them as waiting.
+- **1 pipeline** — "Store Leads": New Subscriber → Engaged → First Order → Repeat Customer → VIP → Lapsed. Overridden by `goal.salesStages` when the brief supplies them.
+- **6 custom fields** — Lead Source, Shopping For, Welcome Code Used, Last Order Value, Last Order Date, Lifetime Value.
+- **22 tags** — source, lifecycle, the hand-off trigger tags (`nurture-start`, `winback-start`, `missed-call`), and interest tags mirrored from the interest field.
+- **6 custom values** — business_name, business_phone, owner_first_name, store_link, welcome_code, code_expiry_days. Every message reads business name / phone / signature / links from these, so the copy stays right when details change.
+- **No calendar** — this preset does not book appointments; the Speed to Lead and nurture sequences drive replies and orders instead.
+- **1 intake form + 1 funnel** — "VIP List Signup" (first name, email, phone, what they are shopping for) and a Join the VIP List landing page (the welcome code, what the list gets, A2P consent block) plus a Thank You page that shows the code and links to the store.
+- **11 email + 12 SMS templates** — complete, send-ready copy written to `references/copy-guide.md`. The build stage rewrites every one from the real brief (offer, pain points, objections, prices, lead magnet) and keeps the cadence, the single CTA and the merge fields.
+- **5 workflows, 23 customer touches** — see the table.
+
+
+## Workflows
+
+| Workflow | Trigger | Actions | Touches | Span of waits | Stops on reply |
+|---|---|---|---|---|---|
+| Speed to Lead | form_submission | 15 | 5 | 1.1 days | yes |
+| Missed Call Text-Back | call_status (missed: no-answer/busy/voicemail) | 7 | 2 | 1 h | yes |
+| Lead Nurture (30 days) | contact_tag (tag.nurture_start) | 28 | 11 | 31 days | yes |
+| Replied - Stop & Route | customer_reply | 8 | 0 | instant | no |
+| Win-back (30 days) | contact_tag (tag.winback_start) | 13 | 5 | 31 days | yes |
+
+- **Speed to Lead** (15 actions): instant text + email, opportunity card, the contact assigned to whoever takes calls, alert to a real person, a call task due today, a 2nd touch at 20 minutes, a 3rd at 3 hours, a 4th and 5th by the next day, then the hand-off tag `nurture-start` as the last action.
+- **Lead Nurture** (28 actions, 11 touches, 31 days of waits): give, give, ask. Ends with `lifecycle-lapsed` + the `winback-start` hand-off.
+- **Win-back** (13 actions, 5 touches, 31 days of waits): one reason to come back per message, then `lifecycle-lost`.
+- **Replied - Stop & Route**: the exit workflow. Pulls the contact out of every sequence, notes it, marks contacted, alerts a person and creates a 15-minute reply task.
+- **Missed Call Text-Back**: `call_status` trigger scoped to no-answer / busy / voicemail, inbound. Text within seconds, tag, alert, call-back task, one more text an hour later.
+
+### Why sequences hand off with a tag, not add_to_workflow
+Every hand-off is `add_contact_tag` + a `contact_tag` trigger. Both halves are live-proven shapes captured from working GHL workflows (`templates/action-schemas.json`). `add_to_workflow` has no captured native shape there and has not been proven at runtime, so a preset may not use it. Each sequence removes its own trigger tag as its first action so a later hand-off can start it again.
+
+## How the brief shapes it
+| Brief signal | Effect |
+|---|---|
+| `goal.salesStages` present | replaces the default pipeline stages (workflow stage refs are mapped to the nearest equivalent) |
+| `channels.sms == true` | keeps SMS templates, the send_sms actions, Missed Call Text-Back and the A2P gating; otherwise they drop (the email-only nurture still spans 31 days) |
+| staff answers present | fills `users`; every `userRef` resolves to a real person |
+| staff empty | every `userRef` → `user.__pending__`; the steps stay; `handoff.add_staff` holds those workflows DRAFT |
+| `flags` | `needs_a2p` / `stripe_not_connected` / `calendar_oauth_needed` / `email_domain_needed` add the matching handoff |
+| `business.name`, `offer.*`, `audience.*`, `extended.*` | fill object names, custom values and ground every template rewrite |
+
+## Order events
+GHL does not see store orders on its own. `handoff.store_orders` connects the store (Shopify integration or an order webhook) so a purchase moves the pipeline card to First Order and stops the nurture; until then, staff move cards by hand. Abandoned-cart recovery is a store-side flow and is out of scope for this preset.
+
+## Copy notes
+Built for a subscriber who gave an email for a code and is deciding whether to use it. The instant touches deliver the code and ask one question (what are you shopping for). The nurture earns the order: how to choose the right one, why we make it, what people buy first, shipping and returns in plain words, the three questions before buying from any small brand, the code expiring (a real expiry the operator sets), the decision sheet. Win-back is "one question" then a fresh code. Reviews and best-seller claims are placeholders the build stage fills only from real store data.