An HVAC Phone Script for a Heat-Wave Monday

September 25, 20267 min readBy , founder of DispatchLine
A bucket under a kitchen sink catching a slow drip from a trap, cabinet door open, a towel folded beside it

The first real heat wave lands on a weekend. Saturday hits 95, Sunday hits 97, and every marginal condenser in your service area runs flat out for forty-eight hours and quits. You wake up Monday to a voicemail box that is full before seven and a phone that starts ringing again while you are listening to it.

By ten you have stopped answering, because every call you take is three minutes you are not spending dispatching the calls you already took. That is the day that decides your summer. Not because you can service everyone, you cannot, but because the customers you handle badly on the worst Monday of the year remember it in November when they are picking somebody to install.

The HVAC phone script, line by line

A phone script does not create capacity. Nothing creates capacity on a heat-wave Monday. What it does is stop the queue from being decided by who is willing to redial the most times, and stop you from being the bottleneck between a caller and a slot.

Concretely: the calls you forward get picked up in a couple of rings instead of going to a full mailbox. Every caller gets triaged against the rules you wrote rather than against how tired the person answering is by eleven. Every booking lands in a real window rather than “sometime today”. And you are freed to do the thing only you can do, which is move trucks. The mechanics of that call flow are in how the agent handles a call, and a script for an ordinary day is in answering phone calls script.

What it does not do is decide which of two customers matters more. You decide that in advance, in writing, and the ordering below is where most of the value sits.

Capacity arithmetic you can do on a napkin

Do this once, before the season, and the rest of the day gets easier to think about.

Say a normal summer weekday brings you 25 calls. A heat wave Monday can run at two or three times that. Take 70 as your working number. Now the supply side: four trucks, and on a no-cool day a tech gets through six calls if the drives are short and nothing turns into a compressor. That is 24 slots. Even if every one of those 70 calls was a real service call, and it is not, roughly two out of three callers are being told something other than yes today.

That is the whole problem, stated honestly. The question is not how to serve 70 calls with 24 slots. It is what the other 46 people hear, and whether they are still your customer on Wednesday. Put your own call count, truck count and calls-per-tech in and run it again; the ratio moves but the conclusion does not.

Triage when everything is an emergency

On an ordinary day “no cooling” is your emergency word. On a heat wave every single call is no cooling, so that word sorts nothing. You need a second layer, and it has to be written before the day arrives.

  • Occupant risk first. An elderly person, an infant, or someone on oxygen or with a medical condition in a house with no cooling goes to the top. Ask it directly and put it in the notes.
  • No cooling beats weak cooling. A system blowing 78 degree air is uncomfortable. A system blowing nothing at all in a house that is already at 88 is a different call.
  • Agreement holders next. If you sell a maintenance agreement and it promises priority scheduling, this is the day it is worth something or the day it is exposed as nothing. That is also why these calls are the ones worth selling, which is covered in the piece on selling an agreement on an inbound call.
  • Filter, breaker and thermostat checks before you roll. Ask whether the filter is filthy, whether the outdoor unit is running, whether the breaker is tripped, and whether the thermostat has batteries. Some fraction of your callers solve their own problem in ninety seconds. That is a slot you get back for someone who needs it.
  • Frozen coil gets an instruction, not a slot. Ice on the line set means turn the system off, leave the fan on, and give it a few hours. A tech arriving at a solid block of ice cannot diagnose anything anyway.

Anything electrical that smells like burning, or any carbon monoxide alarm on a system with gas heat, is not a scheduling question. That caller is told to leave the building and call 911 first.

The waitlist and the cancellation backfill

The 46 people you cannot see today are worth more than most shops treat them as. What they need is a true statement and a place in line, in that order.

A true statement sounds like: the first opening is Wednesday between noon and four, and you are on the list for a cancellation today. Not “we will try to squeeze you in”, which everyone has heard and nobody believes. If you promise a callback by end of day, the callback has to happen, and that is a discipline problem more than a software one.

Then work the backfill. Cancellations and short jobs open slots all day, and the shop that fills them is the one with an ordered list and a way to text twenty people at once to ask who can be home in an hour. Ask before texting, and put a STOP instruction in the message, which is the standard set out in our SMS terms.

What it should never promise on a day like this

Two failures cost more than the missed calls do.

The first is a window nobody can hit. If your trucks are running two hours behind by eleven, a noon-to-four window booked at eleven is a broken promise you have already made. Either you widen the window length in the portal for the surge, or you shorten that weekday’s hours until it passes, so the agent stops offering windows your trucks cannot reach. What a window promises a customer is defined in the arrival window glossary entry.

The second is a price. A caller asking what a capacitor costs, or what a new system costs, should get your diagnostic fee and an honest sentence that the rest depends on the equipment. An automated assistant answers only from the business facts you wrote in the portal, and if you never wrote a number it says the office will confirm rather than guessing one. That is exactly what you want on the day you are least able to supervise it.

What to do before the next one

Write the surge rules now, well before the next heat wave, not on the Monday. The occupant-risk question, the pre-roll checks, the widened windows, the waitlist text, and the point at which you stop selling today’s slots. Then hand them over once and they run the same at eleven at night as they do at eight in the morning. Planning for the whole season, not just the day, is in the seasonal demand piece, and what the monthly number depends on is on the page for what it costs.

FAQ

How many calls can it take at the same time?

Concurrency is the point of the whole thing. Ten people calling in the same minute all get answered in the same minute, which is not true of a single office line or a person on a headset. That is the specific failure a heat wave produces.

Should it tell callers we are booked out three days?

Yes, if that is true. A caller told the truth at 8 a.m. can make a plan. A caller told “we will try” and then not called back is gone permanently, and will tell the neighbor who referred them.

Can it recognize a maintenance agreement customer?

Not by lookup: it does not check callers against a customer or agreement list. You can add an intake question asking whether the caller has a maintenance agreement, so the office can apply your priority rule when it calls back.

What about the checks that avoid a truck roll?

Filter, breaker, thermostat batteries and whether the outdoor unit is spinning are all fair to ask, and a real fraction of callers fix it themselves. Anything past that, including anything involving refrigerant, a capacitor or opening a panel, is a technician’s job and the script should not go there.

Does it wake my on-call tech at midnight in July?

Only for what you put on the emergency list. Most shops keep overnight escalation for occupant risk, gas smells, carbon monoxide alarms and commercial accounts with a contract that says so. Everything else books for the morning.

Is this worth it for a two-truck shop?

Run your own arithmetic on the surge days rather than the average ones. If you lose twenty calls across four bad days a summer and your average repair ticket and close rate are what they are, that number is usually larger than a year of the monthly fee. If it is not, the answer is honestly no.

New field guides by email

Guides for home-service businesses on answering calls, call triage and after-hours coverage: the title, a short summary and a link for up to six of the newest guides on this site. At most one email every 30 days.

Optional: you do not have to give your email, but without it we cannot send you the guides. We use your email only to send these guides, and only after you confirm with the link in the email we send you. To prove your consent we also keep the time, IP address, country and page of the signup, and a hash of your browser's user agent. Controller: DispatchLine, 24 HaNahal Street, Petah Tikva 4927324, Israel; contact: privacy@getdispatchline.com. Your details are kept on this site's server, and the mail is sent through Amazon Web Services (USA). Unless you turn it off in Privacy choices, this site's optional Google and Meta measurement may also receive a hashed copy of the email you type here. We never sell your email. You may see and correct your details, or ask us to delete them from our mailing list: privacy@getdispatchline.com. Privacy policy

See how it handles your calls.

3 days free with 150 trial minutes, up to 8 minutes on any single call. Every feature is included. Your card is charged for the first time on day 4 unless you cancel before then. You make a test call and hear the agent yourself before your line is forwarded. After the trial: $149, $299 or $549 a month, by how many trucks you run. No per-minute charge, no minute bundle to run out of, no setup fee. Taxes where applicable. Cancel any time from your billing page.