Onboarding tab, part 4a: Maintenance
Maintenance › Routing saved through the existing call-routing route; Residents shown as Coming soon
30 Sept 2026 · branch feat/onboarding-maintenance-p4a · captured against propflow-stage · at 6dbbcf0485d
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 · Maintenance › Routing, light
The Maintenance tab joins Leasing. Routing has three questions, each saved to the company row the phone line already reads.
What to look at
Maintenance calls go to shows the stored route as text with no input: no web route writes it today, and the call-routing route reserves it, so the card says PropFlow sets it up. When a maintenance caller asks for a person, Clara rings uses the Call routing card's own RingListEditor (people from the Team, never typed numbers). Calls Clara can't help with forward to takes the office line. Each saves through PUT /api/settings/call-routing. A question with nothing stored carries the pending dot and Not answered yet.
Asserted in the captured DOM — Onboarding · Leasing · Maintenance · Routing · Residents · Maintenance calls go to · When a maintenance caller asks for a person, Clara rings · Calls Clara can't help with forward to · PropFlow set this up. Contact us to change it.. Both tabs, both Maintenance sections, and all three questions rendered (not the loading or error state).
2 · Maintenance › Residents
Notes
Neither question has anywhere to save an answer yet, so both are greyed out with Coming soon, have no input, and never count as open (decision 5). No storage is invented for them.
Asserted in the captured DOM — Offer Spanish at this building · What to say when a repair is waiting on a part · Coming soon. Both Coming soon questions rendered.
3 · Routing, dark (last, because the theme persists)
Notes
Switched to dark with the product's own theme control. Every colour is a shared token.
Asserted in the captured DOM — Maintenance · Routing · Maintenance calls go to. Same strings as light: a theme change switches colours, never content.
Two critique rounds
Round 1 and round 2
Round 1 (against the mock and brand-and-design.md). Same frame as part 1: PageBody + PageHeader, tabs across the top, the shared sub-nav rows on the left, one card per question. Two defects found in the first capture and fixed before this one: (1) a stored ring list whose person is not on the Team rendered only the editor's No one on this list, hiding what is actually stored. The stored list now shows above the editor. (2) Maintenance calls go to said “Tell us your call center” even when a route was already stored. It now says PropFlow set this up. Contact us to change it. once one is set.
Round 2 (dark, and Coming soon). Every colour is a shared token, so dark needs nothing drawn by hand. Coming soon cards are dimmed with no input and no dot, matching the mock's greyed rows. The live (read-only) state is not captured, because turning it on means writing claraLive on the stage test company. The DOM test pins it instead. No save ran in any capture, so nothing was written to stage.