A 5-truck Baltimore-area residential HVAC shop entered February 2026 with a problem most of its competitors share: a tune-up list that wasn’t getting called, a phone that wasn’t getting answered after 5pm, and a Google profile sitting at 73 lifetime reviews while the local-pack winner had 411.
The situation
The shop runs five trucks across Baltimore County and Anne Arundel, with two NATE-certified senior techs, two mid-level techs (one EPA 608 Universal), and a junior on a ride-along. The owner handles installs and quotes; his wife runs the office, processes invoicing, and tries to keep the dispatch board sane.
The tech mix is roughly 70% residential service (no-cool, no-heat, blower-motor, condensate, thermostat swaps), 20% maintenance plan tune-ups, and 10% replacement installs. Average ticket: $312 service, $7,400 install.
The shop had a maintenance plan with 412 members. On paper, that’s a $58k/year recurring revenue floor plus first-call rights. In practice, the spring 2025 tune-up campaign reached 178 of those 412 members. The rest either booked late, complained, or quietly let their plans lapse.
The problem
The owner did the audit and found three leaks:
- The tune-up call-out list got worked manually by one person. Of 412 members, only 43% got contacted in time. The other 57% — about $19k in tune-up revenue alone — leaked.
- The phone stopped at 5pm. A heat-pump-spec area where summer evenings produce no-cool calls until 9pm. After-hours voicemails sat until 7am. Best estimate: 11–16 paying-shaped opportunities per week, lost.
- Reviews were stuck. Customers loved the techs — the techs were great. Nobody was asking the customer for the review at the moment they’d just been saved from a 92° house.
What changed with the snapshot
The shop installed the HVAC Snapshot on a Monday in mid-February. By the following Monday, six workflows were live:
- AI receptionist — 24/7 inbound, books directly to the dispatch board, escalates true emergencies to the on-call tech.
- Missed-call text-back — any unanswered ring triggers an SMS within 47 seconds with a callback slot or one-tap book link.
- Maintenance plan renewals + spring tune-up campaign — staggered SMS + email outreach to the full 412-member list, with auto-booking links and reminder cadence.
- Review engine — 90-minute post-job-close SMS asking for a Google review, plus an auto-followup at 72 hours.
- Dispatch scheduling — zone-aware, tech-skill-aware (608 for refrigerant transfers, NATE for heat-pump diagnostics), drive-time-aware.
- Smart pipeline — every tune-up lead, no-show, and quote pending gets the next-step automation.
The owner’s wife trained on the system in about 9 hours total across week one.
The 60-day outcome
By day 60, the tune-up campaign had hit 384 of the 412-member list with at least 3 touches each. Of those, 326 had booked their spring service. That’s a +38% lift against spring 2025 — and that’s just the existing members.
Missed-call text-back caught calls the AI couldn’t. Of the ~3.5% of weekly calls the AI didn’t fully resolve, 87% of them re-engaged via the SMS and ended up on the dispatch board.
After-hours captures — calls received between 5pm and 8am, plus weekends — averaged 14 per week. At a residential conversion rate of about 65%, that’s nine new bookings per week of work that previously walked.
Reviews crossed 130 lifetime by week 8 and the shop started showing in the local pack for “HVAC repair Baltimore.”
The operator’s take
“We didn’t add a single CSR. We added a workflow stack. The phone stopped being the bottleneck and the dispatch board started running itself.”
The owner noted the membership growth was the real surprise. Twenty-four new maintenance-plan signups per month across 60 days — many of them coming from the after-hours captures, where the AI naturally offered the plan as the close on a same-week dispatch.
Note
Illustrative scenario for educational purposes. Your results will vary based on local market, service mix, and execution. The HVAC Snapshot is a configured toolkit, not a guarantee.
"We didn't add a single CSR. We added a workflow stack. The phone stopped being the bottleneck and the dispatch board started running itself."