Services
Custom SoftwareCRMs, portals, dashboards + internal tools. Automation + IntegrationsWorkflows, APIs + business logic. DataScraping, enrichment + monitoring. AIAgents, assistants + knowledge systems. WebWebsites, performance + conversion.
Company
AboutWorkJournal
Start a project →

How to Automate Annual Service Reminders by Site or Asset

Prompt customers to book their next service, even when they manage several sites. Keep each due date intact when a visit is booked, moved or cancelled.

NM
Written byNathan MackenzieFounder · ZappFlow
Practical notes on software, automation, data, web and AI.

To automate annual service reminders, give each piece of equipment or independently serviced site its own next-due date. Use that date to prompt the right customer contact to book, pause the prompt when a visit is booked, and update the service cycle only when the work is confirmed complete.

A service-due reminder asks the customer to book work that is coming due. An appointment reminder tells them about a visit they already booked. Keep those messages separate so a customer with a visit in the diary does not get another request to book it.

The idea in one viewVISUAL GUIDE
SHOW HOW THE PROCESS IMPROVES STEP BY STEPOPERATING JOURNEY

From separate boiler due dates to the next service cycle

01

Track each boiler

Give each boiler its own due date and site contact.

02

Invite the right person

When a boiler is due, ask its service contact to book.

03

Pause when booked

Link the booking to the boiler and pause its booking prompt.

04

Confirm, then reset

After service is confirmed, set the next due date. If cancelled, keep it due.

Keep each site’s schedule distinctDue-to-book prompts are not visit reminders.

1. Choose the record that should trigger the reminder

Track the reminder against the smallest unit you can book and complete independently. If two boilers at one property can be serviced on different dates, give each boiler its own record. If the whole site is always booked and serviced together under one schedule, a site record may be enough. A customer record can hold the account details, but it should not supply one due date for all their properties.

On each service record, keep the site and equipment identifiers, the last confirmed service date, the schedule rule, and the current due date. Link any active booking to that record and keep its status separate. If one booking covers several boilers, link it to each one it actually covers.

Pick the person who can arrange the work

Record who should receive service-due messages for each site or item. That might be the property manager who approves the work rather than the caretaker who lets the technician in. Use the named service contact for the item or site first. Fall back to an account contact only if staff have confirmed that person handles bookings for that location. If there is no valid recipient or permitted channel, create a staff task instead of guessing. Look up the current contact when the message is sent, not just when it is queued.

2. Set the due-date rule and reminder timing

Rolling interval: Calculate the next due date from the actual date of the last confirmed service. If the agreed interval is 12 calendar months and the boiler was serviced on 12 May, the next cycle is due on 12 May the following year. Agree how to handle dates such as 29 February rather than letting a software default decide. OctopusPro’s recurring reminder documentation shows one implementation that starts the interval from a completed booking.

Fixed schedule: Use the agreed calendar date for each cycle. If a site is due every 1 October, completing this year's service in September does not move next year's due date to September. Link the completed visit to the cycle it fulfils. If a late visit could be mistaken for the next cycle's service, have staff confirm which cycle to close before advancing the schedule.

Set the first reminder far enough ahead for the customer to approve the work and for your team to offer a slot. Choose a follow-up date and decide when an unanswered or overdue item becomes a staff task rather than another automatic message. Email can carry the site and equipment details; an SMS may suit a short booking prompt if the contact can receive texts. Either way, name the site, identify the equipment, state when it is due and give one clear way to book. Make sure someone monitors replies.

3. Apply these reminder rules when the job changes

A booking should pause reminders for the service it covers without changing the due date.

  • Reminder window opens: Send only if the service cycle is still open, no live booking covers it and the current recipient is valid. Check those conditions again immediately before sending, and record which reminder step went out so a retry does not send it twice.
  • Visit booked or rescheduled: Suppress outstanding booking prompts for the covered items. Keep the original due date visible, including when the booked visit falls after it. A move to a new slot should not restart the sequence.
  • Visit cancelled or no access: If there is no replacement booking, return the item to the due or overdue follow-up list with the same date. Check what was already sent before deciding whether to send the next prompt. Route no-access cases to staff if arranging entry needs a conversation.
  • Service confirmed complete: Close that item’s current cycle, suppress any old reminders and calculate the next due date under its schedule rule. If a multi-item visit only completed some of the work, advance only those items.
  • Contact changes: Update the recipient without resetting the due date or the reminder history. Any unsent message should use the new contact; if that contact cannot be reached, leave the item visible for staff.
WHAT HAPPENS WHEN SOMETHING GOES WRONGBACKUP PLAN

When a boiler visit is cancelled or access fails

01 · PROBLEM
Visit cancelled or no access

The visit cannot go ahead, and there is no replacement booking.

→
02 · FALLBACK
Return it to follow-up

Put the boiler back on the due list with its original due date. Check what reminders were sent.

→
03 · RECOVERED
Replacement booking made

Pause reminders for this service again, keeping the original due date visible.

OUTCOME
The boiler stays tracked without reminders duplicating a booked visit.
Due date preserved

Worked example: one property manager, two boilers

Suppose Maya arranges services at Cedar Court and Mill House. Cedar Court’s boiler is due on 12 May 2027 under a rolling 12-month rule. Mill House’s boiler is on a fixed annual schedule of 1 October. Maya is the service contact at both sites at the start; each site has a different caretaker for access.

  • Booking: Maya books Cedar Court for 8 May. Stop Cedar Court’s prompts and retain its 12 May due date. Mill House stays on its own October schedule.
  • Cancellation: Maya cancels the 8 May visit without rebooking. Cedar Court goes back on the follow-up list, still due on 12 May. If it remains unserviced after that date, show it as overdue. Do not resend the first reminder simply because the booking was removed.
  • Completed visit: Cedar Court is serviced on 20 May. Close its open cycle and set its next due date to 20 May 2028. When Mill House is serviced on 24 September for its October cycle, its next due date is 1 October 2028.
  • Change of contact: Before Mill House’s September visit is booked, Maya hands that site to another manager. The next unsent booking prompt goes to the new manager. Cedar Court remains assigned to Maya, and neither due date changes because of the handover.

4. Test your existing job software before adding an integration

Run the two-site example with test contacts and check the message log as well as the job screen. Ask whoever handles the service diary to work through these checks:

  • Bring one boiler into its reminder window. Confirm the other boiler stays untouched and the message goes to the person who arranges the work.
  • Queue a prompt, then book the visit before it sends. Confirm the prompt stops. Move the booking and check that the prompt stays paused.
  • Cancel without a replacement, then test a no-access outcome. Confirm the item returns to a list staff actually review and keeps its original due date. Repeat with a replacement booking and confirm reminders stay paused.
  • Complete a rolling service late and a fixed-date service early. Check the next dates and verify that an item left incomplete on the same job does not advance.
  • Change a contact after a message is queued. Check the recipient at send time and confirm that a missing contact or failed send creates a visible follow-up task.

Use the software you already have if it passes those checks and staff can see what is due soon, overdue, booked or waiting for action. Start with a small batch of service records and give someone on the scheduling team responsibility for checking exceptions before expanding.

If completed work, bookings and contacts live in different tools, use the reminder rules above to scope the automation and integrations you need. Specify which tool owns each record, how a booking is matched to the correct site or asset, and who checks failed updates. If the reminder tool cannot confirm whether a booking is current, hold the send for review rather than risk chasing someone who has already booked.

ZappFlow · practical next step

Connect your service records to your reminders

Show ZappFlow where you record completed visits, where bookings are made and how you decide what is due. An example involving two sites or a cancelled visit will help us assess whether your existing software can handle the rules or needs an integration.

Discuss your service reminders