Onboarding tab, part 3b: Leasing › People
Who gets escalations, the leasing ring order and the lead-summary email, each saved where Clara already reads it
30 Sept 2026 · branch feat/onboarding-leasing-people-p3b · captured against propflow-stage · at 191d5d51076+local
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · Leasing › People
The People section asks who Clara hands off to. Each answer saves to the field the escalation, transfer and weekly-summary paths already read. Open answers carry a blue dot, and so do the section row and the Leasing tab. The lead-summary list never does, because leaving it empty is a real choice: the weekly email stays off.
What to look at
Who gets escalations saves to the company's escalation contact. Leasing call ring order is the Call routing card's own editor, so people are picked from the Team and never typed in as numbers. Who gets the lead-summary email warns that saving an address turns the weekly email on, because that list is also its send switch.
Asserted in the captured DOM — People · Who gets escalations · Leasing call ring order · Who gets the lead-summary email. All three questions rendered (not the loading or error state).
Critique rounds
Round 1 and round 2
Round 1 (against the mock). The mock's People section asks the same three things in the same order. Dots sit on the open ring-order question, the People row and the Leasing tab. The escalation question carries none, because this test company already has a contact. The lead-summary list never carries one (review round 1): it is the weekly email's send switch, and a dot would push people to turn it on. The ring list reuses the Call routing card's editor, so this page and Company › Calls & messages behave identically.
Round 2 (brand-and-design.md). Help lines are one plain sentence, with no field names or jargon. The lead-summary line says what saving does, because saving there turns an email on. One small redundancy is left as it is: an empty ring list reads both Not answered yet and the editor's own No one on this list. The first is this tab's shared line, and the second belongs to the shared editor. Nothing was saved in the capture. The saves are pinned by the DOM tests.