How Service Agreement Management Works
Maintenance agreements are the most predictable revenue an HVAC business has, and the easiest to lose track of. A shop with 600 agreements and no automation is leaking renewals it will never notice.
Software has to do three separate things with an agreement: generate the visits, chase the renewal, and collect the money. Most platforms do the first well and the second two poorly.
The renewal is where the value sits. An agreement that lapses quietly takes with it not just the plan fee but the replacement conversation it would have produced in five years.
What an agreement actually is
Two things bundled, and they behave differently in software.
A commercial contract. The customer pays a fee for a defined set of services over a defined period, usually with additional benefits — priority scheduling, a discount on repairs, waived diagnostic fees.
A scheduling obligation. You owe them a specific number of visits within specific windows, and those visits have to appear on someone’s board without anyone remembering to put them there.
Shops that treat an agreement as only the first thing end up with a list of customers who have paid for visits nobody scheduled. That is the most expensive version of this problem, because it converts predictable revenue into a service failure.
The lifecycle, and where it leaks
How visit generation works
When an agreement is created, the system reads its terms and produces the scheduled work automatically. The terms it needs:
- Visits per period — usually two a year for a heating and cooling system
- Seasonal windows — a cooling tune-up belongs in spring, not August
- Equipment covered — which units at which addresses, since a property may have several
- Duration per visit type — often different for heating and cooling checks
- Anniversary or fixed calendar — does the year run from the sale date or from January
Well configured, the system creates unscheduled work orders inside the correct seasonal window, and they appear in your dispatch queue as capacity becomes available. Which means agreement visits should be filling the shoulder seasons rather than competing with emergency work — and that is exactly how they should feed capacity planning.
Generate agreement visits as unscheduled work in a window, not as fixed appointments on specific dates.
Fixed dates create hundreds of appointments you then have to move as reality intervenes. A window lets the system place them where capacity actually exists, which is the whole point of having them be flexible work.
The renewal is the whole game
Visit generation is a solved problem in most platforms. Renewal is not, and it is where the money is.
An agreement that lapses costs you three things:
The fee. Obvious and the smallest of the three.
The service relationship. Twice-yearly contact is what keeps you the default contractor for that address. Without it, the next failure becomes a search rather than a phone call.
The replacement conversation. This is the expensive one. A technician who sees the same system every six months knows when it is nearing end of life and has the standing to say so. Nobody has that conversation with a customer they have not seen in three years.
What a system needs to do about renewals:
| When | What should happen |
|---|---|
| 60 days before expiry | Flag internally; the office sees it on a list |
| 45 days before | Notice to the customer with the renewal price |
| 21 days before | Second notice, with the year’s service history attached |
| 7 days before | Phone call, not an email |
| On expiry | Status changes automatically. Priority routing and discounts stop |
| 30 days after | Win-back attempt, then move to a nurture list |
The 21-day step is the one to build carefully. Attaching what you actually did that year — two visits, the filter changes, the capacitor you caught before it failed — converts the renewal from a charge into a demonstrated value. It is the single most effective renewal message available and almost nobody sends it.
Billing models
| Model | Cash flow | Renewal risk | Admin |
|---|---|---|---|
| Annual, paid upfront | Best — money in advance | High — a single decision point each year | Low |
| Monthly recurring | Even, predictable | Low — continues until cancelled | Needs stored payment and card updating |
| Per visit | Weakest | Very high — renegotiated every time | Highest |
The trade-off is worth thinking about properly. Annual upfront is better for cash flow; monthly recurring is better for retention, because it converts an annual decision into a passive continuation and most people do not cancel things.
Monthly recurring depends on two things working: stored payment credentials and automatic card updating when a card expires or is reissued. Without the second, you will lose agreements to expired cards rather than to unhappy customers. Worth checking against the fee structure covered in payment processing fees, since recurring card billing on hundreds of agreements adds up.
Converting non-holders
Most shops have far more customers without an agreement than with one, and that gap is the cheapest growth available.
Three moments convert best:
Immediately after a repair. The customer has just experienced what a breakdown costs. This is the highest-conversion moment there is, and it requires the technician to be able to sell and enrol on the spot.
At installation. A new system with a first-year plan included is standard practice and produces a customer who is already in the habit when the first renewal arrives.
Ahead of peak season. A pre-season tune-up offer with the plan as the better-value option, sent to customers with systems over eight years old.
That last one requires knowing which addresses have older equipment — which is a property-record capability rather than a customer-record one, and one of the reasons the distinction between the two matters.
What breaks agreement management
Terms stored in notes. If the number of visits and the seasonal window live in free text, nothing can be generated automatically. Structured fields or no automation.
Renewals with no owner. A flag on a list that nobody is responsible for checking is not a process. One named person, one weekly review.
Peak-season cannibalisation. Agreement visits get pushed aside for emergency work in July, then never rescheduled. By the time anyone notices, the customer paid for two visits and got one.
Expired payment credentials. On monthly billing, a silent failure rate builds up that looks like churn and is actually plumbing.
No visible value. A customer who cannot see what they got will treat renewal as a subscription to cancel. This is why the service-history-attached renewal notice matters so much.
Frequently asked questions
How should agreement visits appear on the schedule?
Is monthly or annual agreement billing better?
When should renewal reminders start?
Why does a lapsed agreement cost more than the fee?
When is the best moment to sell an agreement?
Why do agreement visits get missed during busy seasons?
What to do next
- Audit for undelivered visits. How many active agreements have had fewer visits this year than they paid for? That number is usually a surprise.
- Check whether agreement terms are in structured fields or in notes. Automation is impossible if they are in notes.
- Name one person to own renewals with a weekly review of the 60-day list.
- Build the 21-day renewal notice with service history attached. It is the highest-return message in the whole sequence.
- Capacity planning for HVAC businesses — protecting slots for agreement visits
- Payment processing fees — the cost of recurring card billing
- How HVAC scheduling software works — how generated visits reach the board
This guide describes agreement management practices documented across vendor materials and industry sources. Terms, visit counts and billing structures vary widely between businesses, and platform capabilities differ — confirm what any specific system automates before relying on it.