The HVAC AI dispatch phone agent is a pre-built Sawy template that answers every service call, captures equipment and symptom details, dispatches the right technician, handles emergency no-heat/no-cool situations, and books routine maintenance — 24/7, including weekends and holidays when HVAC emergencies peak.
This page covers deployment: what the template does out of the box, the sample dialogues it handles, the integrations and write actions it performs in each field-service platform, the tuning tips that matter most for HVAC, and where this template is the wrong fit. For the broader market case and ROI math, see the AI answering service for HVAC companies page.
Where this template fits
| Business shape | Fit | Notes | |---|---|---| | Solo operator, predictable hours | Strong fit | Template handles routine; you take exceptions | | Small team with a front desk | Strong fit | Template handles overflow + after-hours | | Multi-location with central reception | Good fit | Configure separate rules per location | | Enterprise with complex routing | Partial | Use as a base; expect heavier customization | | Highly regulated (healthcare/legal first-touch) | Limited | Use only with explicit human-handoff tier |
What This Template Ships With
This is what you get when you select the HVAC Dispatcher template instead of building a generic Sawy install from scratch. The pre-built configuration includes the intake flow, emergency triage logic, dispatch handoff, and field-service software hooks that are unique to HVAC dispatch — none of which a Customer Support or Appointment Booker template carries by default.
Sample Conversation
AI: "Thank you for calling Comfort Pro HVAC. This is Jake. How can I help you?"
Caller: "My air conditioning isn't blowing cold air and it's 95 degrees in here."
AI: "I'm sorry to hear that — let me get a technician out to you as soon as possible. Can I get your name and address?"
Caller: "Mike Thompson, 1240 Cedar Lane."
AI: "Thanks, Mike. Do you know what type of AC unit you have — central air, window unit, or a heat pump?"
Caller: "Central air. I think it's a Carrier."
AI: "Got it. Is the unit running at all, or is it completely off?"
Caller: "It's running but just blowing warm air."
AI: "Understood. I have a technician available this afternoon between 2 and 4 p.m. Would that work for you?"
Caller: "Yes, that's perfect."
AI: "You're all set. I'll text you a confirmation with the technician's name and a 30-minute heads-up before they arrive. Is there a gate code or anything our tech should know about accessing the unit?"
The AI captured the equipment type, symptoms, urgency level, property access details, and booked the service window — giving the technician everything they need before arrival.
Integrations Included — Specific WRITE Actions
What the agent actually does in each connected system. Unlike a generic CRM hookup, these write actions are scoped to the HVAC dispatch workflow:
- ServiceTitan: creates the job with caller-confirmed address, assigns to the dispatch zone matching the service area, attaches the call transcript and equipment summary to the job notes, fires SMS to the dispatched tech with arrival window and access notes. For emergency tickets, the job posts to the on-call queue rather than the next-day board.
- Housecall Pro: creates the service request with appointment type (Emergency / Maintenance / Diagnostic), pre-populates the customer record with phone + address + equipment notes, assigns to the tech with the smallest current route gap, attaches the call recording link to the job.
- Jobber: creates a new work order with auto-generated title (
{Symptom} — {Address}), pulls the client record if the phone number matches, schedules the visit on the calendar with the duration block matching the appointment type (Diagnostic: 1hr, Emergency: 2hr, Maintenance: 1.5hr). - FieldEdge: creates the dispatch ticket and assigns to the tech route by zone + skill match. For commercial accounts, attaches the property manager contact and building/unit notes.
- Google Calendar / Outlook: drops the maintenance appointment on the relevant tech's calendar with the address as location, equipment summary in the description, and the customer's phone number in the title (so a glance at the calendar tells the tech who and where).
- SMS: two messages fire — one to the customer with the tech name and arrival window, one to the tech with the job summary, address, gate code, and equipment notes. For emergency dispatches, the tech SMS also includes the disclosed after-hours rate so they can reference it on-site.
- Zapier / Make: outbound webhook fires with the full call payload (transcript, intake fields, urgency flag, dispatched-to assignment) for connection to fleet tracking, inventory pull-lists, or quality-survey automation.
Setup in 3 Steps
- Select the template — Choose Templates → HVAC Dispatcher from your Sawy dashboard. This loads HVAC-specific intake questions, emergency protocols, and dispatch workflows.
- Customize your company — Add your company name, service area, technician roster, service types with pricing, emergency policies, and business hours. Connect your field service software for automated dispatch.
- Go live — Forward your business line and make a test call. Report an AC issue, verify the job is created, and confirm your technician receives the dispatch notification.
Enable after-hours emergency pricing disclosure. Callers who hear the rate upfront are less likely to dispute charges later, and it qualifies out price-shoppers before you roll a truck.
Who It's For
- HVAC contractors losing after-hours emergency calls to competitors
- Multi-technician companies needing automated dispatch and routing
- HVAC franchises standardizing phone handling across locations
- Commercial HVAC firms managing building maintenance contracts
- Seasonal businesses handling summer AC and winter heating surges
Can I customize the emergency triage criteria?
Yes — the template ships with season-aware defaults (no-cool is an emergency in July, a maintenance call in February), but the rule editor lets you change the keywords, the symptom-to-priority mapping, and the dispatch destination per priority level. Most HVAC companies leave the defaults alone for the first 30 days and tune only after they see real call data.
How does the gas-leak detection work, and what does it do?
Gas keywords (smell, leak, hissing) trigger a hard-coded safety branch that overrides any other conversation state — the agent tells the caller to leave the building immediately and call 911 or the utility's emergency line, then flags the call as critical to your team via SMS and email. This branch is not overridable from the configuration UI by design; turning it off requires a written request to support.
Can I configure different intake flows for residential vs. commercial?
Yes — the template has a residential and commercial branch at the second intake question. Commercial calls collect building name, unit, property-manager contact, and maintenance-contract reference; residential calls skip those fields and ask about access (gate code, dog, side entrance). You can disable the commercial branch entirely if your business is residential-only.
How do I configure season-aware emergency rules?
In the rule editor, each emergency criterion has an optional calendar window. No cooling with the window Jun 1 – Sep 30 flags as emergency; outside that window, the same intake routes to standard maintenance booking. You can also set temperature-trigger rules tied to a weather API if you want priority handling automatically activated on extreme-weather days.
A Second Sample Call — After-Hours Furnace Emergency
A different shape of call this template handles well: weekend emergency, urgent triage, on-call dispatch.
AI: "Comfort Pro HVAC after-hours service, this is Jake. Are you calling about an emergency?"
Caller: "Yeah, my furnace just stopped. House is dropping below 60 and I have a six-month-old."
AI: "Understood — that's a priority dispatch. Can I confirm the address on file is 1240 Cedar Lane?"
Caller: "Yes."
AI: "Do you smell any gas, or hear unusual noises from the unit?"
Caller: "No gas smell. It's just totally silent."
AI: "Good — no safety hazard. After-hours emergency dispatch is $189 plus parts. Can you confirm you'd like a technician sent now?"
Caller: "Yes, please."
AI: "I'm paging Marcus, our on-call tech. He'll text you within five minutes with an ETA — typically 45 to 75 minutes for your zone. Stay warm. If anyone in the home develops symptoms, call 911."
The AI confirmed the address from file, ruled out a gas-leak emergency, disclosed the after-hours rate (qualifying out price-shoppers before dispatch), paged the on-call tech, and gave the caller a realistic arrival window. The transcript and dispatch trigger fire automatically into ServiceTitan.
HVAC-Specific Tuning Tips
Three configuration choices that matter more for HVAC than for most verticals:
- Season-aware emergency criteria. "No cooling" in February is a routine maintenance call; in July it's an emergency dispatch. Configure rules that key off both the symptom and the calendar.
- Refrigerant and parts disclosure boundaries. Don't let the agent quote replacement compressor pricing — those quotes need an on-site diagnostic. Configure the agent to acknowledge the question and book the diagnostic instead.
- Membership upsell timing. The right moment to offer a maintenance plan is after the emergency is resolved, not during the panicked first call. Configure the offer for the SMS follow-up, not the live conversation.
When Not to Use This Template
Honest fits: this template is wrong for HVAC distributors selling to contractors (B2B sales cycle, not service dispatch), and wrong for new-construction installs (long lead-times, blueprint review, not a phone-bookable workflow). Use the Lead Qualifier template for those instead.