Current public status
Available for configured properties and staff workflows.
A triage suggestion is not a diagnosis, a repair commitment, or a guarantee of vendor availability.
Vendor dispatch, access, and spend follow the property’s configured workflow and may require approval.
Availability boundary
Published status
Limited availability
Provider or jurisdiction
Verify before use
Result
No outcome promise
Controls before use
Configuration, provider setup, and a reviewable record matter more than a feature-page promise.
Request history, assigned owner, and supporting photos stay with the work order.
High-risk or uncertain requests are routed for human review instead of being represented as resolved.
Control check
Source records
Reviewable
Policy
Configured by owner
Exception path
Human owner
When Aptoria pauses
Emergency, safety, habitability, uncertain, and out-of-policy requests must be escalated to the configured human contact.
Do not treat a draft, sample, or activity entry as proof of delivery, settlement, legal validity, or compliance.
Use the Trust Center and Availability pages for the current workflow boundary before enabling a customer-facing process.
Escalation
Sensitive or uncertain
Pause and review
Decision owner
Authorized human
Record
Keep evidence with workflow
Trust without theater
Verifiable, not vibes.
Three things you can check yourself — without a sales call, without a logo carousel.
See exactly how we measure it
Switching from another tool?
Review the workflow before relying on it.
Aptoria publishes availability, controls, and human boundaries instead of treating a feature page as a provider, legal, security, or outcome guarantee.