After-hours triage rules for commercial HVAC calls: emergency, urgent or routine

By Manvendra Kumar, founder of Mopshy

The short answer

Write your after-hours triage rules down before anyone or anything answers the phone. Put life-safety calls on their own path that ends with a person, not a message queue. Define emergency, urgent and routine in your company's own words, with examples. Then decide which details the on-call tech needs on every ticket, so the callback starts with a decision instead of twenty questions.

These rules matter whether calls go to a dispatcher, an answering service or an automated intake. Whoever answers can only be as consistent as the rules they are given.

1. Give life-safety calls their own path

Some calls are not service requests. A caller reporting a gas smell or a carbon monoxide alarm needs to be told to leave the building and call for help, and your on-call contact needs to know right away. Routine intake questions come later, if at all.

Public safety guidance is consistent on the first steps. State regulators tell people who smell gas to leave the building and call 911 or the gas utility from a safe place outside, without switching lights or appliances on or off. The U.S. Consumer Product Safety Commission tells people to get outside immediately and call 911 when a CO alarm sounds. Your script should repeat that guidance, not improvise it.

• List the phrases that trigger this path: gas smell, CO alarm, smoke or burning smell from equipment, sparking, flooding near electrical equipment.
• Write the exact instructions the caller hears, using your local utility's emergency number where it applies.
• Name who gets reached immediately, in what order, and what happens if nobody answers within a set time.
• Record the time of the call and the time a person was reached, so you can review it later.

This is an operations checklist, not safety advice for your customers. Check the wording with your gas utility's published guidance and your own safety lead before it goes live.

2. Define emergency, urgent and routine in your words

Most service companies already have these categories in their heads. The problem is that they live in the heads of two or three dispatchers. Write them down with examples from your own customers.

Example definitions to adapt

• Emergency: no heat in an occupied building in freezing weather, no cooling where equipment or inventory is at risk, an active water leak from HVAC equipment.
• Urgent: reduced capacity in an occupied space, a unit tripping repeatedly, a refrigeration or server-room cooling alarm that has not caused damage yet.
• Routine: noise complaints, a thermostat question, a filter or maintenance request, a quote request.

These are examples, not a standard. A data center, a restaurant and an office park will draw the lines differently. Your service contracts may also define response times that override the general rules for specific customers.

3. Decide what every ticket must contain

A good after-hours ticket lets the on-call tech decide whether to roll the truck without calling the customer back for basics. For commercial work, that usually means:

• Urgency, using your definitions, plus the caller's own description in plain words.
• Business name, service address and the on-site contact with a callback number.
• Equipment type if the caller knows it: rooftop unit, split system, boiler, chiller, heat pump, and make or model where available.
• Access details: gate or door codes, roof access, parking, and when someone will be there to let the tech in.
• Whether the customer has a service agreement, if your intake can check it.
• Date and time of the call and a link to the recording or notes.

Mark fields as unknown rather than guessing. A ticket that says 'equipment type unknown, unit on the roof' is more useful than one that confidently names the wrong system.

4. Set the escalation rules for each category

• Emergency: reach the on-call tech immediately by phone, with the ticket sent by text. Escalate to a backup and then a manager if there is no acknowledgement within your set window.
• Urgent: send the ticket to the on-call tech, who decides on timing. Escalate only if there is no acknowledgement.
• Routine: create the ticket for the morning and tell the caller when to expect a call back.

Write down who can override a category. A tech who knows a customer's equipment may decide an urgent call needs to go tonight, and the rules should allow that.

5. Review the rules every week at first

In the first weeks, compare what the ticket said with what the tech found on site. Look for calls that were sorted into the wrong category, questions callers could not answer, and fields techs still had to ask for. Adjust the script and the definitions, then keep a short log of what changed and why.

Useful measures are simple: how many after-hours calls came in, how complete the tickets were, how long it took to reach a person on safety calls, and how often techs still had to call back for basic information.

Where automated intake fits

Once the rules exist on paper, they can be run by a person, an answering service or an automated intake that answers after hours, asks the same questions, creates the ticket and escalates by your rules. The rules come first either way. Automation without them only makes inconsistent answers faster.