AnchorWorks  ·  Pre-Launch Red Team

Strategy Session — Show Sequence

A full read-only audit of the appointment show sequence, the kinks we found, the copy and safety net we built, and exactly what's left before it goes live.

Workflow: REV | Strategy Session | Show Sequence  ·  14 nodes  ·  Status: DRAFT  ·  June 29, 2026

How the sequence runs

Booking on any Strategy Session calendar drops the lead into a tagged, opportunity-tracked reminder track timed to the appointment:

Booked tag remove from 6 other workflows create opportunity Email 1 + SMS 1 (confirm) wait til 24h before Email 2 + SMS 2 wait til 1h before Email 3 + SMS 3 wait til 10min before Email 4 + SMS 4 (join link)

What the red team found

Launch Blocker · Resolved in build

The "Download the Pre-Call Guide" button was dead

All three report emails told leads to download the guide — but the button was just placeholder text ([DOWNLOAD GUIDE]) with no link behind it. The entire purpose of the sequence was broken. Fixed: real clickable buttons wired in the build (pending the live URL).

Launch Blocker · Fixed by new copy

Three emails shared the subject line "TOMORROW"

Emails 2, 3 and 4 all read TOMORROW — including the one that fires 10 minutes before the call. Your rewritten copy gives every email a distinct, timing-accurate subject.

Live Risk · Safety net built

A cancellation could blast every reminder at once

The appointment waits are set to skip if the appointment disappears. So a lead who cancelled would have the remaining reminders collapse and fire back-to-back — "starts in an hour" + "join here" within seconds. Cancel and reschedule are both enabled on the calendar, so this was reachable. We built a Cancel Stop workflow to catch it.

Deploy Gotcha · Caught before launch

Publishing via API can leave the trigger silently dead

The biggest catch wasn't in the sequence — it was in our own deploy method. The appointment trigger type won't arm through the API; it publishes "live" but never enrolls anyone. We proved this on a throwaway workflow, not at launch. The fix: the final Publish happens in the GHL UI, which arms the trigger reliably.

What we accomplished

1
Done

Full read-only red team

Audited every node, trigger, wait, merge tag and link. Verified the calendar group, meeting-link source, and opportunity routing end to end.

2
Done · staged

New copy build — all 8 messages

Your rewritten copy for 4 emails + 4 SMS is loaded into a one-command script, with the real guide button wired into Emails 1–3 and every subject corrected. Dry-run verified — writes cleanly, leaves the workflow in draft for your review.

3
Done · published

Cancel Stop safety net

New workflow REV | Strategy Session | Cancel Stop built and saved: when an appointment is cancelled on the Strategy Session group, it removes the lead from the Show Sequence so the reminders stop. Action is built; trigger is pre-filled and waiting on a UI publish to arm.

4
Done

Deploy method de-risked

Discovered and worked around the silent-trigger gotcha. Split the launch so the proven part (writing copy) runs via script and the risky part (arming the trigger) happens with one reliable click in the UI.

Verified clean — no action needed

Calendar coverage
All 5 Strategy Session calendars sit in the trigger's group — every booking is caught.
Join link source
{{appointment.meeting_location}} resolves to the auto-generated Google Meet link.
Opportunity routing
Lands in Revenue Pipeline (AE) → "Strategy Session Booked" — correct pipeline and stage.
No duplicate confirmations
Calendar has no native notifications — your sequence is the only sender (the Google invite aside).
Merge tags
first_name, user.name and meeting_location are all well-formed and resolvable.

Next steps before launch

1

Get the Pre-Call Guide URL

The one remaining blank. This is the live link the three download buttons point to. Nothing else is waiting on anything.

You
2

Drop the copy into the Show Sequence

Paste the URL into the script and run it — all 8 messages, 3 buttons and corrected subjects land in the workflow. It stays in draft, untouched and ready for your review.

Claude · one command
3

Arm the Cancel Stop — first

Open REV | Strategy Session | Cancel Stop, confirm the trigger reads Appointment Status = Cancelled on the Strategy Session group, and hit Publish. Do this before the sequence goes live so the safety net is up before the first booking.

You · in GHL
4

Review the copy live, then Publish the Show Sequence

Open the Show Sequence, read the emails and SMS in the builder, and hit Publish. This arms the booking trigger and the sequence goes live. One real test booking end-to-end is the final confidence check.

You · in GHL

Optional polish — after launch

Join link in the 1-hour reminder
Currently the link only appears at the 10-min mark. Adding it to Email 3 / SMS 3 can lift show rate. You chose to keep your copy as-is for launch.
SMS opt-out language
Low risk given they just booked, but a "Reply STOP to opt out" on the first SMS is good compliance hygiene.

Reference

Show Sequence workflow88196872-…-52f0370d3e94
Cancel Stop workflow7af5a06b-…-1c34f2914e34
Strategy Session calendar groupUDadfytUHCb06ABKIeCo
Pipeline → stageRevenue Pipeline (AE) → Strategy Session Booked
Copy script_patch_publish_show.py
Pre-edit backup/tmp/show_seq_prepatch.json