Everything I could decide myself is decided. What's left needs
you. Each one has a recommendation from Fable — if you agree, pick it and
press Done. "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.
1We emailed Avery Belafsky tonight saying unit 311 is hers, but in our own records 311 is still marked unavailable and 315 is still marked available — backwards. If she replies, Clara will tell her 311 is not available and keep offering 315. The session that sent the email has ended. Who fixes the listing, and when?
In plain terms. Tonight we told a Camellia applicant she can have unit 311. Our system still has it the other way round: 311 marked not available, 315 still on offer. She has not written back yet. If she does before someone fixes it, Clara will contradict the email we just sent her.
Fable recommends: Someone lists 311 in AppFolio tonight (and Joanna moves the folio 315 to 311), before Avery replies She is an approved applicant who was just told 311 is hers; being told the opposite by Clara an hour later is the kind of thing that loses the lease. Tried first, unsuccessfully: Not a Fable question — it is a write to the PMS that changes what a real prospect is told, which operator doctrine section 3 puts with a human. What I did instead was verify it rather than report the session's word for it. Against propflow-prod: the email is message 19 on Avery's thread, sent 2026-08-20T22:37:35Z, wording as approved. At PROP 1773625953462, UNIT 311 has availableForLeasing false and UNIT 315 has availableForLeasing true. isAvailableForLeasing gates every prospect-facing path, so the contradiction is live. Her thread is still at 19 messages, so she has not replied yet and nothing has gone wrong to her face so far.