A tenant submits a description and photos through the portal, and Aptoria turns them into a work order, classifies urgency, and routes it accordingly. In-scope repairs can stage vetted-vendor routes under your cap and acknowledgement rules; ambiguous, costly, or serious work goes to your approval queue instead.
Dispatch under your limits
A maintenance request usually starts with the tenant, who submits it from their portal with a description and photos. It can also be created on the landlord side. Either way it becomes a work order the agent can begin to act on.
Because the request comes in structured, the agent has what it needs to categorize the issue and judge how urgent it is, instead of leaving a vague message sitting in an inbox.
The agent triages each work order: it classifies the problem, gauges urgency, and separates a true emergency — no heat, a major leak, anything affecting safety or habitability — from routine wear. Emergencies are escalated rather than queued behind lower-priority work.
Triage decides the path. A clear, in-scope, non-emergency repair can move toward a vendor within your limits; anything ambiguous, expensive, or serious is surfaced for you instead of being guessed at.
Dispatch under your limits
When a repair is within the cost cap you set, the agent can prepare a preferred-vendor dispatch proposal and hold it through the configured safety checks. When the likely cost is over that cap, the work order routes to your approval queue with the details, so you approve the spend before anyone is dispatched.
Irreversible steps get a short soft-commit window — a cancellable delay before dispatch — so if something looks off you can intercept before the vendor is on the way. Everything the agent does on a work order is logged in your audit trail.