HVAC AI receptionist: missed-call and after-hours capture

What it is

A missed-call capture agent answers the calls your office cannot. It picks up when the line rings out during the day because everyone is on a job, when the office is closed, and when a heatwave or a freeze triples the volume. It works out what the caller needs, looks up the customer, checks real technician availability, books the job with an arrival window, and writes it to the dispatch board with the lead source attached. When the call is an emergency, it gives a safety instruction and alerts the on-call technician. When the call is out of scope, it says so and takes a message.

The call shape is short: greeting and disclosure, intent, address and callback capture with read-back, availability and window, confirmation, write, close. Two to three minutes is normal. Most of that is the caller talking, often while standing next to the broken unit.

Owner-operators buy this as an AI receptionist or an AI answering service for contractors. Multi-branch groups buy it as overflow and after-hours automation for dispatch. Same job, different volume, deeper integration.

Who buys it

• Owner-operators and office managers at one- to ten-truck HVAC, plumbing and electrical companies. The trigger is usually a week of counted missed calls, or one lost install job that a competitor booked at 7 p.m.
• Multi-branch home-services groups replacing a message-taking answering service that cannot see the schedule, or thinning a central call centre's night shift.
• Franchise operators who need the same script and the same booking rules across many locations and one field-service platform.

Budget owner: the owner or general manager. In groups, the call-centre or operations lead, with the field-service system administrator signing off on the integration.

KPIs

Count missed calls for one week before you deploy, by hour. That baseline is the whole business case. Then track the strip above: answer rate across all hours, jobs captured from calls that would have rung out, booking containment, address and callback accuracy, emergency hand-off time, and voice-to-voice latency on the turns that read the dispatch board.

Two measurement traps. "Captured" means a job on the board or a dispatch-ready record with a confirmed address and callback number, not a call that ended politely. And most missed calls in this trade happen during the working day, so a deployment that only covers nights is measuring the smaller half of the problem.

Demo script

Run the full script from the demo guide. The condensed version, with the traps that separate a product from a demo:

1. Overflow entry and greeting. Call the main line and let it ring past the count you set. Pass: the agent answers, discloses that it is an AI, and gives the recording notice without being asked.
2. Intent with interruption. Start describing an air conditioner that stopped, then cut in mid-offer with "actually it is only the upstairs unit". Pass: it stops talking and takes the new detail. Fail: it finishes its sentence and offers the old slot.
3. Ambiguous address. Give "42 Oak" in a town that has an Oak Street and an Oak Avenue. Pass: it asks which, then reads the full address back with postcode or ZIP and asks about a unit number.
4. Phone read-back. Say your callback number quickly. Pass: it reads the number back digit by digit and waits for a yes. Fail: it repeats the number as a single chunk or skips confirmation.
5. Time window. Ask for "tomorrow afternoon". Pass: it names the date and offers the arrival windows the dispatch board actually has, such as twelve to four, rather than inventing a time.
6. Eight seconds of silence after it offers a window. Pass: a short prompt, then a graceful hold or a message option. Fail: it hangs up, or repeats the whole offer.
7. Emergency injection. Say "hang on, I think I can smell gas near the furnace". Pass: it drops the booking, tells you to leave the house and call the gas emergency line, and alerts the on-call technician in the same turn. Fail: it keeps offering windows.
8. Out-of-scope request. Ask for a quote on a new roof. Pass: it says this is not a service you offer and asks whether to leave a message. Fail: it books a "roof" job.
9. Confirmation and write. Accept a window and watch the job appear on the sandbox dispatch board with the address, window, job type, notes and lead source.
10. System down. Have the sandbox connection disabled and call again. Pass: it says it is taking details, captures a full record and promises a callback within the time you configured. Fail: it says "you are booked".

Score each trap pass or fail. A vendor who wants to run the demo from their own audio has not passed the demo.

Compliance notes

This use case is inbound, and a call the customer initiates is outside the TCPA consent rule in the United States. Recording is the live issue: federal law is one-party consent but roughly a dozen states require all-party consent, so the agent should announce recording at the start of every call. If the agent later sends an SMS confirmation or places a callback, that is an outbound artificial-voice or text contact and needs prior express consent and the 8 a.m. to 9 p.m. window in the customer's local time. In the United Kingdom, a recording is processing of personal data under UK GDPR; the agent should say so at the start and the vendor should document the lawful basis. Any follow-up marketing call by the agent falls under PECR Regulation 19 and needs specific prior consent. In Australia, surveillance-devices laws differ by state and several require all-party consent, so announce recording; any outbound follow-up sits inside the telemarketing hours of Monday to Friday 9 a.m. to 8 p.m. and Saturday 9 a.m. to 5 p.m. and must respect the Do Not Call Register. The compliance rows for your regions are listed on this page. They are informational, not legal advice.

Build or buy

Buy a packaged product if you are a single-location contractor on a mainstream field-service platform; the integration and the overflow forwarding are the hard parts and vendors have done them. Consider a platform or a build if you run many locations with custom booking rules, zone logic or a membership tier that changes what the agent may promise. In both cases the acceptance test is the same: a job on your own sandbox dispatch board during the demo, and a gas-smell call that gets the safety instruction in one turn.