Triage handles the leak at 11 p.m.
A resident reports a leak at 11 p.m. By morning the ticket already has a category, a priority, a board-attention flag, and a suggested vendor — with one sentence of reasoning you can read in a glance. You decide; Arbor Lane did the reading.
What's on the ticket by morning
The resident sends a photo and a sentence from the app — "water under the kitchen sink." No form, no category dropdown they'd guess wrong.
Triage reads it and sets the category (Plumbing — Leak), the priority (High — active water), and the board-attention flag (off — no shared infrastructure, no budget impact), and puts the right vendor at the top of the list.
It shows the one sentence of why — "active water under the sink sets High; no shared cost, so no board flag; Acme closed the last three plumbing tickets here without a callback." You override any of it in a click.
The other two surfaces, same posture
Triage is one of three places AI runs through the work, not in a sidebar. Suggest reply drafts a response in your voice when a resident asks a question — ships today, in the reply box, edit or send. Ask reads your documents and ledger and answers with sources cited — that one is next, not live yet. We'd rather show you the two that work than promise the third broken.
What it doesn't do (yet)
Triage suggests; it never closes or assigns a ticket on its own — a person stays in the loop on every one. Ask, the document-and-ledger surface, is next on the list, not in your hands today. And triage reasoning is shown so you can check it, not hidden behind a confidence score you can't read.