The no-cool emergency script, step by step

The no-cool emergency script for HVAC inbound has six questions in a specific order. The first two filter for genuine emergencies (vulnerable occupants, dangerous indoor temperature). The next two qualify the system status (when it stopped, what it's doing now). The last two set up the dispatch (location, access, payment expectations). Running this script every time — same six questions, same order — separates the true emergencies needing same-day dispatch from the urgent-but-not-emergency calls that book for tomorrow, and prevents both the "missed a real emergency" mistake and the "dispatched a truck for a customer who could have waited" mistake.

The 30-second version

Six questions, in order:

1. Is anyone in the home elderly, very young, or with a medical condition?

2. What temperature is it inside the house right now?

3. When did the system stop cooling? Today, yesterday, this week?

4. What does the unit do when you turn it on — silent, fan only, weird noise, ice on it?

5. Address and access — anyone home this afternoon?

6. Are you the homeowner, and do you have a credit card on file or for payment after service?

Questions 1-2 determine emergency vs urgent. Questions 3-4 give the dispatched tech enough to bring the right parts. Questions 5-6 confirm the dispatch can actually happen.

Why the order matters

The wrong order ruins the call. Most CSRs (and most untrained AI scripts) start with "What seems to be the problem?" — a generic open-ended question that produces a 4-minute monologue from a stressed customer, with the emergency information buried in the middle. The structured order above gets the emergency-determining information in 30 seconds and reserves the open-ended discussion for after you know whether you're dispatching.

Question 1: vulnerable occupants

"Is there anyone in the home who's elderly, very young, or has a medical condition that needs the AC working today?"

This is question 1 because no other answer changes the dispatch decision more. A 78-year-old with a heart condition in an 88°F house is a same-day dispatch even if every truck is already booked. A pair of healthy adults in the same house can wait until tomorrow if needed.

The phrasing matters. "Is anyone vulnerable?" gets evasive answers because customers don't want to be dramatic. The specific list ("elderly, very young, medical condition") gets honest answers because each category is concrete.

Question 2: actual indoor temperature

"What's the temperature inside the house right now? You can usually see it on your thermostat — or just rough is fine."

The combination of indoor temperature and vulnerable-occupant status determines emergency level:

Vulnerable occupant + 85°F+: same-day dispatch, top priority

Vulnerable occupant + 78-84°F: same-day dispatch, standard priority

Non-vulnerable + 88°F+: same-day if capacity allows, tomorrow if not

Non-vulnerable + 78-87°F: tomorrow first slot

Non-vulnerable + under 78°F: tomorrow standard slot

Indoor temperature is the proxy that prevents "my AC is broken" calls from all being treated identically. The customer at 75°F whose AC just won't go below 73°F is a real service call, but they're not in distress. The customer at 89°F with a 6-month-old upstairs is a real emergency.

Question 3: timeline

"When did it stop cooling — was it today, yesterday, earlier this week?"

Timeline tells you two things. First, whether this is a sudden failure (likely component issue, often a quick fix) or a gradual decline (often refrigerant, often a longer service). Second, how much the customer has been managing the discomfort — a customer who's been at 86°F for two days is more committed to today's dispatch than a customer who noticed an hour ago.

Question 4: symptoms

"When you turn the system on, what does it do? Silent? Fan running but no cool air? Noise? Any ice on the unit outside?"

This is the closest thing to a technical question in the script, but it's structured as multiple-choice so any customer can answer. The four most diagnostic patterns:

Silent (no response at all): often electrical — breaker, capacitor, control board

Fan running but no cold air: often refrigerant or compressor

Loud or strange noise: bearing, motor, or compressor issue

Ice on the outdoor unit or refrigerant line: low refrigerant or airflow blockage

The tech going to the call gets these symptoms in the work order. Truck stocking adjusts. Diagnostic time on site drops 15-30 minutes per call.

Question 5: location and access

"What's the address, and is someone going to be home this afternoon or evening to let us in?"

Access is the dispatch killer that doesn't show up in the script if it isn't asked. Customer requests same-day, technician arrives at 4:30pm, nobody's home, key isn't where they said, garage code doesn't work — that's two billable hours lost and a customer relationship damaged. Confirming access upfront prevents the most common dispatch failure.

Question 6: identity and payment

"Are you the homeowner, and how are you planning to handle payment — card on file, pay after service, financing?"

Renter callbacks where the landlord has to authorize service waste hours of dispatch time. Customer expectations on payment that don't match shop policy waste hours of awkward end-of-job conversations. Getting both upfront takes 20 seconds and prevents 95% of the post-service friction.

Where AI handling makes this consistent

Six questions in order, every time, regardless of how stressed the customer is, regardless of how the CSR is feeling that afternoon, regardless of whether this is call 3 of the day or call 47.

Humans drift on emergency scripts. They skip question 1 when the customer immediately says "my AC is broken." They skip question 2 when they hear urgency in the voice. They skip question 4 when they're behind on volume. Each skip costs something — a missed emergency, a wasted dispatch, an undersupplied truck.

An AI Employee on inbound calls trained on the six-question script runs all six every time. The emergency on call 47 of the day gets the same treatment as the emergency on call 3. The dispatcher gets a structured work order with the answers in the same fields every time. Truck stocking improves. Diagnosis-on-site time drops. Customer outcomes improve, and the safety bar holds.

The closing line

After the six questions, the close is short:

"Okay, [first name], here's what I'm doing — I'm booking you for [today at X / tomorrow morning], your tech will be [name], and you'll get a text 30 minutes before arrival. If your indoor temperature gets above 88°F before then, call us back immediately and we'll adjust. Sound good?"

The 88°F callback line matters. It tells the non-vulnerable customer they can escalate if things genuinely get worse, which removes the pressure to argue the urgency level upfront. And it tells the vulnerable-occupant customer that you're watching the situation, not just dispatching and forgetting.