An HVAC office that fields repair requests, maintenance enquiries and replacement consultations by phone faces a bottleneck familiar to field-service teams: calls arrive during installation, in the truck, after hours and during lunch. A missed call often means the homeowner calls a competitor. Zanus AI's AI Phone service answers that first call, captures the intent, books the visit or escalates the emergency, and records what happened. This guide builds a practical pilot scorecard to measure whether Zanus AI's call-answering performance matches your office's definition of success, and when to move from trial to production.
Why Measure Call Intake Separately from Office Work
An AI receptionist's job is not the same as your dispatcher's job. The AI Phone answers the incoming call, understands what the homeowner needs, and either resolves it on the call or hands it to your team with context attached. Your office then schedules the appointment, assigns the truck, and executes the work. Conflating these two workflows leads to false conclusions: a perfectly answered call can result in a missed appointment if your scheduler doesn't act on the lead, and a great dispatcher cannot recover from a call the AI sent to voicemail.
Your pilot scorecard must separate the AI's performance from downstream office performance. The AI Phone succeeds if it answers the call, determines whether the caller has a current emergency, a repair need, a maintenance contract renewal, or a replacement inquiry, captures the address, verifies that you serve that area, and either books the appointment or escalates appropriately. Your office succeeds if it acts on that information within your service standard. Both must succeed for the customer to feel heard.
Ground-Truth Calls: Defining Success Cases
Before the pilot launches, list the call types your business actually receives. HVAC offices typically field these categories:
| Call Type | AI Success Outcome | Measurement |
|---|---|---|
| No heat / no cooling (emergency) | AI recognizes urgency, confirms address in service area, escalates to on-call tech per your safety script | Emergency correctly routed; safety wording spoken |
| System repair (non-urgent) | AI books estimate visit, confirms symptoms, captures address and phone | Appointment confirmed; call summary includes system type and problem |
| Maintenance or tune-up | AI quotes flat rate if available, books or takes message if booked | Caller knows cost; appointment or follow-up request recorded |
| System replacement consultation | AI books in-home estimate, does not quote price | Estimate visit scheduled; address verified as in service area |
| Warranty or recall question | AI answers from knowledge base or transfers to technician | Question resolved or technical call offered |
Write these definitions down before the trial begins. Share them with your dispatcher and the technician assigned to on-call duty during the pilot week. When the pilot ends, you will score each call against these categories. If an incoming repair call is mistakenly classified as a maintenance question, the appointment type changes and your technician arrives unprepared. That is a measurement failure, not a software failure; it informs your training data.
Handling Wrong Addresses and Service-Area Mismatches
One of the most common pilot frustrations is a call from outside your service area that wastes your time or the homeowner's. Zanus AI's setup allows you to define your service zip codes and geographic boundaries. The HVAC and home-services configuration page describes how the AI checks the address against your service area during the call.
For your pilot scorecard, create a test case: a homeowner from a neighboring town calls to request a repair. The AI should either politely decline or offer a referral if you allow it, rather than booking an impossible visit. Record the call outcome and the caller's reaction. Did the AI handle the rejection gracefully? Was the homeowner offered an alternative? This scenario is not a failure of the AI; it is a validation that your geographic boundaries are correctly configured and respected during intake.
Disagreement often arises about whether a call from the edge of your service area should be accepted. Some HVAC offices will travel to a house three miles outside their standard zone if it is a high-value replacement job. Your pilot scorecard should include a decision rule: "Addresses within zip codes 10001, 10002, 10003 are automatically accepted. Addresses in 10004 are offered to the dispatcher for approval." This rule lives in the AI's configuration and can be changed after the trial.
Ambiguous Intent and the Follow-Up Conversation
Many homeowners call without a clear plan. A caller might say, "My air conditioner isn't working as well as it used to." That could be a refrigerant leak, a dirty filter, a failed compressor, or a desire to explore a newer system. The AI must gather enough information to route the call correctly without playing technician.
For your pilot, design an illustrative conversation and score how the AI handles it:
Homeowner: "Hi, my AC isn't cooling like it used to."
AI: "I can help you with that. Are you saying the air from the vents isn't as cold as usual, or that some rooms aren't cooling at all?"
Homeowner: "The whole house is warm. It's been running all day."
AI: "I understand. When did this start—today, or a few days ago?"
Homeowner: "A couple of days ago."
AI: "Got it. This sounds like a repair visit. I can book an estimate appointment this week. What's your address?"
In this scenario, the AI correctly moved from symptom to classification (repair, not replacement consultation) and moved toward a booking. Your scorecard should note whether the AI asked clarifying questions, how many back-and-forths occurred, whether it asked about the system age or type, and whether it eventually booked or correctly offered a callback. A successful outcome is not always an immediate appointment; it is clear routing and captured information.
Ownership and Tenant Calls
A property manager or tenant calls on behalf of a landlord. The AI needs to ask who pays the invoice, whether the caller has authority to approve the work, and whether the address is registered in your system. Some calls will require the owner's approval before you dispatch a technician. Zanus AI's knowledge-base capability allows you to script these scenarios.
For your pilot scorecard, document this case: a tenant calls to report no heat. The AI should ask whether the landlord or property manager has been notified, offer to take a message for the owner if not, and book the emergency visit if you serve that building. If the call is from a property manager requesting a quote for ten buildings, the AI should recognize the scope as outside a phone conversation and offer an office contact for a proposal. Record whether the AI routed the multi-property inquiry correctly or tried to book a single visit for a fleet of systems.
Building Your Knowledge Base and Safety Scripts
Zanus AI's AI Phone draws answers from your website and a knowledge base you configure. For an HVAC office, this typically includes service areas, pricing for flat-rate services (tune-ups, filters, diagnostics), hours, emergency protocols, and warranty policies. The AI Phone product page describes how the system searches your knowledge by meaning rather than keyword matching, so the way you write your scripts matters more than finding the exact phrase a caller might use.
Before the pilot, create a test document with entries like these:
Flat-Rate Services (Example entries for your knowledge base):
"Spring air conditioning tune-up: $119. Includes filter replacement, coil cleaning, refrigerant check and system test."
"Winter heating system inspection: $89. Includes combustion analysis, thermostat check and safety wording for gas systems."
"Emergency service charge (after 5 PM or weekends): $150. Waived if repair is completed same visit."
Emergency Safety Wording (Example for gas smell):
"If you smell gas, please leave the house immediately, go to a neighbor's house, and call the utility company's emergency line or 911. Do not use any electrical switches or phones inside the house. We will respond as soon as the utility company clears the home."
Your pilot scorecard includes whether the AI correctly recited flat-rate pricing and whether it spoke safety wording word-for-word during an emergency call. If the AI paraphrases a safety message, the call should be flagged for training. If flat-rate pricing is always correct, you can rely on the AI to quote those items without dispatcher review.
Appointment Booking and Calendar Integration
Zanus AI integrates with your calendar to offer only time slots that are actually available. During the pilot, your dispatcher should manage the calendar as usual. When a call comes in, the AI offers the next three or four available slots within your service area, confirming the address first to estimate travel time.
An illustrative booking call might proceed like this:
Homeowner: "Can someone come out tomorrow?"
AI: "I can book you for a repair estimate. What's your address?"
Homeowner: "[provides address]"
AI: "Thanks. I can offer you tomorrow between 1 and 3 PM, or Wednesday morning between 8 and 10 AM. Which works better?"
Homeowner: "Tomorrow afternoon is good."
AI: "Perfect. I'm booking you for 1 to 3 PM tomorrow for a repair estimate. I have your phone number as [confirms number]. We'll text you a reminder the morning of the visit. Is there anything else?"
Your pilot scorecard measures whether the AI booked within your actual calendar windows, whether it confirmed the address and phone number, and whether it sent the appointment confirmation. If the AI offers a time that conflicts with your technician's schedule, that is a calendar-sync failure, not an AI failure. Fix the calendar sync before declaring the booking module ready for production.
Distinguishing Call Quality from Downstream Action
Your pilot should include a simple workflow log that separates the AI's responsibility from yours. Create a spreadsheet with these columns:
Call ID | Date/Time | Caller Type | AI Outcome | Info Captured (Y/N) | Address Verified (Y/N) | Appointment Booked (Y/N) | Escalated to Tech (Y/N) | Your Follow-Up Action | Your Follow-Up Completed (Y/N) | Notes
For each call, mark whether the AI did its job (answered, understood, routed) and whether your office did its job (acted on the lead). A call where the AI booked an appointment but your scheduler never confirmed it is an office failure, not an AI failure. A call where the AI took a message but routed it to the wrong person is an AI or configuration failure. These distinctions guide your decision whether to expand the pilot or adjust settings.
Handling Refusals, Hang-ups and Silence
Some callers will hang up when they hear an AI voice, either immediately or after a few seconds. Some will refuse to provide information. Others will sit silent. Your pilot scorecard should count these outcomes without judgment.
Use the pilot’s own completion log to identify calls that ended before the intended next step. Review the circumstances and the resulting office work rather than importing an unsupported industry abandonment percentage.
For a pilot, run the trial for at least one full week, ideally two weeks, to capture a representative sample. A single day of calls is too small to judge. If your office receives 20 to 30 calls per week, a two-week pilot yields 40 to 60 call records, sufficient to identify patterns in call handling and configuration adjustments.
Robocall and Spam Filtering
Zanus AI's AI Phone includes a robocall guard that gives telemarketers one polite goodbye and does not connect them to your team. During the pilot, monitor whether legitimate business calls are incorrectly blocked. For instance, if your supplier's automated order-confirmation system is treated as a robocall, adjust the filtering rules. Conversely, if your team is still receiving sales calls that should have been blocked, the guard is not configured strictly enough.
Your scorecard should include a row for "Robocalls received by team" and "Likely legitimate calls declined." After two weeks, you will see whether the guard is helping or whether it needs tuning. This is not a failure of the AI Phone; it is an expected part of setup.
Response Time and Caller Experience
Zanus AI's product page states that the AI answers on the first ring, 24/7. During the pilot, measure how quickly the caller hears a greeting. If your office forwarded its main line to the AI Phone as part of setup, the call should connect within one to two seconds. If the greeting takes longer, or if the caller hears ring-back tones or silence, report this to Zanus AI support.
Also note caller satisfaction anecdotally. If customers mention to your team that the AI was helpful or rude, ask for details. A caller who says, "The AI couldn't understand me" might speak with an accent, be in a noisy environment, or expect a menu-driven phone system. Context matters. Your dispatcher's impression is valuable feedback for the scorecard but should not be the only measure; the call transcript and booking confirmation are more objective.
Escalation Paths and On-Call Coverage
Zanus AI's configuration allows you to route emergency calls to an on-call technician. For your pilot, assign one team member to on-call duty during the trial week and provide them with a mobile number registered in the system. When an after-hours or emergency call comes in, the AI should recognize the urgency, speak your safety script if applicable, and ring the on-call phone.
Test this scenario during the pilot: a call comes in at 7 PM on a Tuesday reporting no heat. The AI should detect the emergency, confirm the address is in your service area, ask clarifying questions (how old is the system, is there a backup heat source), speak your safety wording if needed, and transfer to the on-call tech. The on-call tech should receive an announced transfer: "This is a no-heat emergency call from [address]. The caller is holding." The tech then presses 1 to accept or declines if overloaded. Track whether the transfer succeeded, the call connected, and the tech understood the situation.
Acceptance Criteria and Decision Rules
Before the pilot begins, write down the criteria that will determine whether you expand AI Phone to full production or negotiate changes. Examples might include:
Must Have: AI answers 95 percent of calls within two seconds. All emergency calls are correctly classified and escalated. Flat-rate pricing is quoted accurately 100 percent of the time. Addresses in service area are booked; addresses outside are declined politely.
Should Have: At least 70 percent of repair and maintenance calls result in booked appointments without dispatcher follow-up. Callbacks and messages are routed to the correct person 90 percent of the time. After-hours calls are handled per policy (AI service vs. message-only) and recorded.
Nice to Have: Spanish-speaking callers are recognized and offered a Spanish-speaking team member if available. Repeat callers are greeted by name. Multi-location inquiries are flagged for office handling.
After the two-week pilot, review the scorecard against these criteria. If the must-haves are met and most should-haves are met, move to production. If must-haves are missed, work with Zanus AI support to adjust configuration (knowledge base, routing rules, calendar sync) or disable the feature temporarily and retry after changes.
Scaling from Pilot to Production
If the pilot succeeds, your transition plan should address these operational changes:
Staff training: Your dispatcher and on-call techs need to understand how the AI routes calls, what information is pre-filled, and how to use the call summary. Allocate one hour for a walkthrough with the team using real pilot calls as examples.
After-hours coverage: Decide whether the AI handles all after-hours calls, takes messages only, or routes emergencies to on-call while other calls go to voicemail. This is your policy, not the AI's limitation. Zanus AI's configuration allows each choice.
Incoming lead capacity: If the AI successfully books more appointments than your current technician schedule allows, you have a good problem: you need more labor or must raise prices. Do not disable the AI to avoid capacity; optimize your scheduling instead.
Knowledge base maintenance: Prices, service areas, and hours change. Assign one person to review and update the AI's knowledge base quarterly. New technicians, updated flat-rate pricing, and seasonal service offerings all belong in the knowledge base.
Call review cadence: After going live, continue spot-checking calls weekly for the first month, then monthly. Listen to a few recordings, read the transcripts, and verify that the AI's performance remains consistent. If you notice drift—more misclassifications, fewer complete bookings—investigate and retrain.
Frequently Asked Questions About HVAC Pilots
Q: Will the AI ever replace my dispatcher or technician?
No. The AI Phone answers incoming calls and captures information. Your dispatcher schedules, routes, and manages the truck. Your technician sells and performs the work. The AI's job is to make sure no call falls through the cracks while your team is busy.
If the intended recipient is unavailable, demonstrate the configured fallback and the recorded callback request. Any response promise must be one the responsible team has agreed it can fulfil.
Q: Can the AI handle multi-trade calls (someone calling for plumbing instead of HVAC)?
If you operate both trades, you can configure separate AI departments for each. A caller saying, "I need a plumber," will be routed to the plumbing department. The call transcript will note the trade. If you only do HVAC, the AI can politely redirect or offer a message.
Q: How much does Zanus AI cost?
Pricing is available on the home-services page, and it is per company, never per seat. A 7-day free trial requires no credit card, so you can test your exact workload before deciding. Renewal billing occurs at then-current pricing, so confirm pricing in your agreement.
Q: What if our business hours change or we add a location?
Talk to Lisa, the AI assistant, or update the settings yourself. Hours, service areas, departments, and team members can be changed anytime. The AI adapts on your next call.
Your pilot scorecard is a tool to turn assumptions into data. Before launch, commit to measuring these call outcomes: answering rate, correct classification, address verification, booking completion, escalation success, and customer follow-up. After two weeks, you will know whether Zanus AI's AI Phone is the right fit for your HVAC office. The decision to expand to production should rest on this evidence, not on vendor promises or fear of missing calls. Build the scorecard, run the pilot, review the data, and decide.
Official sources and related guides
This independent Sysevo guide uses the following official documentation. The workflow and trial scenarios are evaluation proposals, not reported customer results or a hands-on benchmark.
- Zanus AI official product documentation
- Zanus AI official supporting guide
- Macro for Contractors: Hand Over Projects Without Lost Decisions
- GoHighLevel Voice AI for Trades: Control Customer Promises
- Zanus AI for home services
Compare the same requirements with the relevant Sysevo product, Voice Agents and CRM. Review Sysevo plans and pricing or book a demo to discuss the proposed setup. Sysevo sells its own business software and is not affiliated with the competitors discussed here.



