Automation Audit: Example HVAC & Plumbing Co.

What happens now. ~340 active maintenance-plan customers are tracked in a spreadsheet. Office staff manually check due dates, call customers to schedule the seasonal tune-up, and chase renewals when a plan lapses. At roughly 15 renewal/scheduling calls a day and 5–8 minutes each including no-answers and callbacks, that's 7–8 hours a week.

What to do. Move the membership plan into field-service software with built-in recurring-service tracking and automated renewal/reminder texts — Housecall Pro (Grow tier, ~$169–249/mo) or Jobber (Grow plan, ~$249/mo) both have this natively; ServiceTitan (Field Pro/Essentials, roughly $398+/mo per user, better once you're past ~10 techs) is the fit if you outgrow the smaller platforms. The system auto-texts customers at the due date and lets them self-schedule; office staff only work the exception list of no-responses.

• Cost: $170–400/month depending on platform and tier
• Setup: 2–4 weeks — importing the spreadsheet, matching customer records, configuring renewal cadence
• What the office has to change: someone (usually the office manager) owns the initial data import and has to resolve duplicate/incomplete customer records by hand — expect 4–6 hours of one-time cleanup
• Who handles a failure: if a renewal text bounces or a customer doesn't respond, it lands on the exception list the office reviews daily — same person who currently does renewal calls, just fewer of them
• Risk: low; the spreadsheet stays as a backup export for the first month

What happens now. Customers call in, office staff check tech availability by phone/text and assign jobs verbally, then call the customer back to confirm the window. With 6 techs and ~35–40 service calls/week, the back-and-forth (checking routes, re-confirming, handling same-day changes) runs 6–8 hours combined across both office staff.

What to do. A shared digital dispatch board with drag-and-drop scheduling and route awareness (Housecall Pro or Jobber both include this; ServiceTitan's dispatch board is the more advanced version) plus automated "tech on the way" texts to customers. This doesn't remove the dispatcher — it removes the phone tag of confirming and re-confirming, and gives techs their day on a phone app instead of a radio call.

• Cost: usually the same subscription as 3.1 (dispatch is a core feature, not an add-on)
• Setup: 1–2 weeks to get all 6 techs using the mobile app reliably
• What the office has to change: dispatcher has to actually use the board instead of falling back to phone calls under pressure — this is a habit change, not a tech problem, and is the most common reason these rollouts stall
• Who handles a failure: if the app is down or a tech can't get signal on-site, dispatcher reverts to phone/text for that job — same fallback as today, so nothing is worse-case
• Risk: medium; requires the whole team, including less tech-comfortable techs, to adopt a new daily habit

What happens now. Requesting a Google review is inconsistent — happens when a tech remembers to mention it, or office staff call a handful of customers a week and ask.

What to do. Automated review-request SMS triggered when a job is marked complete in the field-service app, with a direct link to the Google Business Profile (built into Housecall Pro/Jobber, or a dedicated tool like Podium or NiceJob, ~$150–300/mo standalone). Suppress the request automatically if the job notes flag a callback or complaint.

• Cost: included in 3.1's platform, or $150–300/month standalone
• Setup: under a week — one template, one trigger condition
• What the office has to change: techs must reliably mark jobs "complete" in the app (they should already be doing this for invoicing) — this is the dependency, not new work
• Who handles a failure: office manager spot-checks weekly that the trigger fired and reviews are coming in; a bad review still routes to the owner for a personal follow-up call, same as today
• Risk: low

• Quoting & follow-up on estimates (5 hrs/wk). Estimates for replacements/larger repairs are written up by hand and followed up by phone when a customer goes quiet. A templated digital quote tool with e-signature and automatic 3-day/7-day follow-up texts (built into Housecall Pro/Jobber, or standalone like Estimate Rocket) removes the manual chase — office staff only step in once a customer replies.
• After-hours call handling (3 hrs/wk). Emergency calls after hours currently roll to the owner's cell or go to voicemail and get called back in the morning, costing both missed jobs and owner interruptions. A live answering service for HVAC/plumbing (Smith.ai, Ruby Receptionists, or a trade-specific service like Apeiron) or an AI phone agent that captures job details and can send urgent ones straight to on-call tech's phone, cuts this without the owner fielding every 2am call. Requires publishing clear after-hours triage rules (what counts as urgent) for whoever answers.
• Utility-rebate paperwork (2 hrs/wk). Rebate forms for high-efficiency HVAC installs are filled out by hand and mailed/uploaded per utility. A templated intake (a form that captures the model numbers, install date and customer info at job close) feeding a rebate-tracking spreadsheet or a light workflow tool (Zapier/Make) cuts re-typing; the paperwork itself still has to be filed by a person since most utilities require signatures and don't have public APIs.
• PDF invoicing & payment collection (1 hr/wk). Invoices are generated and emailed as PDFs, then payment is chased by phone. Turning on the field-service platform's built-in online payment link (all three platforms above support this) lets customers pay by card/ACH from the invoice text — lowest hours here, but it's the easiest win once the platform from 3.1 is in place.

1. Week 1 — pick the field-service platform (Housecall Pro or Jobber, based on a side-by-side demo). Import the maintenance-plan spreadsheet and clean up duplicate customer records.
2. Week 2 — turn on dispatch board and "tech on the way" texts for all 6 techs; run it alongside phone dispatch for the first few days as a safety net.
3. Week 3 — enable automated maintenance-plan renewal texts and review-request triggers; office staff work only the exception lists.
4. Week 4 — measure: office hours spent on dispatch/renewal calls, review volume, and no-show/missed-appointment rate. Compare against the numbers in section 1, then decide on after-hours call handling as phase two.

• We don't know which field-service software, if any, is already in use — if you're on QuickBooks-only with no scheduling tool, the maintenance-plan and dispatch numbers above are close; if you already have partial tooling, some of this is already solved and the hours drop.
• We assumed the maintenance-plan spreadsheet is a single shared file with reasonably clean customer contact data — if it's several techs' personal notes reconciled manually, the one-time cleanup effort in 3.1 is larger than stated.
• We don't know current call volume or how many after-hours calls are genuine emergencies versus routine scheduling that could wait until morning — this changes whether an answering service or a simpler after-hours voicemail-to-text flow is the right fix.
• We assumed all 6 techs carry a smartphone capable of running a field-service app; if any don't, that's a one-time hardware cost not included above.
• We don't know your current close rate on estimates or average job size, so the dollar impact of faster quote follow-up (3.4) is directionally right but not precisely sized — confirm with your own numbers and we'll revise.
• Utility-rebate volume (how many rebate-eligible installs per month) wasn't visible from the website; if it's more than a handful a month, that line item is worth prioritizing higher than "Later."