How to Build a Preventive Maintenance Automation Workflow

Walk into any well-run HVAC shop, plumbing company, or fleet maintenance operation and ask the owner what one thing they wish they had more of, and the answer is almost always the same: more preventive maintenance contracts. Not more leads. Not more trucks. More PM contracts.

The reason is math. A one-time service call generates one invoice and ends. A preventive maintenance contract generates 2-4 scheduled visits per year for as long as the customer renews — often 5 to 10 years — plus first-right-of-refusal on every emergency repair that happens between visits. In the field service businesses I have worked with, PM customers have roughly 3x the lifetime value of break-fix-only customers, and their gross margin on emergency repair work is higher because they are not bidding against three other shops.

The blocker is operational. Running PM at scale means tracking which customer is due for which service in which week, dispatching the right technician with the right checklist, sending the right reminder before the visit so the customer is home, completing the work, getting the invoice out same-day, and then scheduling the next visit a year in advance. Do that by hand for 50 customers and you spend a Saturday a month on it. Do it for 500 customers and you cannot.

This is exactly the kind of workflow that automation eats for breakfast. Here is the build, end to end, using Deelo's apps. The same architecture works for HVAC, plumbing, fleet maintenance, commercial cleaning, generator service, fire safety inspection, refrigeration, and any other recurring-service field business.

Open Deelo CRM and create a Contract record type if you do not already have one. Each PM contract has the following fields, and they all matter — the automation downstream reads every one.

Every field here is a knob the automation will turn later. The richer the contract record, the less manual work downstream.

Once a contract is signed, the next 12 months of jobs should appear in the dispatch schedule automatically. Open Deelo Automation and build the contract-onboarding workflow.

The trigger is the Contract record's status changing to "Active." The first action node loops through the equipment list and the service cadence to generate the visit schedule. A semi-annual contract with two pieces of equipment on different schedules might produce 4-6 scheduled visits across the year. Each scheduled visit becomes a Booking record in Deelo Bookings with these properties: customer, equipment, service template, target week (not a specific day yet — that gets confirmed closer to the visit), assigned territory or technician if specified, and the contract reference.

The scheduling logic should respect a few rules. Group visits geographically when possible — if the customer has two pieces of equipment on the same address, schedule them on the same visit. Stagger contracts across the calendar so you do not get a glut of jobs in week 26 just because every PM was sold in week 1. Build a Conditional node that checks the technician's existing schedule density and shifts the target week by one if it is already over capacity.

Two weeks before each scheduled PM visit, the workflow needs to lock in a specific day and time. Build a second workflow in Automation triggered by a Schedule node that runs daily and looks for any Booking whose target week is 14 days out and whose specific date is still null.

For each matching booking, send the customer an SMS and email via Deelo Marketing and Deelo SMS. The message offers two or three available time slots within the target week, with one-click confirmation. When the customer picks a slot, the Booking record updates with the confirmed date/time, and the workflow auto-assigns the technician based on territory, skills, and the customer's preferred-technician field.

For customers who do not respond within 48 hours, the workflow assigns the most likely time slot and sends a confirmation message stating the assigned slot with a one-click reschedule link. Do not let unscheduled bookings sit indefinitely — they end up missed, and missed PM visits are the leading cause of contract cancellation.

One week before the visit, the customer gets a reminder. The reminder workflow is simple — a Schedule node that runs daily, finds bookings 7 days out with confirmed dates, and dispatches the reminder via the channels in the contract's preferences.

SMS is the default channel for field service reminders. The response rate and the show-up rate are both higher than email. The message should include: the specific date and time window, the technician's name (so a stranger does not show up at the door), the equipment being serviced, what the customer needs to do to prepare (clear access, secure pets, be home or leave instructions), and a one-click reschedule link in case something has come up.

For customers on email-only preference, send the same content as an email. For high-value commercial customers, send both, plus a calendar invite the customer can drop into their team's shared calendar.

Morning of the visit, the dispatcher (or the dispatch automation) confirms the technician's route in Deelo Field Service. The technician opens the booking on their mobile device and sees the service template — the checklist for the visit, with every step pre-loaded from the contract. For an HVAC spring tune-up, that might be 20-30 items covering refrigerant levels, electrical connections, condensate drain, filter, blower motor, thermostat calibration, and so on. Each item gets a pass/fail/note as the technician works through it.

When the technician taps "On my way" in the mobile app, the Field Service app fires an event that the Automation engine picks up. The workflow sends an SMS to the customer: "[Technician name] is on the way and will arrive in roughly 20 minutes. Truck description: white Ford Transit, license plate ABC-1234." This is the single piece of automation customers thank you for the most in service businesses. It eliminates the "is anyone actually coming" anxiety that drives so many cancellation calls.

When the technician finishes the visit and taps "Complete" in Field Service, the workflow fires the closing automation. This is where the recurring-revenue magic actually happens — every cycle ends with the next cycle already scheduled and billed.

The technician taps one button, and seven things happen across four apps. The office did no manual work. The customer received a completed report, a paid invoice, and a confirmed future appointment within minutes of the visit ending.

PM is a long game. The leading indicators that tell you whether your program is healthy are not revenue — revenue lags by 6-12 months. Watch these instead, weekly.

Build this dashboard in Deelo's reporting and put it on a TV in the shop. PM is the metric the whole company should see every day, because every contract you add today pays out for the next decade.

If you do not have a single PM contract today, start with the easiest sell: offer every break-fix customer who paid an invoice in the last 90 days a discounted first-year PM contract. The conversion rate on this cold offer is usually 10-15% even before the automation is built. That gives you 10-30 contracts to onboard and validate the workflow with before you scale it.

If you already have PM contracts but they live in a paper file or a spreadsheet and you are scheduling them by hand, your first build should be the auto-scheduling workflow from Step 2. That single workflow saves the most time and pays for the whole stack in the first month. Layer on the reminder, dispatch, and completion workflows over the next two sprints. Within 90 days you should be running 5-10x the contract volume on the same office staff. If you want help mapping your current PM motion onto this architecture, the Deelo AI Assistant can review your existing customer list and identify which accounts are the highest-probability PM candidates.