Service Reminders Shouldn’t Live in Someone’s Head
Updated: Sep 4
The next service is easy to remember when you’re standing beside the machine. Six months later, it has disappeared behind a hundred other jobs.
G’day, it’s Dazza. Service work has a funny habit of looking organised right up until the reminder depends on one person remembering it.
You finish a job, tell the customer it should be checked again in six or twelve months, and make a mental note to follow it up. Maybe the date goes in a diary. Maybe it gets scribbled on the job sheet. Maybe somebody in the office says, ‘Yep, I’ll put that in.’
Then normal work takes over. Phones ring, urgent jobs arrive, staff change, emails pile up and the reminder that felt obvious on Tuesday quietly disappears.
A service reminder is really a future promise
When you tell a customer, ‘We’ll remind you when it’s due,’ you have created a small future job for the business.
It might be an air-conditioner service, pump inspection, filter change, equipment check, caravan system service, safety inspection or any other repeat work that makes sense for that customer.
The problem is that the work is due months from now, while the information needed to remember it exists today. If that future action only lives in someone’s head, the business is relying on memory across a very long gap.
Good intentions are not a reminder system
Most missed reminders are not caused by people being careless. They are caused by busy people using memory as storage.
A tradie can remember an impressive amount while a job is active: the odd noise from the unit, the customer’s gate code, the part that needs ordering and the promise to ring on Thursday.
But once the job is finished, the brain quite reasonably moves on to the next problem. Add six months and twenty, fifty or a hundred other customers, and ‘I’ll remember that’ is no longer much of a system.
A wall calendar can help. So can a spreadsheet, diary or phone reminder. The weakness comes when the information is scattered between people and places, or when nobody can tell whether the follow-up actually happened.
The useful record starts at the completed job
The best time to set up a future service reminder is while the current job is still fresh.
At minimum, the record should make it easy to understand who the customer is, what was serviced, where it is, roughly when the next service is due, and any useful note the future person needs before making contact.
That last part matters. ‘Service due October’ is less useful than knowing what equipment was involved and why the interval was chosen.
It also helps to separate a genuine service due date from a sales guess. A reminder should come from the actual job, manufacturer guidance, agreed maintenance arrangement or another sensible basis — not from pestering customers because the calendar says it has been a while.
Someone also needs to know what happened next
Remembering the date is only half the job.
Suppose the reminder appears and somebody emails the customer. Did they reply? Did they ask to be contacted next month? Was the service booked? Did they say they sold the equipment? Was there no response at all?
If those outcomes are not recorded, the reminder can become another loose end. Two people might contact the same customer, or everyone might assume somebody else handled it.
A useful follow-up process needs a simple next state: waiting on us, waiting on them, booked, snoozed, no longer required, or whatever language suits the business. The exact labels matter less than making the next responsibility visible.
This problem is bigger than service reminders
The more I work through these small admin problems, the more often the same pattern appears: the business is not short of information — it is short of something quietly keeping an eye on what needs attention next.
That applies to service reminders, but also to unanswered emails, quotes waiting for a decision, documents somebody promised to send, customer questions that need a reply and dozens of other small communications that can disappear into a busy week.
That broader follow-up problem is something I’m actively working through with Dazza. The idea is closer to a digital secretary than a giant CRM: keep an eye on the loose ends and bring the right one back to your attention at the right time.
It is still work in progress. I’m not offering a finished Dazza follow-up product for people to use today, and I’m deliberately keeping the early thinking focused on reminders and visibility rather than software trying to take over customer conversations.
The customer should not have to remember for you
There is a simple customer-side benefit to getting this right too.
If a business genuinely knows that something should be serviced again, it is useful to make that easy for the customer. They should not have to find an old invoice, remember which month the work happened and then chase the business that already has the history.
A sensible reminder can be a service rather than a sales pitch: ‘We serviced this around this time last year. It may be due again. Here’s what the previous job was.’
And if the customer says not now, the process should respect that rather than turning into an endless sequence of automated messages.
Put the reminder somewhere that can remember longer than you can
There is nothing wrong with having a good memory. It is just a poor place to store a business process for the next twelve months.
When a repeat service becomes apparent, capture it with the job. Give it a due date. Keep enough context that the reminder makes sense later. Then make sure somebody — or eventually something — can see whether the follow-up was actually dealt with.
The aim is not more admin. It is to stop useful future work, and useful customer service, disappearing simply because everybody got busy.
Comments