Ticket inclusions: TicketSpice to GHL build plan.

Consoles / quick links

Direct links to every object this build touches, so you can open and check each one in one click.

Goal

Buyers receive the correct inclusions based on what they purchased:

• General Admission (GA): confirmation email only, no course grant (published + live-tested Jun 3).
• VIP ticket: updated VIP inclusions.
• Team Support add-on: its own inclusions, on top of whatever ticket the buyer has.

The flow

TicketSpice fires zaps that tag the GoHighLevel contact. A tag triggers the matching GHL workflow, which delivers the inclusions. The access piece is the part that changes most: it is no longer a rolling trial, it is a fixed window.

flowchart TD
  TS["TicketSpice purchase\nTop Rep Columbus 2026 (page 991799)"]
  TAG["Zap 243026762 (single entry)\ntags the GHL contact:\n[customer] ...columbus 2026 + [ticket] ...- ga / vip / team support"]
  TS --> TAG

  TAG --> Q{"Ticket type / add-on?"}
  Q -->|GA| GA["tag [ticket] ...- ga"]
  Q -->|VIP| VT["tag [ticket] ...- vip"]
  Q -->|"Team Support (vipAddon > 0)"| TT["tag [ticket] ...- team support"]

  TAG --> C0["Noah comms - on [customer] - 3-min stagger\nt=0  Buyer Onboarding: You are in for Columbus (anchor)"]
  C0 --> C3["+3 min  Post-Purchase: You're in. Aug 24-25"]
  C3 --> C6["+6 min  Team Seat + Referral: Who else needs the room?"]

  GA --> GAW["GA-to-VIP upsell (15-min wait)\nTRB GA retired - no course grant"]
  VT --> VL["+9 min  VIP Logistics: VIP confirmed (4596e019)"]
  VT --> VIP["TRB VIP fulfillment (9cd1f5e8)\ntrigger: [ticket] ...- vip"]
  VIP --> V2["+12 min  Email: request Black Pivot Point address"]
  V2 --> V3["ClickUp task: mail Black Pivot Point"]
  V3 --> V4["+15 min  Email: workbook + Solo access"]
  V4 --> V5["tag [customer] flight school - solo\n+ Webhook -> Solo zap (ukmryqw)"]

  TT --> TEAM["TRB Team Support fulfillment (a21a25cc)\ntrigger: [ticket] ...- team support"]
  TEAM --> T2["+18 min  Email: request Blue Pivot Points address"]
  T2 --> T3["ClickUp task: mail Blue Pivot Points (per attendee)"]
  T3 --> T4["+21 min  Email: prep videos + Elite access"]
  T4 --> T5["tag [customer] flight school - elite\n+ Webhook -> Elite zap (30m9d65)"]
  T5 --> T6["Manual: assign LearnWorlds group manager\n+ group implementation calls (Noah/JC)"]

  V5 --> SZ["Zap 336409225: Solo\nLW Create User + Add Tags + ClickUp"]
  T5 --> EZ["Zap (hook 30m9d65): Elite\nLW Create User + Add Tags"]

  SZ --> ACC["LearnWorlds access starts\n(tag-based enrollment)"]
  EZ --> ACC
  ACC --> REM["Wait until Sep 25, 2026\n(Bootcamp Aug 24-25 end + 30 days)"]
  REM --> RW["Webhook: remove LearnWorlds access (23tbuwr)\n+ access-ended email"]

  classDef src fill:#e0f2fe,stroke:#0ea5e9,color:#0f172a;
  classDef vip fill:#f5f3ff,stroke:#7c3aed,color:#0f172a;
  classDef team fill:#f0fdf4,stroke:#16a34a,color:#0f172a;
  classDef zap fill:#fff7ed,stroke:#ea580c,color:#0f172a;
  classDef acc fill:#fef3c7,stroke:#b45309,color:#0f172a;
  classDef ga fill:#eef2ff,stroke:#6366f1,color:#0f172a;
  classDef comms fill:#fdf2f8,stroke:#db2777,color:#0f172a;
  class TS,TAG src;
  class VT,VIP,VL,V2,V3,V4,V5 vip;
  class TT,TEAM,T2,T3,T4,T5,T6 team;
  class GA,GAW ga;
  class C0,C3,C6 comms;
  class SZ,EZ zap;
  class ACC,REM,RW acc;
  

What gets built

The crux: fixed-window access (not a rolling trial)

1. On the trigger tag, enroll the buyer in LearnWorlds immediately (Solo for VIP, Elite for Team Support).
2. Store the access-end date explicitly (Bootcamp end + 30 days).
3. A wait-until-that-date step fires the LearnWorlds de-provision so access is removed cleanly.

Stays manual (by design)

• Pivot point fulfillment. Address is collected automatically, then Mitch or a VA mails the cards.
• LearnWorlds user group manager assignment. LearnWorlds does not automate this yet, so it stays a documented manual step with an internal notification.

Optional cleanup

Three zaps fire per TicketSpice purchase (ticket created, order created, VIP/add-on tagging). Evaluate folding the VIP-tagging zap into one of the other two without breaking the attendee-filter tags. Also strip deprecated items from the emails (for example "engaged presentations").

Execution order

1. Pull the live workflow and the 3 zaps, document current state as the diff baseline.
2. Rework the VIP flow (draft, test, publish).
3. Build the new Team Support flow.
4. Adjust or add the zap for the add-on tag.
5. Wire the fixed-window LearnWorlds access plus scheduled removal.
6. End-to-end test with a sample purchase.
7. Second task (per the recording): backfill contacts who already bought tickets.

Build status (updated 2026-06-04, go-live)

Combined purchases (decision: leave both)

The TicketSpice trigger fires per ticket line item, so each ticket type applies its own tag independently and each tag triggers its own GHL workflow. Combined orders therefore enter more than one workflow:

Tagging zap: all three paths exist (resolved)

Blocked on (inputs from Jet)

Plan for ClickUp task 86e1nvc3z.  ·  Documentation home