AnchorWorks · GoHighLevel

LAS — Master Intake
Launch Readiness Report

Local Authority Score funnel · Workflow v27 · June 29, 2026
Structurally launch-ready

The Short Version

The LAS intake workflow went from a 4-email skeleton with broken links to a complete, tested 6-email Soap Opera Sequence with a safety net. The dead report link is fixed, the two missing story emails are built across all five stages, no lead can silently fall through, and a full end-to-end submission passed clean. Two items remain before sending real traffic — both on your side.

What We Did Today

1

Full audit & red-team of the live workflow

Pulled the published workflow (65 nodes), mapped all 5 stages, verified every merge tag resolves against real custom fields, confirmed the trigger is active and routing logic is sound. Confirmed the prior merge-tag and notification-key fixes are holding.

28/28 merge tags resolvetrigger activeno [object Object]
2

Fixed the dead report link

The core deliverable link in all 5 confirmation emails pointed at a placeholder. Swapped every instance to the real location.

?placeholder=las-report → las.myanchorworks.com5 links · v24 → v25
3

Built the two missing emails — all 5 stages

The sequence was only 4 emails per stage; the spec calls for 6 (confirmation + 5-day story arc). Built Day 4 (Self / identity shift) and Day 5 (VSL / offer / urgent CTA), wired into every stage on the existing 1-day cadence.

+10 email nodes · v25 → v266 emails × 5 stages = 30
4

Built a silent-drop safety net

The "no stage matched" branch was a dead end — a malformed submission would vanish with no email, no opp, no alert. Added a fallback: tag las-no-stage + internal notification to the team with the lead's details, so nobody is ever lost.

+2 nodes · v26 → v27no lead falls through
5

Verified the front-end fix & ran a live test

Confirmed PR #1 (the question-skip race condition) is merged and deployed live — all 16 answers are now required and correctly keyed. Then fired a full simulated submission through the production webhook and confirmed every piece fired.

PR #1 liveend-to-end PASS

By The Numbers

30
Emails live
16/16
Fields captured
v27
Published version
82
Workflow nodes

End-to-End Test · Passed

Simulated full submission — routed to Stage 2

Contact createdWebhook Test · tryhubczak+lastest@gmail.com
Quiz fields captured16 / 16 — zero blanks
Routinglas_stage "Stage 2" → tags: las stage 2 + nurture - war room
Score / archetype58 · grade C · Reputation Builder
OpportunityDemand Pipeline → New Lead · status open
OPS taggeractive-opp auto-applied on opp creation

Current State

ComponentStatus
Trigger (inbound webhook)Active
Stage routing (las_stage exact match)Verified live
6-email sequence × 5 stagesBuilt & wired
Merge fieldsAll resolve
Opportunities → Demand PipelineConfirmed correct
Team notification (every submission)Active
Silent-drop safety netLive
Front-end skip-bug (PR #1)Merged & deployed
Video / creative linksPlaceholders — on hold by choice
Email domain authentication (SPF/DKIM)Needs verification

Before Complete Launch

Verify SPF / DKIM for myanchorworks.com

Authenticate the sending domain in GHL settings. Without it, the 30 emails land in spam or bounce. This is the one true blocker for real traffic.

You · ~5 min

Confirm the report link behavior

Check that las.myanchorworks.com re-renders the lead's report rather than restarting the quiz. If it needs a per-lead parameter, I'll append it.

You

Check the test confirmation email

Open the Stage 2 email sitting in tryhubczak+lastest@gmail.com — confirm merge fields and link render correctly in a real inbox.

You

Supply the 5 video URLs

thesis · universe · others · self · vsl. Once sent, I swap all 50 placeholder links in one pass. The structure won't change.

On hold

Decide: clean up the test contact

Leave "Webhook Test" running to watch the Stage 2 sequence roll out, or have me delete the contact + opp. Your call.

Optional

Optional polish (not blockers)

Add an 8 AM send window so emails don't fire at 3 AM · normalize the "from" casing (Chris@ vs chris@).

Later