Resident complaints are filed as work orders.
For building managers. Property OS takes complaints by chat or phone and links them to notices and billing.
Clients
Proof of concept
Each complaint arrives with its unit and channel.
Work order
- Channel (chat · phone)
- Unit · location
- Complaint
Linked tasks
- Notice to residents
- Billing task
Your building team gets the work order.
Repairs and site visits stay with your team.
- Takes resident complaints by chat or phone.
- Files each complaint as a work order.
- Links it to a notice or a billing task.
- Anything to agree with a resident goes to a person.
Questions people ask before a pilot.
What does Property OS not do?
It does not fix things. Repairs and site visits stay with your building team; billing and anything that needs agreeing with a resident stay with your staff. Requests outside the script go to a person.
What is recorded, and how is it deleted?
Each complaint is kept in your command center as a work order, with its channel, unit and text. Nothing on this page starts a call or records you. How this site keeps and deletes records is in the privacy notice. Read the privacy notice
Is the screen on this page real?
No. It is a schematic of the fields the building office sees, drawn without values. The real screen goes here once the proof of concept can be published.
Which systems does it connect to?
Chat and phone intake, work orders, notices and billing sit in one command center, with CRM integration. The scope is set in a working session.
What does it cost?
It is at proof-of-concept stage, so there is no public price list; pilot pricing is on request. Buildings, call volume and the CRM integration set it. See pricing