A 30-day HVAC missed-call reduction playbook

A missed-call project should begin with the path a call takes through your shop, not with a software promise. The useful question is whether every request reaches an approved outcome: answered, qualified, booked, escalated, or intentionally declined. A 30-day rollout lets you inspect that path without moving every call at once.

Quick answer: Spend four weeks measuring your current call path, opening controlled overflow and after-hours coverage, verifying every field-service write and approved message, then comparing the results with your own baseline. Expand only the call paths that follow shop policy; keep ambiguous, safety-related, and exception decisions with a named person.

We build Patchment, an AI front office for field-service businesses. That is an explicit first-party interest, not evidence that a particular result will occur. This playbook uses records you can inspect yourself.

Start with the operating question

This guide does not repeat the seasonal-volume and cost analysis in why HVAC companies miss winter calls. Treat that article as the diagnosis. This one is an implementation sequence for an owner or operations lead who wants to test a different call path while retaining control of dispatch decisions.

Choose one accountable rollout owner before day one. They own the rules, daily exception review, and decision to pause coverage. Write down the current routes: main line, tracking numbers, forwarded numbers, overflow queue, and after-hours line. If a route cannot be tied to a call log, leave it outside the test or fix the logging first.

Keep the first scope narrow. Routine requests, existing-customer scheduling, and defined after-hours intake are observable. Complaints, disputed prices, safety concerns, and unclear requests should retain a named human owner.

Define shop-owned metrics before changing coverage

Use only the shop's own call logs, routing records, field-service records, escalation receipts, and review notes as metric inputs. These shop-owned metrics are not an industry comparison. Their job is to show what happened before and during the rollout under your actual staffing, service area, and rules.

Track the same six measures every week, keeping answered and qualified requests as separate raw counts:

1. Inbound calls by route and time window. The denominator is every inbound call attempt visible in the selected phone routes. Break the count into business hours, overflow periods, and after-hours periods so a change in call mix is not mistaken for a coverage change.
2. Answer coverage. Answer coverage = answered attempts / inbound attempts for the same route and time window. Keep the numerator and denominator as raw counts. A caller who hangs up before qualification can still be an answered attempt, while spam and wrong numbers remain visible outcome rows.
3. Intake completeness. Intake completeness = qualified requests / answered calls. A qualified request contains the minimum intake your shop requires, such as caller identity, callback number, service address, equipment or problem summary, and requested timing. Unsupported service-area requests remain separate outcomes rather than silently disappearing.
4. Verified field-service bookings. Count a booking only after someone confirms the customer, address, request details, and appointment or follow-up state inside the field-service management system. Qualified requests eligible for booking are the denominator; voicemail messages and unverified notes are not bookings.
5. Escalation delivery. Count each call that triggers an emergency, safety, complaint, or policy escalation, then confirm whether the designated person received the context through the approved channel. Calls requiring escalation are the denominator. Delivery is distinct from how quickly the person decides what to do.
6. Exceptions and review outcomes. Log ambiguous requests, failed writes, duplicate customers, missing consent, unreachable escalation owners, and caller corrections. The denominator is all calls handled in the trial routes. Record the review outcome: rule changed, record corrected, person followed up, call path paused, or no change required.

Keep the numerator and denominator visible. A booking count can rise because more calls arrived, so retain the counts beside each ratio and annotate route, schedule, staffing, and weather changes. Do not turn a short trial into a forecast.

Week 1: measure the current path and establish a baseline

For the first week, do not expand automation. Map where each selected number rings, what happens when nobody answers, who checks voicemail, and how a request becomes a customer or job record. Review the six measures at the same time each day. If two systems disagree, preserve both records and identify which one the shop treats as authoritative.

Review examples from each route and time window using the same outcome labels the team will use later. The goal is to establish the week 1 baseline and expose gaps in routing, logging, or definitions.

End the week with a one-page call policy. It should state the required intake fields, services and areas the shop accepts, times that may be offered, requests that cannot be booked, emergency conditions, and the person who owns each exception. If the team cannot agree on a rule, keep that decision human.

Week 2: open overflow and after-hours coverage

Start with overflow and after-hours routes rather than moving the primary daytime line all at once. Define the handoff threshold for overflow, the exact coverage window, and what the caller should hear when a human decision is pending. Avoid telling callers that an appointment or technician response is confirmed until the corresponding shop record supports it.

Write explicit emergency-versus-maintenance rules. The HVAC call triage guide can help the team discuss categories, but your shop must set its own service area, weather context, on-call policy, and safety escalation language. For a reported gas odor or carbon-monoxide alarm, the caller should leave the building and contact the gas utility or 911 or local emergency services first, without waiting for Patchment or the shop. Then hand the call context to a human according to shop policy; do not diagnose or declare the situation safe. Electrical hazards, active flooding, and other unclear safety reports should also leave the routine booking path for the applicable public-safety instruction and human shop handoff.

Review escalation delivery daily. A delivered alert is not an accepted job, so retain both outcomes. If alerts reach an unavailable person or lack context, pause the rule, correct it, and retest.

Week 3: verify Jobber and Housecall Pro writes and consent-aware messages

Patchment supports native integrations with Jobber and Housecall Pro. Run supervised calls covering a new customer, an existing customer, a routine request, a duplicate address, a full schedule, an unsupported request, and an escalation. After each call, perform write verification in the field-service system: check the matched customer, service address, request summary, schedule state, source, and internal notes. The team should see the same usable record the caller was told to expect.

Patchment does not currently support a native ServiceTitan integration. Patchment supports native integrations with Jobber and Housecall Pro. This is a product-fit correction, not a recommendation to rank or replace field-service systems. A ServiceTitan shop should not treat a message relay or custom workaround as equivalent to a native integration.

Test consent-aware status messages separately from booking writes. A caller providing a mobile number does not, by itself, authorize every future text purpose. Document the approved message purpose, the source and time of consent, sender identity, what message frequency the customer was told to expect, and how help and opt-out requests are handled. The field-service SMS consent guide provides the fuller policy checklist.

Use test or appropriately consented contacts, then inspect the message and delivery record. A field-service write and a status message are separate events requiring separate review evidence.

Week 4: review exceptions, compare with the baseline, and choose ownership

In week 4, keep the coverage window stable long enough to compare it with the week 1 baseline. Compare answer coverage and intake completeness using identical routes, time windows, and denominators in week 1 and week 4. Then read the exceptions rather than looking only at totals. A clean aggregate can conceal a repeated duplicate-customer issue, an escalation that reaches the wrong phone, or a message sent without the evidence your policy requires.

Group exceptions by cause: missing rule, incorrect rule, failed integration write, caller ambiguity, unavailable human owner, consent gap, or staff correction. For each group, decide what to expand and what to keep human. Expand a path only when its intake, booking, escalation, and message outcomes are observable and consistently follow the written policy. Keep it human when judgment is central, ownership is unclear, or the cost of a wrong routine action is unacceptable.

Document the day-30 decision: routes and hours retained, routes paused, rules revised, human-owned exceptions, and the next review date. Broader coverage, the same scope, or a rollback can each follow the shop's evidence. Patchment does not publish a public list price; use a current written quote rather than an invented tier or allowance.

Next step

If you want to walk through this four-week plan against your current phone routes and FSM, book a Patchment demo.