Syntronia AI logo
Case Study

The After-Dark Call System

Residential HVAC, 5 techs4.6★ on Google, 88 reviewsColumbus, OH metro

Client identity withheld.

Results

$48K

Booked revenue in 90 days, at the shop's own prices

7 nights → emergencies only

Owner on the after-hours phone

58

After-hours calls booked by the phone assistant

59% → 68%

Booking rate on answered daytime calls

21%

Lost callers rebooked the same day

77% → 86%

Maintenance plan renewal rate

Company Profile

Company

Residential HVAC shop. ~$1.15M revenue, 4 techs plus the owner, and 1 CSR on weekdays. ~1,900 past customers and ~200 maintenance plan members.

Stack

Field-service management software, a VoIP phone system with call recording, the after-hours line forwarded to the owner's cell, and a payment processor with cards on file.

Operating Need

Take the owner off the night phone without missing emergencies, and book more of the calls the shop already answers.

The Challenge

The owner had carried the after-hours phone every night for nine years. Most night calls weren't emergencies: a thermostat question, a reschedule, a routine repair that could wait until morning. He answered them anyway, because the ones he missed went to competitors. During the day, the shop's one CSR answered most calls, but many ended without a booking, and nobody knew why. Membership renewals were handled when someone had time.

The Audit

We reviewed 60 days of after-hours call logs, scored a month of recorded daytime calls, and reviewed membership records.

Patterns Found

  • The owner answered about 55 after-hours calls a month, and only about 1 in 6 was a true emergency
  • After-hours calls he missed went to voicemail with no callback
  • 41% of answered daytime sales calls ended without a booking, often after a price question
  • Callers who hung up without booking were never contacted again
  • About 1 in 4 members didn't renew, and failed cards went unnoticed
  • The CSR had never had feedback on her calls

The owner didn't need to answer every night call. He needed the routine ones handled and only the real emergencies sent to him.

The Architecture

Three systems working as six parts, built around nights and the shop's single CSR.

Call Handling

An AI assistant answers every call after 6pm and on weekends in the shop's name, and picks up after 3 rings when the CSR is on another line. It identifies itself as virtual and books routine work into the next available slots.

Emergency Paging

Applies the owner's written rules. True emergencies, like no heat with an infant or elderly person at home, page the on-call tech with a summary; gas smells and carbon monoxide are sent to 911 or the gas company.

Call Grader

Scores every recorded call on booking, asking for the booking and offering the plan. The CSR gets a weekly coaching report with clips of her own calls.

Lost-Lead Rescuer

Texts every caller who hung up without booking the same day, with a real open slot.

Plan Renewals

Reminders 30 and 7 days before renewal, an instant card-update link when a payment fails, and one plan offer to non-members after a visit.

Monday Recovered Revenue Report

One page every Monday with night calls handled, emergencies paged, booking rate and dollars booked.

How the System Operates

The system handles nights, overflow and follow-up. The owner decides what counts as an emergency and still takes every one.

  • Emergency rules are written by the owner, and the AI never decides on its own what's urgent
  • The CSR answers first during the day; the AI covers overflow and after hours
  • Coaching reports go to the CSR privately first

How It Flows

  1. 1A call comes in, day or night
  2. 2The CSR or the AI answers and qualifies urgency
  3. 3Routine work is booked, emergencies page the on-call tech, and unbooked callers are rescued the same day
  4. 4Every call is scored, and every booking is logged on the Monday report

A summary and recording of every after-hours call is waiting for the owner each morning.

Implementation

StageFocusKey Results
Stage 1Call audit55 after-hours calls a month logged; about 1 in 6 true emergencies; baseline booking rate of 59%
Stage 2Setup and approvalEmergency rules, price list and service windows written by the owner
Stage 3Night launchAfter-hours Call Handling live, with every night call reviewed daily for two weeks
Stage 4Always-onDaytime overflow, Call Grader, lost-lead rescue and Plan Renewals live; Monday reports every week

Ownership

The shop now has night coverage and a coaching loop built on its own rules and calls.

Written emergency rules the AI follows exactly

Call scores and coaching clips for the CSR

A live member list with renewal dates and payment status

A recording and summary of every call, and every Monday report

Operational Impact

The owner now sleeps through most nights. Routine after-hours calls are answered and booked, and his phone rings only for the emergencies he chose. During the day, the CSR books more of the calls she answers, and callers who slip through get a second chance before they call a competitor. Memberships renew on schedule instead of when someone remembers.

Start Here

Bring us the process your company still runs by hand

Book a call

Case Studies

See more systems built and run for real operations

See other case studies