Everything I could decide myself is decided. What's left needs
you. Each one carries the recommendation of the session that raised it — if you
agree, pick it and press Done. A model's opinion, where there is one, appears on the card
as a receipt line; cards with no receipt were never put to a model. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1A live prospect (move-in Oct 1) replied on 9/19 with his budget and a 6-month-lease-with-extend ask. A defect meant no agent turn ever processed that reply, so his guest card notes are empty — which is what Sean reported — and on 9/21 the cadence sent him a prospect.inquiry.no_response template. The forward fix is separate and proceeding. What do we do about HIS record and what he receives next? ProspectInquiry.notes feeds Clara's outbound email draft via composeInput.notes, so writing it is not an inert annotation.
In plain terms. A renter moving in Oct 1 wrote back with his budget and a six-month lease question, our system never picked the reply up, and two days later we emailed him asking why he hadn't responded — what should we do about him now? Sean never saw what the man said. The fix so this stops happening to other renters is already underway, so this is only about this one card and whether he hears from us again.
The session raising this recommends: Write his answers on his card, send him nothing Sean gets the information he asked for and can call the man himself, and we avoid an automated late reply that contradicts the email we already sent him. Tried first, unsuccessfully: Asked the ladder three times — receipts f7a22aebb, f94263c83, f4bec975b (the last after honouring retry_after). No model rung ever answered: Fable at its weekly limit until Sep 23, Astra at its usage limit until Sep 24. NOT a Fable decline — nothing ran, so there is no model recommendation to quote. The recommendation above is the Driver's own.
96073008 is parked on this.
2tools-leasing.ts:298 (the update_prospect notes parameter) says 'Anything they say they WANT in a unit goes in preferences, never here', while clara-leasing.ts:1536,1700 instructs the opposite. Observed behaviour follows the PROMPT: prod row 68bab116 carries the lease-term and budget remarks in notes. Meanwhile the one extracted preference was dropped because Property.preferenceCaptureEnabled is not true for that property, so the PREFERENCES row renders an em dash. A measurement just merged (#10609, #10613) found update_prospect carried notes 0 times in 36 single-turn cases. How should the contradiction be resolved?
In plain terms. When a renter says they want a six-month lease or tells us their budget, where should that show up for the property manager? Right now our system is given two contradictory instructions — one says that kind of thing belongs in a Preferences field and must never go in Notes, the other says put it in Notes — so it lands differently for different renters. On Sean's property the Preferences option is switched off entirely, which is why that row on the card shows a dash. This is the underlying reason he could not find what the renter told us.
The session raising this recommends: Write both, and show them together under Notes It makes the property manager's view correct no matter which of the two instructions the system follows on a given conversation, and it matches how we fixed the last problem in this exact field — render it on the page rather than write it twice. Tried first, unsuccessfully: Ladder asked a fourth time — receipt f41412fe6, after f7a22aebb, f94263c83, f4bec975b. No model rung has ever answered: Fable at its weekly limit until Sep 23, Astra until Sep 24, soonest reset ~5h out. NOT a decline — nothing ran, so there is no model recommendation to quote. The recommendation above is the Driver's own.