Failed follow-up — after
The tour card says the link did not go out, and what fixes it
4 Oct 2026 · branch p9-calendar-followup-failure-visible · captured against propflow-stage · at ebb679d752a+local
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · AFTER — a tour-stage lead whose link send failed on Oct 2
The same lead. The tour card names the tour, says what happened and what fixes it. Before: main.
Asserted in the captured DOM — Evidence Sendfailed · didn't send · keep trying automatically through Oct 9. The lead and the notice (absent on main).
Sections 2–4
2 · AFTER — an inquiry-stage lead at a building with no application link
The same lead. The tour card names the tour, says what happened and what fixes it. Before: main.
Asserted in the captured DOM — Evidence Nolink · No active tour. · Add an application link in leasing settings.. The lead and the notice (absent on main).
3 · AFTER — an inquiry-stage lead whose failed send could not release its claim
The same lead. The tour card names the tour, says what happened and what fixes it. Before: main.
Asserted in the captured DOM — Evidence Stuckclaim · couldn't be asked to send it · got stuck partway. The lead and the notice (absent on main).
4 · PHONE — 390px
Same screen at phone width.
Asserted in the captured DOM — Evidence Sendfailed · didn't send · keep trying automatically through Oct 9. The lead and the notice (absent on main).
