Files
2026-10-02 07:10:57 -07:00

4.8 KiB
Raw Permalink Blame History

Phoenix name-change remediation — living review loop

Slug: phoenix-salon
Updated: 2026-09-20 ~12:08 PT (CoS)
Sibling: surface-checklist.md (what is open/done) · sop-email-follow-up.md (email silence + nudges) This file: what we tried, what landed, what we cut — reviewed after each batch

Keep this glanceable. One row per action. Update after every Job Card / batch — do not wait for end of project.


Triage framing (who feels the friction)

Sort work in this order. Prefer the top of the list when choosing the next batch.

Priority Who feels it Examples Bias
1 — Customers People trying to find / book / trust Phoenix GBP/Maps, site NAP, IG, Yelp, stale “La Mae / Flying C” on directories customers actually click Highest impact; fix or email first
2 — Vendors / partners Platforms, directories, aggregators, review networks Birdeye, MapQuest tickets, Superpages, FindGlocal, hairsalonsinusa Batch email/ticket; park Cloudflare / no-contact
3 — Back-office Us / Ashley ops friction Onboarding folder, auth, GBP Manager invite, VeriMail process lessons Do when it unblocks 1–2; don’t let it crowd out customer surfaces

How to use (30-second ritual)

After each batch:

  1. Add rows under Batch log (copy a blank row if needed).
  2. Mark Worked? yes / partial / no / too-soon.
  3. Fill Keep (repeat next time) and Cut (never again / demote).
  4. If a pattern shows twice, write one line under Patterns.
  5. Sync status into surface-checklist.md.

Patterns (fill as we learn)

Seen Keep / Cut Since
(empty — first patterns after 2–3 batches)

Seed from Gate 3 pilot (not a full batch review yet):

  • Keep: on-disk send receipt + .eml before claiming SENT.
  • Keep: Method A with hermes .venv python (system Python312 burns a run).
  • Cut: treating Cloudflare/no-contact scrapers as email targets (WONT-DO fast).
  • Cut: Anthony personally chasing aggregators day-to-day.

Batch log

Batch 0 — Gate 3 email pilot (2026-09-19 → inbox check 2026-09-20)

# What we did Channel / audience Priority Worked? Keep Cut Evidence
1 Checked FindGlocal listing Vendor directory (public) 2 yes — already canonical Fast “already green → WONT-DO” Spending time on claim/contact forms when NAP is right gate3-pilot/2026-09-19/evidence/findglocal-*.html
2 Hit hairsalonsinusa Vendor directory 2 no — CF 403 Immediate WONT-DO when CF blocks + no mailto Retry loops / browser rabbit holes same day .../hairsalonsinusa-*.html
3 Emailed Birdeye remove/update La Mae Vendor: profiles@birdeye.com via VeriMail ashbotphoenix@ 2 (customer-facing stale NAP on aggregator) too-soon — SENT, no reply as of 2026-09-20 Receipt + mid-week inbox re-scan before nudge Same-day human chase gate3-pilot/2026-09-19-birdeye-send/evidence/
4 VeriMail inbox pass for listing returns Back-office + response channel 3→feeds 2 yes — NONE_FOUND clear Job Card + artifact inbox-scan.md Claiming done on STATUS alone mail/2026-09-20-inbox/evidence/

Batch 0 review note: Pilot proved the thin email pipe. Highest remaining customer friction is still human (IG) + vendor waits (Yelp/MapQuest), not more cold emails today.


Batch 1 — (next) — date: ____

# What we did Channel / audience Priority (1/2/3) Worked? Keep Cut Evidence
1
2
3

Batch 1 review note: (what to do more of / less of)


Batch 2 — (ready) — date: ____

# What we did Channel / audience Priority (1/2/3) Worked? Keep Cut Evidence
1
2

Batch 2 review note:


Suggested next batch (not started — needs Gatekeeper go)

Ordered by triage:

  1. Customer: Ashley IG bio + Vagaro + guest screenshot (human).
  2. Customer/vendor: Yellow Pages confirm or WONT-DO (human).
  3. Vendor wait: leave Yelp + MapQuest alone until they move.
  4. Vendor: mid-week Birdeye inbox re-scan (VeriMail Job Card) before any nudge.
  5. Back-office: onboarding green (auth + GBP Manager) when it unblocks proof letter.
  6. Vendor parked list: only after Job Card — BestPros / wheree / etc.

CoS updates this after each batch. Hermes does not invent Keep/Cut without evidence paths.