Proposed capability · not available
How HVAC Reception would work
A step-by-step walk through the proposed call flow — what happens on the call, what your company decides in advance, and where people take over. This is a design, not a working product.
Vendors describe AI receptionists for HVAC in broadly similar terms. Avoca’s HVAC page describes answering, identifying the issue, booking the job and escalating to a CSR with context. Smith.ai’s HVAC page describes structured intake questions — system type, system age, service needed, urgency, property details and scheduling preference — and routing by service type with escalation thresholds the company defines. Those are their descriptions; we have not tested them.
The HVAC Reception concept follows the same broad shape but puts the weight on two places most demonstrations skip: the rules your company writes before any call, and the handoff at the end of it.
Before any call: your rules
Nothing in the flow below works without decisions only your company can make. The call-intake checklists set these out per call type. At minimum:
- Which call types and conditions are urgent, by time of day.
- Your written procedure for safety-sensitive calls, including exact wording.
- Who is on call, who is their backup, and how long before the backup is contacted.
- Which appointment windows, if any, can be offered without a person.
- Exact wording for any fees callers must be told about.
- Your service area, hours, holidays and closures.
The proposed call flow
1. Answer and identify the company
The call is answered in your company’s name. Depending on your configuration, it answers every call, only after hours, or only when your team does not pick up (overflow).
2. Understand why they are calling
The caller explains in their own words. The system maps the call to one of your call types — no heat, no cooling, maintenance, estimate, plan member, warranty, billing, reschedule, technician arrival, commercial, tenant or property manager — and keeps the caller’s words for the summary.
3. Ask the safety question
On every service call: is there a gas odor, a carbon monoxide alarm, a burning smell or smoke? A yes goes straight to your safety-sensitive procedure. The system would use only your approved wording and would not diagnose.
4. Capture what the next person needs
The fields from the checklist for that call type — for example, for a no-heat call: who is in the home, system type if known, the service address and access notes, and a callback number read back digit by digit.
5. Apply your routing rules
The call is routed by your rules, not the software’s judgment: escalated to a person now, recorded as an appointment request or booked into a released window, or added to the callback queue.
6. Tell the caller what happens next
Exactly what was recorded, who will act and by when. Nothing unauthorised: no arrival time promises, no prices outside your wording, no “a tech is on the way” until a person has confirmed.
7. Hand off and confirm
A handoff goes to the named receiver in the format they need. Urgent handoffs wait for acknowledgement and escalate to a backup if none comes.
8. Summarise and log
Every call — including spam and wrong numbers — produces a call summary and appears in one log your office reviews.
Where people stay in charge
| Decision | Who makes it |
|---|---|
| What counts as urgent | Your company, in writing |
| What callers are told about safety | Your company’s approved procedure |
| Whether a technician is dispatched | Your dispatcher or on-call technician |
| Prices, fees and exceptions | Your office |
| Anything the rules do not cover | A person, via transfer or callback |
What is not built
None of this exists as software. There is no phone number, no integration with field-service software, no pricing and no customers. The flow is published so HVAC offices can judge whether this design would help — and so the planning work behind it can be used today with any answering option. See about this preview for more.
Sources for vendor descriptions
Vendor statements above are those companies' own descriptions of their products, read on the dates shown. They are not verified by us and may have changed. Check current details with each vendor.
- Avoca — AI CSR for HVAC businesses — read 2026-09-26
- Smith.ai — Receptionist services for HVAC companies — read 2026-09-26
- Avoca — AI CSR features that matter during busy season — read 2026-09-26
Frequently asked questions
Would callers know they are talking to software?
The concept's position is that callers should never be misled. The greeting would identify your company, and whether and how the system identifies itself as automated would be stated openly in your configuration, not hidden.
What happens when a caller asks something the system cannot answer?
It would record the question in the caller's words and route it — as a warm transfer where your rules allow, otherwise as a callback task with an owner. It would not guess.
How long would setup take?
We cannot say; nothing has been built. The honest answer is that most of the work would be on your side: writing down the rules in the call-intake checklists. That work is useful whichever option you choose.
Could it take payments or look up customer history?
Not in the proposed design. Some vendors describe payment collection and CRM lookups; the concept deliberately starts narrower, with intake and handoff, and has no integrations.
When will it be available?
There is no launch date. HVAC Reception is a concept preview published to test whether the design is useful.