Direct answer
An HVAC AI receptionist keeps the number customers already call and answers when the truck is on a roof or the shop is closed. It sorts no-cool, no-heat, maintenance, and replacement quotes. It books the ones that can wait and transfers the ones that match your escalate rules. The owner is still in the loop — just not as the default voicemail.
HVAC call paths that should not share one script
How long, indoor temperature if known, is the outdoor unit running, filter last changed, occupancy. Then book a diagnostic or escalate.
Same intake plus weather and vulnerable occupants. After-hours no-heat is a written rule, not a vibe.
These should almost never page the owner. Collect address, system count, and a calendar window.
Collect home size if they know it, system age, fuel type, and whether they want a quote visit. Do not invent a price on the call unless you published one.
Realistic HVAC calls
“The AC died and my kids are home.”
No-cool + occupancy. Get the address, how long it has been down, and whether anyone is heat-sensitive. Apply your same-day rule. Transfer if that rule says the on-call tech must hear it.
“Furnace will not ignite and it is 19° tonight.”
No-heat after-hours. Collect occupancy and any carbon-monoxide alarm status you want asked. If CO is suspected, follow the safety script you wrote — usually “leave the area and call emergency services,” not a parts guess.
“I just need a spring tune-up.”
Book it. Ask how many systems and whether they are an existing maintenance customer. This is not an owner transfer.
“Your tech was here yesterday and it is warm again.”
Callback / warranty. Pull the address and yesterday’s work, then route to the original tech or service manager.
“What do you charge to replace a 4-ton?”
Answer only approved ranges or book a quote. Do not let the model invent a turnkey price from a phone description.
“Can you come at 7 tonight? I work days.”
Scheduling intent. Offer configured windows. If evening capacity is owner-only, transfer after the intake is complete.
No-cool vs no-heat vs after-hours
| Situation | Usual AI action | Usual human trigger |
|---|---|---|
| No cool, occupied, daytime | Intake + book diagnostic | Same-day capacity or VIP customer |
| No heat, occupied, dangerous weather | Intake + escalate rule | On-call transfer after required fields |
| Filter / thermostat how-to | Approved troubleshooting only | If they still have no heat/cool |
| Maintenance membership | Book on the calendar | Rarely |
| Existing-job callback | Identify job, then route | Original tech or manager |
| After-hours noise complaint | Morning queue | Only if you defined it as urgent |
Carbon monoxide, gas smell, or burning electrical smell should use your safety script. The receptionist is not the fire department and should not pretend to be.
Setup that survives July and January
Peak season is when voicemail costs the most and when sloppy AI is most visible. Write two escalate lists: summer and winter. Put service-area ZIPs, brands you will not touch, and after-hours windows in the same instructions. Keep the public number. Forward the miss.
If you already use a phone system such as Google Voice or a hosted PBX, Fix9 is the receptionist behind that number, not a reason to reprint magnets. Confirm the unanswered path with your current provider.
Write summer rules and winter rules separately
One generic “urgent if uncomfortable” instruction will page you for a filter and miss a no-heat call. Split the file. Summer: no-cool, occupied home, indoor temperature if they have it, outdoor unit running or not, filter age. Winter: no-heat, occupancy, weather, any carbon-monoxide or gas-smell script you approved with a licensed person — not with a marketer.
Put membership and tune-up language in a third block so those callers never hit the emergency path. Put “callback / you were just here” in a fourth. HVAC companies bleed time when a yesterday visit is opened as a brand-new lead.
If you refuse certain brands, refrigerants, or rooftop units, say it. Booking a truck for work you will decline is how owners start to distrust the receptionist.
Rehearse the heat-wave call and the January call
July, 4:40 p.m. “AC is blowing warm, two-story, kids upstairs.” The receptionist gets the address, how long it has been down, whether the outdoor fan is spinning if they can look, and whether they already changed the filter. It offers a diagnostic window you actually have. If your same-day list is full, it should say the next real window — not invent one — and transfer if your rule says occupancy plus no-cool still wakes a dispatcher.
January, 11:10 p.m. “Furnace will not stay lit.” Closed-hours greeting. Occupancy, indoor temperature if known, CO alarm state if you ask it. If the alarm is going off, the script should send them to fresh air and emergency services first. If it is no-heat without that alarm and your rule escalates occupied no-heat below a temperature you chose, transfer after the address. If they have heat in part of the house and can wait, morning queue.
Scheduling and after-hours without lying
Booking a tune-up is a good AI ending. Booking a no-heat emergency into next Thursday is a bad one. Use the appointment scheduling guide for calendar rules, and the after-hours guide for the night queue. The HVAC-specific work is deciding which intents are allowed to book themselves.
Do not promise that AI will cut no-shows or raise average ticket. Those outcomes depend on your follow-up and your techs. The receptionist’s job is a correct next action and a record the morning board can read.
Membership, filters, and the calls that should never page you
A large share of an HVAC inbound line is not broken equipment. It is “when is my tune-up,” “do you still have the filter size,” “can I add the other house to the plan,” and “what do you charge to look.” Those callers deserve a competent answer. They do not deserve the on-call tech’s dinner. Put the membership phone script in the same instruction file as the no-heat script so the model can tell them apart on the first question.
If you sell a maintenance plan, write the one-sentence description and whether the receptionist may book a member visit without a transfer. If members jump the queue, say how. If they do not, say that too, so the AI does not invent a VIP policy you will have to unwind.
Related AI receptionist guides
Frequently asked questions
Do I have to replace the number on the truck?
No. Keep Your Number. Forward unanswered or after-hours calls to a Fix9 line. Customers keep dialing the HVAC number they already saved.
How should AI handle no heat?
Collect the address, indoor temperature if they know it, system type if known, and whether anyone vulnerable is in the home. Apply your weather and occupancy escalate rules. Do not have the model invent a parts diagnosis.
What about no cool in a heat wave?
Same structure, different rule. Ask how long it has been down, whether the outdoor unit is running, and whether they already changed a filter. Book a diagnostic or escalate based on occupancy and your same-day policy.
Can it book maintenance instead of interrupting a tech?
Yes. Tune-ups, filter plans, and “how much for a new system” calls can stay with AI and land on the calendar. Transfer when they ask for you by name or when the no-heat / no-cool rule fires.
Should AI answer every call or only the misses?
Either. Many HVAC owners ring the on-call phone first during the day and send the miss to AI. After hours, AI-first with a short escalate list is common.
Keep the number people already call.
Add Fix9 as the answering layer: AI answers first, qualifies the request, books or routes the work, and transfers to you when the caller needs the owner.