Service Agreement Renewal, Fulfilment & Reactivation
A continuous system that renews agreements before they lapse, actually delivers the visits they promise, recovers failed payments, and brings dormant customers back with a reason rather than a discount.
- Tier
- Flagship
- Build order
- 6th of 7 for HVAC
- Shape of it
- 9 steps, 1 stop rule
- At launch
- Built against your stages, then proven before it runs alone
The problem this solves
Agreements rarely get cancelled. They expire, for a handful of separate reasons that each need a different fix:
No renewal reminder went out.
The card on file declined and nobody worked the failed-payment queue.
The agreement renewed but the maintenance visit was never booked, so the customer paid for a year and felt nothing.
The customer moved or changed their number and the record was never cleaned.
A repair customer was never offered membership after the repair.
An install customer was never enrolled at commissioning.
The agreement exists in the field service platform but not in accounting, or the other way round.
The customer called after expiry and was treated as brand new, which is how a ten-year relationship ends.
And beneath all of it: a member who has not had a visit has no reason to renew, so fulfilment and renewal are the same problem.
How it works, step by step
Every wait, threshold and branch below is a value we set with you during the build, against your stages and your language. None of it is a default we impose.
- What starts it
- A stop rule, so nothing closes itself
Step 1Trigger
Every agreement carries a status that distinguishes active, due, expired, cancelled, failed payment, and renewed but unfulfilled. That last one is the category most shops cannot see.
Step 2
Renewal contact begins sixty to ninety days before expiry, and it leads with what the customer got this year, not with the price.
Step 3
A second contact goes at thirty days, and it is a call for anyone whose visit was not completed, because that conversation cannot be automated honestly.
Step 4
A failed payment triggers immediately, to a person, with the specific card problem named. This queue is worked daily or it is not worked.
Step 5
The next maintenance visit is booked before the current one closes, while the technician is still standing in the house. A visit that is scheduled is a renewal that is largely decided.
Step 6
Seasonal maintenance is scheduled off the equipment and the agreement rather than off a campaign, so it lands when the work is right rather than when marketing is quiet.
Step 7
Dormant customers are reactivated with a reason: equipment age, a deferred repair recorded on a previous visit, an expired warranty, or a system that has now passed the interval where a tune-up is defensible. Not a discount with no argument attached.
Step 8Stop rule
Anyone who has been offered and declined twice is rested, not pursued.
Step 9
Review requests go only to customers whose job actually closed well, and only after the work is complete.
How it gets built
Built inside what you already run
- ServiceTitan
- Housecall Pro
- Jobber
- FieldEdge
- or whatever your office already runs on
Nothing to log into and nothing to license. If a system needs a record your platform does not hold, we add the field to your platform rather than starting a second one beside it.
This is the actual build order, in the phases its own steps fall into. It runs in supervised mode first, with you approving what goes out, until you are happy with the tone.
- 1
Build
Reconcile the agreement list between the field service platform and accounting before anything else. The two will not match, and the difference is the first month of value.
Built inside the software you already run, against your stages and your language.
- 2
Build
Build the status model, including renewed but unfulfilled.
- 3
Agree
Write the renewal content around what the customer received, and get the owner to approve the version that goes to a member who did not get a visit.
The thresholds, the wording and the names are yours. We write them down with you and get the consequential ones signed off.
- 4
Build
Build the failed-payment queue and assign it to a named person with a daily review.
- 5
Build
Make booking the next visit a required step at the close of the current one.
- 6
Build
Build the reactivation reasons from the equipment and visit history, and agree the ones the owner considers honest.
- 7
Agree
Set the rest rule after two declines.
- 8
Build
Connect review requests to job outcome, and exclude any job with an open complaint or a callback.
What changes after it goes live
How it runs today
Agreements rarely get cancelled. They expire, for a handful of separate reasons that each need a different fix:
After this one is live
Renewal stops being a season and becomes a rolling process. The failed-payment queue stops being invisible. Members feel the agreement because the visit happens. And the dormant list stops being a place customers go to be forgotten, which matters because a customer with a twelve-year-old system is the most qualified replacement prospect the business owns.
How to measure whether it worked
Your arithmeticRun with your numbers, not ours
Three numbers, all of which the business already has: the renewal rate, the share of active agreements whose visit was not completed this period, and the value of failed payments never recovered. The second one is usually the largest and is almost never measured.
We agree the baseline before anything is built, and we do not take credit for things that were going to happen anyway. There is no figure on this page claiming what we have produced for somebody else, because there is no verified figure to publish.
What we will not do
This is from the same delivery document as everything above it. It is on the page because a supplier who has not thought about it will not tell you, and you would find out later.
Every system here sends automated messages to consumers in the United States, which puts all of them inside the TCPA and inside carrier A2P 10DLC registration. These are two different things and both apply. Registration is a carrier trust requirement; it does not create consent and does not make an unlawful message lawful. Unregistered application traffic gets filtered or blocked.
Classify every system before it sends. A service message is narrowly connected to an existing job: appointment confirmation, technician on the way, part arrived, invoice. A marketing message promotes something: a tune-up offer, a replacement promotion, a membership push, an estimate reactivation sequence. The standards of consent are different, and a promotional line inside a service template converts the whole message into marketing.
The minimum a compliant build has to do:
- Consent recorded per number with the date, the source, the exact wording shown, the sending brand, and whether it covers service, marketing, or both. Marketing needs prior express written consent with an unchecked opt-in, and consent cannot be a condition of purchase.
- A2P 10DLC registration of the brand, the numbers, and a campaign use case that matches the traffic actually sent. An appointment-reminder campaign does not quietly become a seasonal promotion campaign.
- Quiet hours of 8am to 9pm in the recipient's local time, not the office's, with queued sends held until the window opens. Apply the same gate to service messages by default and handle genuine emergencies as a named exception.
- Opt-out handling for STOP, UNSUBSCRIBE, CANCEL, END, QUIT, REVOKE and OPT OUT, and for free text like "stop texting me". Suppress immediately in practice rather than to the outer limit of the rule, cancel messages already queued rather than only future ones, and propagate the suppression to every sending number, system and platform the contractor controls.
- Replies routed to a monitored human queue, always. A reply that says the heat is off is not a marketing response.
- Human review before any sequence that would materially pressure a prospect, which in this playbook means System 4.
- Suppression reconciled across systems, so a customer cannot opt out in the field service platform and keep receiving messages from the marketing tool.
- Purchased or scraped lists are not messaged. Consent has to name the actual sender.
Nothing in this document is legal advice. State mini-TCPA statutes, carrier policy, and the exact dialling or sending technology can each add requirements, and the rules in this area have moved more than once recently. Every template that states a commercial term, a price, or a guarantee requires review by the contractor's own counsel before it goes live.
Nothing here is legal advice. Rules in this area have moved more than once recently, and every template that states a commercial term or a guarantee goes to your own counsel before it goes live.
Seven systems forHVAC.
We build one at a time and prove it moved before starting the next. The tiers are the dependency order, not a price list.
Tier 1Foundational
Nothing arrives late or unowned. These come first because everything above them assumes they are true.
- 1Multi-Channel Capture, Triage & Instant ResponseFastest visible result, and it is the one that survives the first heat wave, which is when the owner decides whether any of this was real.
- 2Dispatch Confirmation, Arrival Protection & Technician BriefProtects the capacity and the truck rolls already paid for.
Tier 2Growth
The recoverable money. These work the pools the foundational systems have made visible for the first time.
Tier 3Flagship
One connected system end to end, plus what the owner reads on a Monday. Only once the pieces are proven individually.
- 5The Complete Service-to-Install SystemThe flagship, once the pieces are proven individually.
- 6Service Agreement Renewal, Fulfilment & Reactivationyou are hereCompounds everything above, and depends on the equipment data System 2 started collecting.
- 7The Owner's Morning BriefOnly meaningful once there are systems to report on.
The tiers are the dependency order for HVAC, not a price list. Most firms do not start at the first one, because the order is a default and the call is where it gets changed.
A note on sequencing this trade
Do not build all seven at once.
Each stage is proven against its agreed measure before the next begins.
Season note. Build Tier 1 in the shoulder season and let it run through one peak before starting Tier 2. A contractor who sees System 1 hold on the first hot Saturday will build the rest without being sold again.
Back to the HVAC overview for the stage map and where these fit.
Is this the oneyou need first?
Often it is not. On the call we look at what is actually costing you most right now, which is frequently a different system from the one that brought you to this page. If there is nothing worth building yet, we will say so.