Short answer: no heat is an emergency with a clock on it, and in many places a legal one. Software can take the request, pull the unit's history, and get a person on it immediately. It cannot decide that the resident should wait, troubleshoot the boiler by chatbot, or pick the vendor.
Maintenance triage covers the ordinary ticket. This is the one that gets you a 3 a.m. call, a same-day complaint, or a non-renewal. Fair Housing already forbids software from deciding who gets housing. Heat-out is the other bright line: habitability is not a bot loop.
Why this ticket is different
A leaky faucet can wait until morning. A cold apartment in October cannot. The resident may be elderly, may have a child, may have a disability that makes the delay an accommodation issue whether anyone named it that way or not. An AI that offers "have you checked the thermostat?" five times is not being helpful. It is creating a record you will not want.
The useful history is already in your system if anyone looks: last boiler work, the HVAC vendor you actually use on that building, the last time this unit had no heat, what you told the owner. A general answering bot has none of that. It has a script.
What AI may do
- Recognize no-heat, no-hot-water, gas smell, and carbon monoxide language and skip the FAQ.
- Attach the unit's recent work orders and the vendor on file.
- Draft the resident update and the owner note for a person to send.
- Wake the on-call manager. Not a ticket. A person.
What it must never do
- Auto-dispatch. Who is on the list, who has the keys, and whether this is a building-wide outage are human facts.
- Negotiate wait time. "We can look at it Tuesday" is a housing decision in practice. A person says it, or it is not said.
- Handle a reasonable-accommodation request. If the resident says they cannot stay in a cold unit because of a disability, that conversation is human, immediately. Full stop.
- Close the ticket because the chatbot "resolved" it. A thermostat FAQ is not a repair.
The questions to ask any vendor before the first freeze
- Do heat-out and air-out skip the bot and reach a person, every time?
- Can it dispatch or approve a vendor without a manager?
- How are accommodation requests routed?
- What record does it keep of who decided what, and when?
A realistic first step
Pull last winter's no-heat tickets. Walk them through the tool you are considering, at the hour they actually came in. If any path leaves the resident in a loop, or dispatches without a manager, it is not ready for this season.
If you want triage that escalates heat-out to a human and leaves housing decisions with your staff — talk with us. We would rather lose a sale than design around that boundary.
Related: AI maintenance triage your residents won't hate · Fair Housing and AI · our approach for property management.