Prospecting Single-Send Cutover Checklist
What this is: the one-time cutover from the announce-then-deliver pair to a single email that carries the report.
✅ The cutover was executed on 2026-10-30
Verified live the same day via
list-workflow-campaigns:
Workflow Status Last updated (UTC) C-021.Prospecting - generate and email reportpublished 09:05 C-021.Prospecting - Touch 2 Deliverydraft 07:00 It was done in the safe order. Touch 2 was retired two hours before the merged workflow was touched, so no prospect sat in the overlap where both could fire. That was the failure mode this checklist led with, and it did not happen.
Sections 1, 3 and 4 below are therefore a record, not a task list. Sections 2, 5 and 6 are still open and are the reason this document is still
active.
Still open
A. Test the trigger link — never done, and it gates the value of everything else
- Send the merged template to a test contact
- Open the email in a real inbox, not the builder preview, and click the report link
- Confirm it opens that contact's own report, not a cached one and not another prospect's
- Confirm it opens in a private window with no login
Why this still matters more than anything else here. Across every tracked send of the old delivery email the report link was clicked zero times, and per-contact link resolution has never been tested. The link is shared with the inbound C-025 lane, so a change to its destination moves both. The cutover shipped without this test. If the link does not resolve per contact, the merged send is delivering the same broken thing faster.
B. Backfill the contacts who were never delivered
- Preferred Air Inc. — announced 2026-10-09, no report. Send
-
Gulberg Builders LLC— removed 2026-10-30. A second contact at the same business asked to be removed on 2026-10-07 and is correctly suppressed. Sending to the remaining contact is not a breach — the request named one address — but somebody there has said stop, so the business is left alone - Apuzzo Electric Inc — announced 2026-10-29. Same check
Contact ids are in the cutover entry of the operational change log.
C. Re-tick the three orphaned bucket contacts
The single-select prospect_bucket (jCdKeYfwzNaTPWn6j5o5) was replaced on 2026-10-30 and is gone
from the field list, but contacts still carry values against its id. They are invisible to any
filter built on the new field and cannot be edited from the contact card.
⚠️ This is not a three-contact job, and it cannot be done by filtering. A deleted custom field
cannot be queried — search-contacts-advanced returns 422 … Check if custom field exists — so the
affected contacts have to be found by paging all 621 and reading raw customFields.
- Run the sweep first. Page every contact, collect those carrying
jCdKeYfwzNaTPWn6j5o5, and record the count. At least ten are known, and a sample of 18 worked prospects found seven of them affected, so expect substantially more - Re-tick each onto
Prospect Bucket Options, dropping theB1-toB5-prefix (B1-review-engine→review-engine) - Known so far:
p9MopMVO4aOtnm0eDp6K,4Ypde03xZBM2cY05XtTh,rzpHyaYGLhZoUJlIaqWK(alldisqualified);e7UzpsQDBNbIEIiNq5uN,vRMrijaPSl1ndsYv489Y,p8SCrXIlXyvs3zGUTuA9,noqpcHeAPuD4nWxzXDBL(B1);mfvg492nAHGfJmmAbFHe,b5hagQGmSPr4x9xGCq9t(B2);p3zNgUMgsF7Yr6PoQV1T(B3)
D. Read the two things in the builder that nothing documents
-
C-021.Prospecting - disqualified— published, has run, appears in no document. Record what it triggers on and what it does - The two disposition automations (
lostandabandoned). They send no email, so the one working workflow endpoint cannot see them, and the workflow API is blocked. Four questions in C-021 spec §10.0.1 — above all, does thelostworkflow set a Lost Reason, or was that done by hand? - Record both in the inventory per
ghl-structure-sync
E. Fix two opportunities whose status and stage disagree
Both predate the automations and neither is caught by them.
- Mark Ferris
4Ypde03xZBM2cY05XtTh— statusabandoned, stage still Audit Sent. Move the stage - Ellis Builders LLC
hSsMM035AqohPohfUHtY— statusopen, stage Closed Lost. Decide which is true and set the other
What was done
1. The merged template ✅
Created in the C-021.Prospecting folder from Template 19.
⚠️ One thing to re-check if greetings ever come out wrong: the Default Text fallback on
{{contact.first_name}} is UI state and invisible to the API, so a template that reads back
correctly can still be missing it. Without it most sends render "Hi ,".
3. Touch 1 rebuilt ✅
Report generation and the send are now one published workflow.
⚠️ Three guards from the original design are unverified — the builder cannot be read, so whether they were built is unknown:
- Retries at 3, 8 and 18 minutes rather than a flat 3-minute wait. A slow report is otherwise a lost one
- Report-link guard: no link after the last retry → tag
prospecting-report-failed, notify, end. Never send a report email with no report. (The tag exists in the account ✅) - Heat-map guard: audit present but no local heat-map → park and flag rather than send
4. Touch 2 retired ✅
Unpublished at 07:00 UTC, before the merged send was touched.
⚠️ What happened to the contacts who were mid-wait in it is unrecorded. They receive nothing from a draft workflow. Check whether any were stranded, and whether they are covered by the backfill in B.
Verification, after the first live tag
- Exactly one email, within minutes of the tag
- Greeting is a person's name, not a company name and not "Hi ,"
- Report link opens that prospect's own report
- Opportunity moved to
Audit Sent - Nothing fires the next morning
- A prospect with a failed audit is parked and flagged, not sent
Related Documents
- Prospecting Outreach Email Templates — Template 19
- SC GHL C-021 Prospecting Workflow Spec — the as-built record and §10 on the disposition automations
- Automated First Touch SOP — the standing procedure this cutover produced
- GHL Prospecting Pipeline SOP — the cadence
- SC GHL Sub-Account Structure Inventory — where the outcome is recorded
Document History
| Version | Date | Changes |
|---|---|---|
| 2.1 | 2026-10-30 | Corrects section C, which listed three orphaned contacts as a quick manual fix. A sample of 18 worked prospects found seven more, and a deleted custom field cannot be filtered on, so the affected contacts cannot be enumerated by query. The step becomes a paging sweep first, then the backfill, with the ten known ids listed |
| 2.0 | 2026-10-30 | Converted from a to-do into a record, because the cutover was executed the same day it was written. The merged send is published and Touch 2 went to draft two hours earlier, which is the safe order, so the duplicate-report failure this document led with did not occur. What remains is pulled to the top and is mostly not the cutover itself: the trigger-link test was never done and still gates whether any of this delivers value; three contacts carry orphaned values on the deleted bucket field; two opportunities have a status and a stage that disagree; and the disqualified workflow plus the two new disposition automations are unreadable and undocumented. The three WF-1 guards are marked unverified rather than done — the builder cannot be read, so whether they were built is unknown |
| 1.1 | 2026-10-30 | Gulberg Builders removed from the backfill: a second contact at the same business opted out on 2026-10-07 and is suppressed, so the business is left alone even though sending to the other contact would not be a breach |
| 1.0 | 2026-10-30 | Created as the handoff for a cutover that cannot be scripted: the workflow API is disabled for this sub-account and the builder canvas does not render to browser automation. Carries the two failure modes that are not obvious from the design — a published Touch 2 that sends a duplicate report if it is not retired in the same sitting, and a Default Text fallback that is invisible to the API and renders "Hi ," without it |