The front door: where leasing records get their property
A map, not a proposal. What the front door is, how each record picks its property today, what has piled up on it, and the one field that can't tell a phone call from a tour.
For review. Map only; nothing proposed, nothing built. Western Slope, read-only production data, Oct 7–8. Linked from Staff notifications, section 4.
1. What the front door is
The office number rings a stand-in building with no homes in it.
Calls can be about anything, so a company-level place for them is reasonable. The question is what else lands there.
2. Where a record gets its property, by channel
On the phone the property is fixed when the call rings; on text and email it is re-decided every message but rarely written down.
gets the real homeonly when one home is already knowninherits the line
Before 23:36 on Oct 7, the phone tour and AppFolio card were red too. Text already finds the home every message; it is just not written onto the record.
3. What sits on the front door
Since Sep 12, mostly phone calls; the leasing records on it are few, and none has ever moved off.
Western Slope, Sep 12 to Oct 7. Flat at 6 to 9 front-door conversations a day. Section 4 of the staff page counts from Sep 1, so its numbers differ slightly.
In 20 front-door calls read by hand, 3 named one of our homes and were missed.
The other 17: vendors, residents with no address, hang-ups, police, a home that isn't ours. The switchboard mostly works. The damage is split records: 14 of the 126 belong to someone whose card or tour is already on a real home.
4. Thomas, step by step
The right home was in hand at 19:25 and nothing used it.
Times UTC. The 23:36 fix files new phone bookings on the listing's building; it is not yet proven on a real call.
5. Two things with the same name
A conversation and a leasing record both write one field called "property," and nothing tells them apart.
Gera's design already draws this line: "Tours and work orders are born on the home." Fede, quoted there: "You can't tour a portfolio."
6. Where a rule could live
Four places, listed without a pick.
Place
What it would mean
L1 Each creator
A check inside each place that writes an inquiry, tour, AppFolio write or application.
L2 The per-turn resolver, on voice
Phone calls find the home every turn, the way text already does, and hand it to the tools.
L3 The data layer
Saving a leasing record without a real home is refused, whoever is saving it.
L4 After the fact
A job later re-files records whose conversation names a home. An earlier move of this kind broke the tour-to-card link.
Gera's side, three conditions on any build. (1) Spot the front door with the existing company-line umbrella check, not a new stamp. (2) Conversations legitimately live on the line and are left alone. (3) A refusal is a named "home unknown" result that makes Clara ask which home, never a silent skip. His design's words for it: "This caller has not named a home yet … so Clara asks first."
Sources. Front-door inspection, Oct 7 (read-only prod scans by property id and org id; transcript sample seed 20261007). Write paths: call-ended route, conversation bindHome, inbound-dispatcher, tools-leasing save_prospect and schedule_tour, front-door-unit-home, apply-tour-intent, postcall-tour-request, PMS drain, guest-card-send-application-intent, escalation-matter. Phone booking fix #17573; earlier re-key breakage #9579; re-key tooling #7622, #7754, #14218, #17376. Gera's design: portfolio architecture. Gera's conditions: Smith on the engineering bridge, Oct 8 02:58Z. Context and options with a recommendation: staff notifications, sections 4 to 4b.