Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
1
In plain terms. When nobody picks up an emergency page, what should Clara tell the tenant before she hangs up? A tenant with no heat at 58 degrees called, we paged the on-call person, nobody answered, and Clara ended the call saying the on-call person would reach out if they picked it up - never mentioning that a repair request had been filed, which it had. That silence is a rule we added a week ago on purpose, because nobody had accepted the job during the call and we did not want to promise what we could not keep. Leaving it alone means tenants on an unanswered page keep hearing only a maybe-callback and the 911 line. Adding a line about the repair request gives her one concrete thing, at the risk of sounding like somebody is on the way when nobody has agreed to come. Separately, a change already in flight will text the tenant after a page goes unanswered, which is the gap that actually left her in the dark.
The full question, as raised
On a HELD high emergency page (the page fired, nobody accepted during the call), what should Clara say at the close of the call? The current close is the escalation tool's own nextStep repeated verbatim, as the EMERGENCY CLOSE bullet in agents/clara/lib/voice-agents/maintenance-tenant.ts orders, and that bullet explicitly bans any mention of a work order, a repair, a tech or anyone coming. The sentence is pinned by agents/clara/lib/voice-agents/__tests__/maintenance-active-leak-pages.test.ts line 93, so options 2 and 3 change that guard too.
Why, and what was tried
The session raising this recommends: Keep the close exactly as it is The silence is deliberate and measured: nobody accepted the job during the call, so promising anything is a promise we cannot keep. Two changes on 2026-10-20 put it there - propflowai#21271 took clean closes from 6/15 to 36/45 by cutting the tech-on-the-way promise, and propflowai#21307 then removed the repair-request line itself, taking three leak rows from 12/15 to 15/15. The real gap is not this wording, it is that nobody told the tenant anything after the page went unanswered, and a separate change in flight fixes that by texting them. Tried first, unsuccessfully: fable-decide f266181c8 came back RESOLVED for option 1 (receipt ~/.claude/jobs/fable/f266181c8.json), held under option reversal at medium confidence. I am raising it anyway for three reasons: this is a product call about what a customer hears, which the brief assigns to Fede or Gera; Fable could not read issue 22788 on that host, so it never saw the judge's own findings; and its verdict is explicitly conditional on the tenant follow-up text landing - if that lane stalls, held-page tenants stay uninformed and this question reopens. Fable also corrected a figure in my brief: the 40 percent was main BEFORE 21271, not the repair-request wording, which survived 21271 at about 80 percent and was removed by 21307 on a 12/15 to 15/15 measure. Cost if option 1 is wrong: a caller at 58F keeps hearing nothing concrete about a repair that was in fact filed.