Pre-launch: MaintenanceOS is still under testing, and we're taking early-access requests.
Repair intake for the people who answer for repairs
Whoever you are, the rules are the same: the AI takes the details, fixed rules decide what happens next, and a person still clears anything flagged as dangerous. What changes is who's calling and what you need to show afterwards.
Pre-launch · in testing. Core safety controls are built; a public always-on phone is not declared ready.
- LandlordsRepair reporting for landlords who can't be on the phone all night
- Letting agentsRepair reports your landlords can trust, and your team doesn't have to chase
- Property managersOne way of taking repair reports, across every building you manage
- Maintenance companiesJob intake for maintenance firms that won't promise an engineer you haven't sent
- Housing associationsRepairs reporting that keeps dangerous cases in front of a person
- Facilities managementFacilities management — site maintenance triage with clearance and audit in the loop.
- CouncilsRepairs reporting for councils that need to show their working
- Holiday letsHoliday lets — guest maintenance calls, structured — without autonomous dispatch.
UK maintenance — not a generic AI receptionist
What a public always-on phone is not:
- emergency triage vs jobs: UK/999 guidance is locked in product source.
- contractor-dispatch language: rules must not invent a van or slot.
- out-of-hours honesty: designed to collect caller details when the desk is closed.
- no client-money: no payment, refund, compensation, or fee-waiver authority.
Read the rules every sector shares on How we keep control.