A maintenance agreement is a paid promise to come back, usually two PM visits a year, sometimes quarterly, with a discount and priority attached. The money is collected once and the obligation runs the full term. An agreement system tracks each visit the customer is entitled to, marks it consumed when a tech completes it, flags unused visits before the term expires, and puts the renewal in front of someone ahead of the anniversary rather than after it.
Why maintenance agreements quietly stop earning
Nobody knows which visits are still owed
The agreement sold in March with two visits. One was run in April. Whether the fall visit happened is a question answered by scrolling job history and guessing. The office cannot tell you how many PM visits the company owes across the book.
Renewals depend on someone remembering an anniversary
There is no queue of agreements coming due. A renewal happens because a customer calls about something else and the CSR notices, or because the owner pulls a list in a slow week. The ones nobody notices lapse without a conversation.
A lapsed customer looks identical to a stranger
Once the term ends the record shows nothing. Someone who paid three years running and let one renewal slide gets the same non-member pricing and the same place in the queue as a first-time caller. Nothing distinguishes them, so nobody reaches out.
Deferred repairs found on a PM visit go nowhere
The tech notes a weak capacitor and a rusting drain pan on the tune-up ticket. The note stays on the ticket. Nobody builds a quote from it, nobody follows up, and the part fails in July as an emergency call at overtime rates.
Agreement states and what moves a customer between them
An agreement is not simply on or off. It moves through states, and each transition is either something the customer did, something a technician did, or a date passing. Building the state model first is what makes a renewal queue possible at all.
| State | What it means | What moves the customer in | What moves them out |
|---|---|---|---|
| Active, visits unused | Term current, no PM visit consumed | Agreement signed and first payment cleared | A tech completes a PM visit coded against the agreement |
| Active, partially consumed | At least one entitled visit used, one or more remaining | A completed PM visit is coded to the agreement rather than billed as a service call | The last entitled visit completes, or the term end date arrives |
| Active, fully consumed | Every entitled visit used, term still running | The final entitled visit is completed | The term end date arrives, or the customer buys additional visits |
| Renewal window | Inside sixty days of the term end date | The date, regardless of visits used | A renewal is accepted, or the term end date passes |
| Unused visit at risk | Term ends within forty-five days with a visit still outstanding | Date and consumption count evaluated together | The visit gets scheduled and run, or the term expires with it unused |
| Lapsed | Term ended, no renewal recorded | The term end date passes without a renewal | The customer renews, or the grace period ends |
| Win-back | Lapsed past the grace period, still an active service customer | The grace period ends, typically thirty days after the lapse | The customer re-enrolls, or is marked do-not-solicit |
How the agreement record is put together
The agreement is its own record, not a tag on the customer
It carries a start date, a term, an entitlement count, a price, a payment method, and covered equipment at one specific address. A customer with two properties holds two agreements. That separation is what makes the question of what you still owe answerable.
Visits are consumed, not merely completed
When a tech closes a PM visit, the ticket is coded against a specific entitlement on a specific agreement and the remaining count drops by one. A visit run outside the agreement stays a billable service call and never touches the count.
The renewal queue is generated by date, not by memory
Agreements entering the sixty-day window appear on a working list showing visits used, equipment covered, and the last tech on site. Whoever makes the call has the context in front of them instead of asking around for it.
Outstanding entitlements raise a flag before the term closes
Forty-five days out, an agreement with a visit still owed goes onto a scheduling list. Those calls get fed to the board as fillable work, which is realistically the only way they get run before the deadline.
Deferred repairs become a quote instead of a note
Findings on a tune-up ticket create a follow-up record carrying the equipment, the part, and a photo. It lands in a queue the office already works, so recommended repairs stop dying on the ticket they were written on.
Systems the agreement record touches
- CRM automation for renewal outreach — Renewal windows and win-back lists become sequences running against the customer record, not a quarterly spreadsheet.
- QuickBooks automation for recurring billing — Payments post against the agreement itself, so revenue and remaining obligation stay attached to one record.
- document automation for agreement paperwork — The signed agreement, its equipment list, and every renewal are stored as versioned documents with date ranges.
Is this a fit for your business?
A good fit when
- You hold more than fifty agreements and the number is still climbing
- Nobody can tell you how many PM visits the company still owes
- Renewals happen when someone thinks to look rather than on a schedule
- Tune-up findings are written on tickets and rarely turn into quoted work
Probably not a fit when
- Agreements are a handshake and you do not track entitlements at all
- You want one suite replacing dispatch, invoicing, and payroll in a single purchase
- You are looking for advice on how to price an agreement program
What to have ready
- Your agreement terms: what a customer gets, how many visits, at what price
- The current list of agreement holders and their start dates
- Which visits count as PM and which stay billable service calls
Questions we get asked
Can the system auto-renew agreements against a card on file?
Yes, and whether it should is a business decision more than a technical one. Auto-renew holds up when the authorization language is in the signed agreement and the customer got clear notice before the charge. We build the notice as a required step ahead of any charge, because a surprise charge costs more in the chargeback and the phone call than the renewal was worth.
What if a customer has agreements on two properties, or buys a home that has one?
Agreements attach to the address and the covered equipment, not only to a person. Two properties means two agreements with separate entitlements and equipment lists. Transfer on sale is supported if your terms allow it, and the record keeps both the original holder and the new one so service history stays intact.
We already track this in QuickBooks. Why is that not enough?
QuickBooks knows what you invoiced. It does not know what you still owe in visits, because an entitlement is not a line item and consumption is not a transaction. You generally keep QuickBooks for the money and add a record that tracks obligation and consumption alongside it, with the payment side posting back.
Does a lapsed customer get pushed into marketing automatically?
Only into a queue, and only after a grace period you set. Automatic outreach the day after a lapse tends to land badly, because a lapse is often a payment problem or a customer in the middle of moving. We build the grace period in and put a person on the first contact.
Related
- membership and service plan management
- service call scheduling and dispatch
- CRM automation for customer follow-up
- workflow automation for construction and field service companies
Tell us what the process looks like now and we will map what a system would need to do. No obligation, and you keep the map either way.