Writing service and rego reminder messages with AI

A reminder works when it's short, says what's due, and makes the next step easy. AI can write the words. Whether you're allowed to send the message at all is a separate question, and a tool won't answer it.

What a reminder needs

Most reminders carry the same few facts:

• Who you are, by workshop name.
• What's due: a service, a registration renewal ("rego" in Australia, the yearly paperwork that keeps a vehicle registered) or a safety inspection where your area requires one.
• When it's due, or the date you last saw the car.
• How to book, with a phone number or link.
• How to stop getting reminders.

Put those facts in your prompt as plain lines. Don't ask the tool to work out the due date or the service interval. It might guess, and your records know better.

A prompt for a text message

Draft a text from [workshop name] telling a customer their car is due for a service. Stick to the facts that follow and add nothing. Plain and friendly, no exclamation marks. It must say how to book and how to opt out. Facts: last service date [date], booking number [number], opt-out wording [wording].

Run it a few times and pick the version that sounds most like your shop. Keep that one as the template, so you do the work once.

Check the rules before you send

Reminders sit close to marketing, and some countries regulate marketing messages hard. This is general information. For your own situation, ask your regulator.

In Australia, the communications regulator explains the Spam Act for marketing messages. Before you send one, you need consent from the person who'll receive it. The message must identify you as the sender and make it easy to unsubscribe.¹

The regulator also says to keep a record when someone gives express consent. Every commercial message needs an unsubscribe option, and requests must be honored within 5 working days.¹

Wikipedia's summary of the Act agrees that commercial messages need a working unsubscribe facility.²

Is a plain service reminder "marketing"? Neither the AI tool nor this page can say. Ask the regulator. A reminder that also pushes a special offer looks more like marketing, so keep reminders to the reminder.

Other countries have their own rules for texts and email, and their regulators publish guidance for businesses. Look up yours before you start a bulk send.

Where your customer list comes from

The prompt doesn't need names, but your send list does, and that's where the care goes. Note how and when each customer agreed to hear from you. The regulator also warns that you're responsible for consent on any list you buy.¹

Australia's privacy regulator, the OAIC, is a separate body from the ACMA. It recommends that organisations do not enter personal information into publicly available generative AI tools.³ That covers the send list as well, even if all you want is a quick tidy-up before the next batch goes out. Merge names into the template with your own booking software or a spreadsheet.

Making people read it

A few habits help, none of them clever.

• Put the reason first: "Your car's service is due."
• Name the workshop at the start, so it doesn't look like a scam text.
• Give one action. A single link or phone number.
• Don't scare. Skip "urgent" and "final notice" unless it's true.
• Keep texts to a couple of lines. Save detail for email.

AI tends to pad. A warm opening and a long sign-off add nothing to a text that has to be read on a phone screen in a few seconds. Cut both.

Before it goes out

Send the template to your own phone first. Look for blank merge fields, a wrong date, an opt-out that doesn't work, or a sender name that's missing. The wider checklist is on the checking page.

If a customer replies to a reminder with a question about their car, that's a job for a person. The next stage of that conversation is covered under job updates.