How to Automate Service Reminders and Maintenance Schedules for a Garage, HVAC or Equipment Servicing Business

A garage, an HVAC firm or an equipment servicing business has a customer list that is really an asset list. Every unit you have ever worked on has a next service date attached to it, and almost none of those dates sit anywhere a person can see.

So the work comes back as emergencies. A boiler fails in November, a fleet van arrives with a warning light, a compressor that should have had a filter in March seizes in July. All three were predictable, and none of them were on a list.

This guide builds an asset register with due dates, and an automation that contacts the customer before the date rather than after the failure. Budget about half a day, plus an evening of typing in what you already know.

What you are building

One register with a row per unit rather than per customer, a rule that sets the next due date whenever a job is completed, and a reminder sequence that starts a few weeks before it. Plus a monthly list of everything due in the next sixty days, which is the part you will use to fill a quiet week.

Tools: your job management, invoicing or workshop software, a spreadsheet if it will not hold the fields you need, an automation tool such as Zapier, Make or n8n, an AI assistant such as ChatGPT or Claude, and email or SMS.

Step 1: build the register, one row per unit

The mistake is organising this around customers. A landlord with nine boilers, a company with four vans and a factory with eleven machines need nine, four and eleven rows, because each unit has its own date.

• ·The customer, and the site if it is not their billing address.
• ·What the unit is: make, model, serial number or registration, and where on site it lives.
• ·When it was last serviced, by whom, and what was done.
• ·The interval, in months or hours or miles, whichever the manufacturer or the contract actually uses.
• ·The next due date, worked out from the last service and the interval.
• ·Anything fixed about access: keys, a site contact, an induction, a shutdown window.
• ·The warranty or contract end date, if there is one.

Fill it from your invoice history rather than from memory. Two evenings of typing gives you a register covering everything you have touched in the last two years, which is a far better prospect list than anything you could buy.

Step 2: set the next date the moment a job is finished

A register only stays true if it is updated at the point of work rather than in a catch-up session that never happens. When an engineer marks a job complete, the automation should write the date it was done, the work carried out, and the next due date calculated from the interval on that row.

For units measured in hours or miles rather than months, capture the reading on the job and let the automation estimate the next date from the usage you already know, then mark it as an estimate. An estimated date that is roughly right produces a phone call at roughly the right time, which is the whole point.

Step 3: the reminder sequence

Three touches, spaced by how long your customers usually take to arrange access.

1. 1Four weeks before due. What the unit is, when you last attended, what is due and roughly how long it takes. Offer two specific weeks rather than asking them to suggest a time.
2. 2One week before due. Shorter, with a booking link and the access details you hold, so they can correct anything that has changed.
3. 3Two weeks after the due date, if nothing has been booked. Plain and factual: the service is now overdue, here is what usually happens next, here are two dates.

Keep the instruction about not describing what might fail, even though the temptation is obvious. A reminder that reads as a warning about an expensive breakdown gets read as a sales tactic, and the customers who resent it are usually the ones with the most units.

Step 4: wire it up

1. 1Run once a day. Read the register and find every row whose due date falls inside one of the three windows.
2. 2Check a status column first. Anything already booked, quoted or marked do not contact gets skipped.
3. 3Fill the right template with the fields from the row and send it from the address or number the customer knows you by.
4. 4Write a timestamp back against the row for that touch, so nobody gets the same reminder twice.
5. 5When a booking is made, set the status and clear the remaining touches for that unit.
6. 6When the job is completed, write the new last service date and the new due date, which puts the unit straight back into the cycle.

That last step is what turns this from a one-off campaign into something that runs for years. Every completed job reschedules itself, and a unit you serviced in March quietly reappears in your diary two winters later.

Step 5: the sixty day list

The reminders handle the customer. The list handles your diary.

The line about sites with several units due together is the one that pays for the build. Four boilers in one building attended on a single visit is a different job to four visits, and you can only see it if the register is organised by unit.

What changes

Work stops arriving as a surprise. The quiet fortnight in February gets filled from a list you generated in December, customers hear from you before something fails rather than after, and the unit you serviced two years ago and forgot about is back in the diary.

Connecting your job records, a register and a reminder sequence so the whole cycle runs without anybody remembering is the kind of build in Workflow 05: Build Automation Workflows, the AutomateFirst module about connecting the tools you already pay for so repetitive work runs in the background. This guide is one complete build from it, free. The playbook has seven workflows for one payment of $297, with a 30 day refund.