No-heat vs no-cool: how an HVAC triage rule should work
Two callers, both without conditioning, are not the same emergency. A written rule ranks them. A gut feeling does not.
The short version
4 things that decide this
- 01Life-safety signals outrank everything: a carbon monoxide alarm, a smell of gas, a burning smell, or water pouring from an air handler send a human to the phone immediately, with no exceptions written into the rule.
- 02After life safety, the rule weighs the occupant, the weather, and the contract, in that order, because a no-heat call at 15 degrees with an infant in the house is not the same job as a no-cool call at 68 degrees in an empty rental.
- 03The rule belongs in a decision table a dispatcher can read and edit, never in a prompt buried inside a vendor's black box.
- 04What the system writes to the field service management platform is the ranked queue and the reason for the rank. What stays human is any call that does not cleanly match a row.
No heat and no cool are not one category
Most dispatch software has one urgent bucket. A no-heat call and a no-cool call both land in it. Whoever answers the phone decides which goes first. That works until a heat advisory hits the same week as a cold front. The board fills with two kinds of urgent that are not equal.
A no-heat call at 15 degrees outside is a pipe-freeze risk within hours. A no-cool call on a mild 68-degree afternoon is uncomfortable, not dangerous. Sameday and Supacalls, two vendors that publish contractor call data, put HVAC call miss rates near 27 percent industry-wide. 85 percent of callers refuse to leave a voicemail. Book the wrong call first and revenue is not the only loss. The real emergency waits behind a comfort complaint.
What outranks a comfort complaint, and why
A working triage rule ranks your call on four things, checked in order. Each one only matters once the one above it has cleared.
Life safety comes first, with no exceptions written into the rule. A carbon monoxide alarm. A smell of gas near a furnace. A burning smell from any equipment. Water pouring from an air handler into a ceiling. None of these are HVAC calls anymore. They are safety calls that happen to involve HVAC equipment. The only correct action is a human on the phone within seconds, not a booking slot.
Second is the occupant. An infant, an elderly resident, or someone on medical equipment moves a call up the queue. That holds even when the weather alone would leave it in the standard slot. A CPAP machine does not care what the thermostat says. The rule has to ask, and your caller has to be asked plainly. Nobody volunteers that detail unprompted.
Third is the outdoor temperature band. A no-heat call under freezing is a same-day dispatch, regardless of anything else on the board. Pipes freeze and burst on a predictable clock. A no-heat call at 55 degrees is unpleasant but survivable overnight, and can wait for the next open slot. The same logic runs in reverse for cooling. A no-cool call during a declared heat advisory ranks with the freezing no-heat call. A no-cool call on a mild shoulder-season day sits behind almost everything else on the board.
Fourth is the account. A maintenance-agreement member goes ahead of a non-member at the same urgency tier, because that is what the agreement is for. A commercial account with a walk-in cooler full of inventory outranks a comparable residential comfort call. The loss there is measured in spoiled stock, not discomfort. None of this reorders past life safety or the occupant check. It only breaks ties within a tier.
How four calls sort against each other
The exact shape a dispatcher should be able to open, read, and edit without asking an engineer for help.
| The call | Rank | Why |
|---|---|---|
| CO alarm sounding, any temperature | Human now | Life safety overrides the queue entirely |
| No heat, 15 degrees, infant in the house | Same-day, first slot | Freeze risk plus a vulnerable occupant |
| No cool during a declared heat advisory | Same-day, first slot | Heat stress risk matches a freeze risk |
| No heat, 55 degrees, member account | Next available slot | Uncomfortable, not dangerous; membership breaks the tie |
| No cool, mild day, non-member | Standard queue | Lowest urgency tier on the board |
A table the dispatcher can edit, not a hidden prompt
A common mistake is a triage rule that exists only as a paragraph inside an AI vendor's system prompt. It works until the dispatcher wants to change the freezing threshold from 32 degrees to 28. Or add a rule for a commercial walk-in cooler. The only way to touch it turns out to be a support ticket to the vendor.
It should live as a decision table the office manager owns. Rows for call type, temperature band, occupant flags, and account tier. Columns for the rank and the reason. A CSR or an AI phone agent reads the same table when a call comes in. When a heat advisory is declared, someone edits a threshold. Nobody rewrites a paragraph of prose an engineer has to reinterpret.
What gets written back to ServiceTitan, Housecall Pro, Jobber or whatever you run is the ranked queue position and the reason code the table produced. Nobody has to re-read a raw transcript to understand why a job jumped the line. What stays human is anything that does not cleanly match a row. A vague caller. A mixed signal, like a burning smell paired with a routine request. Uncertainty routes to a person. That is the same design position we take on emergency handling generally.
- 01Freeze and heat-advisory thresholds are numbers the office should set, not the vendor.
- 02The reason code that lands in the FSM should be legible to a technician glancing at their board, not a transcript dump.
- 03A rule that cannot be edited without a support ticket is not a rule the business owns.
Some of the systems we have shipped
What HVAC owners ask about triage rules
01Does a maintenance-agreement member always go first?+
No. Membership only breaks a tie within the same urgency tier. A carbon monoxide alarm from a non-member still outranks a routine no-heat call from a member. The account tier is the last thing the rule checks, not the first.
02Which signals count as life safety on a phone call?+
A carbon monoxide alarm sounding, a smell of gas near gas-fired equipment, a burning smell, or water actively pouring from an air handler. Any of these routes to a human immediately, with no booking flow in between.
03How does the rule treat a commercial account differently from residential?+
A commercial call with perishable inventory in a walk-in cooler ranks above a comparable residential comfort call. The loss compounds on a clock. It still sits behind any life-safety signal, residential or commercial.
04What outdoor temperature counts as an emergency for no heat?+
A sensible starting threshold is 32 degrees outdoor, sometimes a few degrees higher to cover lag in an uninsulated house. Below that line, a no-heat call becomes a same-day dispatch regardless of account tier. Above it, occupant and account factors decide the order.
05Can an AI phone agent apply this rule, or does a person have to?+
An agent can read the same decision table a CSR would and assign the initial rank in real time. That is where most of the speed gain comes from. Anything the table does not cleanly cover should route to a person rather than have the agent guess.
06Do we need a ServiceTitan integration for this to work?+
The rule itself does not require one. Writing the ranked queue and reason code back automatically does, and what that requires depends on the platform's access model. Treat the table and the write-back as two separate pieces of work.
