Optivanced Logo Go back to Portfolio
HVAC Technician working
VOICE AI & AUTOMATION

Meet Emily: The Voice AI Scheduler that Never Sleeps

How a custom Voice AI agent helped a mid-sized HVAC contractor capture 99% of calls, eliminate double bookings, and secure over $30k/mo in recovered revenue.

Call Answer Rate

99%

Double Bookings

Zero

After-Hours Capture

94%

Est. Monthly Gain

+$15k

The Business Context

Our client, a residential and light commercial HVAC company, was facing the classic "seasonal squeeze." During peak heat waves, call volume doubled to 110+ calls per day, overwhelming their two office coordinators.

Industry data shows that 80-85% of callers who hit voicemail won't call back. With an average emergency job value of $500-$800, every missed call was significant revenue leakage. They needed a way to capture every lead without hiring a 24/7 call center or abandoning their existing Google Calendar workflow.

The Baseline Problems

  • 22% Missed Calls: Spiking to 37% during peak weeks. Most after-hours calls (18% of volume) were lost.
  • Scheduling Chaos: Manual booking in shared calendars caused 3-5 double bookings per month and inefficient routing.
  • Staff Overload: Coordinators spent 70% of their day answering repetitive "Do you service my area?" questions.

The "Leakage" Funnel (Before)

100 Heat Wave Calls
Peak Demand
37 Calls Missed / Voicemail
Lost Revenue (~$18k potential)
Only 41 Booked Jobs
Low Efficiency

Meet Emily: The Voice AI Solution

We introduced "Emily," a natural language voice agent that lives on the phone line and integrates directly with the company's existing Google Calendar infrastructure.

Intent Detection

Emily intelligently categorizes calls into Emergency (No heat/cool, burning smell) vs. Routine (Tune-ups), prioritizing urgent jobs automatically.

Calendar Logic

Connected directly to Google Calendar APIs to read live availability, respecting travel buffers, technician skills, and service territory rules in real-time.

Structured Data

Captures critical details—gate codes, pet alerts, parking—and syncs them to the CRM, ensuring technicians arrive fully prepared.

Today 10:42 AM
My AC stopped working and it's 95 degrees inside!
I understand this is urgent. Since it's extremely hot, let's treat this as an emergency. I have a senior technician available at 2 PM today. Does that work?
Yes, please book that.
Done. I've booked James for 2 PM. Do you have any gate codes or parking instructions he needs?
GOOGLE CALENDAR Now

New Event: Emergency AC Repair

Tech: James • 2:00 PM - 3:30 PM

How Emily Works in Practice

Emily mirrors the logic of a skilled human dispatcher but operates at the speed of software. She doesn't just "take messages"—she actively manages the schedule.

1. Eligibility & Territory Check

Instantly verifies the caller's zip code and system type against company rules. Out-of-area jobs are politely declined to save technician drive time.

2. Conflict-Free Booking

Emily sees what humans sometimes miss. She enforces minimum travel buffers and never offers a slot that overlaps with an existing job or a technician's time-off block.

3. Emergency Triage

Keywords like "burning smell" or "no cooling" trigger emergency logic, unlocking premium same-day slots reserved specifically for high-value breakdown jobs.

Metrics & Outcomes (9 Months)

By turning the phone line from a bottleneck into an automated booking engine, the company saw immediate improvements in both efficiency and revenue.

Call Answer Rate

99%
Up from 78% baseline

Double Bookings

0 Incidents
Eliminated completely (was 3-5/mo)

Booking Conversion

57% of Calls
Up from 41%

Staff Time Saved

62% Reduction
In phone workload for office staff

Est. Monthly Gain

$15k+
From recovered missed calls

Customer Satisfaction

4.6 / 5.0
Up from 4.2

Implementation Timeline & Team

The project moved from discovery to full production in four sprints. We worked closely with the client's operations team and two lead technicians to minimize disruption during peak season.

Week 1 — Discovery

Call flow mapping, KPI definition, calendar access and basic territory rules were gathered directly from dispatchers.

Week 2 — Prototype

A voice prototype handled 10 common call types and was validated on live calls during low-volume hours.

Weeks 3–6 — Integration & Testing

Full Google Calendar API integration, routing rules, and technician buffers were implemented and tested across shifts.

Core Team

  • Product Lead: 1 (Operations liaison)
  • Voice Engineer: 1 (NLP tuning & telephony)
  • Backend Developer: 1 (Calendar & CRM sync)
  • QA & Field Tester: 2 technicians (live-call validation)

Client Feedback

J

Jason M., Operations Manager

"Emily removed the late-night call guessing game. Our techs arrive prepared, we no longer lose high-value emergency jobs, and customers actually tell us they appreciate the quick clarity on arrival times."

— Implemented across 8 service zones, measured after 90 days.

Technical Notes & Lessons Learned

  • Respecting technician travel time and skill tags was essential to avoid false positives in availability.
  • Small default buffers (15–30 minutes) prevented nearly all scheduling conflicts when combined with live calendar reads.
  • Customer scripts that asked two short clarifying questions increased booking conversion by ~8% in A/B testing.

Technology Stack

Google Calendar API Twilio / SIP NLP Engine (intent + entity) Node.js backend CRM sync (custom)

Stop Missing Calls. Start Booking Jobs.

See how a Voice AI scheduler can handle your phone lines 24/7, integrate with your calendar, and let your team focus on high-value work.