Maintenance agreements are the HVAC revenue nobody bills on time
A membership is supposed to run itself. Instead it runs on a renewal date someone was supposed to remember.
The short version
4 things that decide this
- 01A maintenance agreement is a scheduling obligation, a billing subscription and a renewal flow at once, and most shops track only one of the three well.
- 02Renewal dates that live in a spreadsheet or a manager's memory slip past their date before anyone notices, and the customer finds out only when the next visit gets a full price.
- 03A failed card on a recurring plan often just sits there. Nobody chases it until the member calls asking why they were skipped.
- 04None of this needs artificial intelligence to fix. It needs a schedule that runs the reminders, the seasonal booking and the payment retries on its own, and a monthly list of what fell through.
A membership is three jobs wearing one name
A maintenance agreement, a tune-up membership, a service plan: same idea under different names. A customer pays for two visits a year, priority scheduling and a discount on repairs. In exchange, the shop gets revenue that shows up whether or not the phone rings that week.
That revenue only shows up if three separate things happen on schedule. Visits get booked, spring and fall, before the season that needs them. The card on file gets charged, and charged again if it fails. And the renewal happens before the agreement quietly expires. Most shops run one of those three well. Fewer run all three.
The gap is easy to miss because nothing breaks loudly. A membership does not cancel itself with a phone call. It just stops renewing. The shop finds out a year later, when the same customer calls in as a one-off job.
Four ways an agreement lapses without anyone deciding it should
Renewal dates live in someone's head, or in a spreadsheet that gets opened once a quarter if it gets opened at all. A one-year agreement signed in March renews in March. If the office manager is buried the week it comes due, the customer rolls off the plan and nobody sends the renewal invoice. Nobody chased them, so they assume they cancelled it and never call to ask.
Spring and fall tune-ups get sold but never scheduled. A member paid for two visits this year. Dispatch fills with no-cool calls in July and no-heat calls in January. A scheduled tune-up loses to a same-day emergency every time. The visit gets pushed, then pushed again, until the year ends with one delivered instead of two.
A card on file fails and nobody chases it. Cards expire, get replaced after fraud, or hit a limit. A failed charge on a recurring plan usually just sits in the payment processor's dashboard, unseen. The member's coverage lapses over a payment problem nobody told them about.
A member calls in and nobody flags them as one. The CSR taking the call has no easy way to see that the caller is a plan holder entitled to priority scheduling and a discount. That member gets booked and billed like anyone off the street, and the thing they paid for never shows up on the call.
What automation actually does about each one
None of this needs intelligence. It needs a schedule that runs without a human remembering to check it. Renewal reminders go out on a fixed calendar, tied to each agreement's actual signing date. Not to whenever someone gets around to reviewing the list. A reminder at 30 days, another at 7, then the renewal charge itself. All on autopilot.
Seasonal tune-up runs get booked against real technician capacity, ahead of the season, instead of waiting for a slow week that never comes. The system holds a block of spring and fall slots for members before the emergency calls fill the board. That way, the visit a customer already paid for competes on the calendar before the rush starts, not during it.
A failed card triggers a retry sequence and a text to the member, not silence. Card declined, retry in two days, a short text asking them to update payment through a link. Three attempts over a couple of weeks catch most cases. The plan lapses for a payment glitch, not because the customer wanted out.
Member status shows up the moment someone calls in. Whoever answers, human or AI receptionist, sees the plan, the visits owed and the discount before the call ends. Priority scheduling becomes something that actually happens, not a line in the sales pitch.
The office manager gets a monthly list too. Agreements that renewed late. Visits still owed with fewer than sixty days left in the year. Payments that failed and were never resolved. One page, reviewed once a month, instead of a problem nobody sees until a customer complains.
- 01Renewal reminders tied to each agreement's own date, not a manual review cycle.
- 02Seasonal visits booked against technician capacity ahead of peak demand.
- 03Failed payments retried automatically with a text asking the member to update the card.
- 04Member status visible at intake, so priority scheduling and the discount actually apply.
- 05A monthly unbilled-agreements list, so the gap gets caught before the customer does.
This lives inside the system you already dispatch from
A shop running ServiceTitan already has memberships as a native object: visits owed, renewal date, plan tier. The gap is usually not the data model. Nothing acts on the data without a human opening the report. A fix reads the membership record on a schedule and triggers the reminder, the booking hold, or the retry. Then it writes the result back to the same record.
Housecall Pro has Service Plans; Jobber uses recurring jobs as the stand-in. A recurring job series stands in for the agreement. The same reminder and retry logic runs against it. Payment failures and renewal invoices post through to QuickBooks either way. The office manager's list and the accounting record agree, instead of needing to be reconciled by hand.
- Agreement signedRenewal date and visit count get set once, on paper or in the FSM.
- Renewal date arrivesNo reminder fires unless someone checks the calendar.
- Tune-up season opensEmergency calls outbid the scheduled visit for the same slot.
- Card charge runsA decline sits in the payment dashboard, unseen.
- Member calls inThe CSR has no flag showing plan status or visits owed.
Every stage above can fail silently. None of them needs a person to fail; they only need a person to have been the plan.
Some of the systems we have shipped
What HVAC owners ask about membership billing
01How do I find out how many maintenance agreements have already lapsed?+
Pull your renewal dates out of ServiceTitan, Housecall Pro, Jobber or whatever you run and compare them against actual charge history. Shops that run this comparison for the first time usually find more lapsed agreements than expected. That list is the starting point, not any new software.
02Does this replace the office manager who currently tracks memberships?+
No. It removes the part of the job that depends on remembering a date. It leaves the part that depends on judgment: talking a customer back onto a plan, or deciding when a discount makes sense. The office manager reviews a short list instead of building one from scratch every month.
03What happens when a tune-up visit can't be scheduled because the shop is slammed with emergencies?+
The visit stays owed and rolls into the next available window rather than disappearing. Booking against real technician capacity ahead of the season is what keeps that window from running out entirely before the year ends.
04Can this work with a paper-and-spreadsheet shop that isn't on ServiceTitan yet?+
Less cleanly. The reminders and retries still work off a spreadsheet. But the write-back that keeps the office manager's list accurate needs a system of record with an actual membership or recurring-job object. A shop still on paper gets more value from moving that record first.
05Is a failed card retry going to annoy members who just forgot to update a card?+
A short text with a link to update payment is less friction than a phone call telling them their coverage lapsed. Three attempts over roughly two weeks catches most expired-card cases without the awkward call either side would rather avoid.
Related
- HVAC software development →Maintenance-agreement billing as one part of a wider dispatch and compliance build.
- What an HVAC company loses after hours →The same pattern, on the phone line instead of the billing calendar.
- Is an AI receptionist worth it for an HVAC company? →Where the intake layer that flags members at the point of contact fits in.
