Clara sends the application when asked

On email and text, a prospect who asks to apply gets the application sent — no tour gate, no unasked tour offer — in fixed_url and pms_generated orgs

Status is DERIVED from each row’s own PR, decision and prod-evidence links by bin/refresh-tracker clara-sends-application — never typed. Last refreshed 2026-10-03 16:35Z.

Overall
—
 
—
Shipped
—
Merged
—
In flight
—
Open
—
Waiting on you
Groups — click to filter
Status
—
Finding — 2026-10-24 · Western Slope · Kat asks Clara to send Heather the application, Clara says no

Heather already had it. She asked for the application herself at 2:09 PM; Clara sent it through AppFolio at 2:10 PM (email and text). Kat texted “Good, please send an application” at 2:34 PM. Clara saved the note, hit the default-off company switch (on only at the Sandbox company) and replied: “Saved for Heather. I can’t send her the application from here, so you’ll need to send it yourself.”

Shipped 2026-10-26. The send reads the card first, both desk switches are gone, the lookup shows what was done (#22505, #22532, #22533). Live at Willows (#22514): “Rosamund already has it: sent Oct 22 at 1:15 PM, email and text.”

Three defects, history, before → after
Oct 24 (MT)What happenedEvidence
2:09 PMHeather emails “Can you send me an application?”her thread 7e17665c
2:10 PMClara asks AppFolio; application sent, email + textoutbox row gc:send_application:e05b7845…:appfolio-163 = sent, guest card 3038
2:30 PMClara asks Kat how the 1:30 tour wentKat’s thread c9f809af
2:34 PMKat: “Good, please send an application” → stamped attended → send_application returns setting_off → “you’ll need to send it yourself”same thread, trace 3a68f669
  1. The desk never read the card. The staff read (find_people) carries no “application sent at” fact, and the send handler checks the switch before it looks at the card. Clara could not say the true thing: “already sent, she asked for it at 2:10.” This stays broken even with the switch on.
  2. A switch on an action Clara already takes everywhere. Clara sends the application with no switch when a prospect asks (how Heather got it) and after an attended tour (#21142, live at every building; Western Slope’s owner, Oct 14: “keep that going, where Clara just sends an app out. I don’t think there should be approval”). Only the staff trigger is gated, and it was never turned on at a customer. Fede, Oct 2: “if the staff says send application… we should send the app for that one”; Oct 3: “it shouldn’t be just a note. It should also be an action taken.” Built Oct 3 (#15899) as a default-off company setting; reclassified Oct 22 (#21782) as a Leasing feature switch, turn-on Fede; never on the dark-features register; the gatekeeper’s question on the Decisions page was withdrawn, not answered. 23 days dark.
  3. The scripted refusal. The desk prompt tells Clara, on setting_off: “Saved; I can’t send Sam the application from here.” A staff request is never answered with no (Fede, Oct 26).
Before“Saved for Heather. I can’t send her the application from here, so you’ll need to send it yourself.”
After“Added to Heather’s notes. She already has the application — she asked for it at 2:10 and AppFolio sent it by email and text.” When it has not gone yet: “Sent Heather the application for 2841 Morningside Court.”

Side note: Heather’s thread shows AppFolio’s “Dear Heather Wolff” template email in a Clara bubble, five days after #21140 was meant to file those as the PMS’s.

Every row opens: when it was added, why it exists, and the links that prove it. Rows waiting on a human carry a Decide → link straight to the answerable question on the decisions page. Statuses are re-derived from live PR, decision and prod-evidence state by bin/refresh-trackers; nothing here is typed by hand, and merged is not shipped until a prod_evidence permalink says the fix was exercised in production.

PropFlow Docs