Context before action
Understand property and unit history, reported symptoms, access, urgency and relevant warranty or policy information. Incomplete context should trigger clarification rather than invented facts.

The maintenance-first development direction coordinates intake, context, work orders, vendors, authorization and evidence — with people performing the physical work.
Property Manager AI is available with custom onboarding. Additional autonomous capabilities are in development.
Follow the intended case lifecycle. This is a process explanation, not a live repair or completed autonomous product.
A resident reports an issue through an agreed channel, with photos or other evidence when available. The intended workflow connects the request to the property, unit and history.
Understand property and unit history, reported symptoms, access, urgency and relevant warranty or policy information. Incomplete context should trigger clarification rather than invented facts.
Vendor replies, availability and repairs can take days. The target case keeps its state, next action and owner visible, including retries, alternative providers and escalation.
The work is not complete because a message was sent. The intended closure compares the requested scope with the appropriate repair evidence, documents and confirmation.
Move the example repair amount. A financial threshold changes the authorization path, while policy, safety and vendor checks still apply.
Example only. These amounts are not WSAI pricing or a recommended spending policy.
Prepare scope, vendor options and evidence. Ask the authorized person to approve this specific amount before committing to the repair.
Start with the outcome. We’ll work with you to define the right next step.
Submit an objective