An independent auto repair shop can remind a family about each car by creating a Vehicle custom object in GoHighLevel, linking every vehicle to the family's contact record, and setting each car's own next service date. The reminder names the vehicle. The bottom line: a family with four cars has four different oil change dates, and a single contact field can only remember one.
Why the date differs for every car
Oil change intervals are set by each vehicle's owner's manual. A consumer article that cites AAA says many newer owner's manuals allow about 5,000 miles between changes under normal conditions and drop to 3,000 miles for severe driving, which it describes as short trips of under five miles in normal temperatures, under 10 miles in freezing temperatures, and hot weather stop and go traffic. Castrol says most manufacturers now recommend between 5,000 and 10,000 miles, and adds that oil degrades over time even in a parked car, so time matters as well as miles. It says a six month interval is a smart default that AAA and Consumer Reports both recommend for many drivers.
A 2010 trade report on Ford's guidance shows why one rule fails: the automaker said normal driving allows longer intervals, while special operating conditions are 5,000 miles or six months, whichever comes first, and it told owners to check the manual because there can be two recommendations. A parent's highway commuter, a teenager's short trip car, and a delivery van in the same family do not share a schedule.
How to set each car's date
| Situation | How to set Next oil service date | Source of the interval |
|---|---|---|
| Normal driving, newer car | Miles in the manual divided by the owner's monthly miles, capped at the time limit | Owner's manual, typically 5,000 to 10,000 miles per Castrol |
| Severe driving | Shorter interval, for example 3,000 to 5,000 miles | AAA definition of severe conditions, cited by a consumer article |
| Low mileage driver | Six months as a time limit | Castrol, citing AAA and Consumer Reports |
GoHighLevel does not read odometers, so the date is an estimate made at the counter. Ask the customer how many miles they drive in a month, divide the interval by that number, and cap the result at six months.
Build it in GoHighLevel
- In your GoHighLevel account, go to Settings, then Objects, and click Add Custom Object. Enter Vehicle as the singular name and Vehicles as the plural name, and label the primary field Vehicle. Only admins can create objects, and the internal name cannot be changed later.
- Add the fields to the vehicle object: Year make model, Primary driver, Next oil service date, and Next inspection date.
- Open the object's Associations tab and add an association to Contacts with the label Owner. GoHighLevel's documentation shows this flow for linking records, and one object can link to many contacts.
- Create a record for each vehicle and link it to the owner contact.
- In Automation, choose Create Workflow and pick the workflow based on your custom object.
- Add the Custom Date Reminder trigger. For object workflows, GoHighLevel says the date field selector shows date fields on the same object. Select the date field and add Before Number of Days set to 30.
- Add the Add Associated Records to Workflow action, choose Contact as the object type, filter by the Owner association label, and select the contact workflow that sends your message.
- Build the contact workflow with Send SMS and Send Email actions, inserting the vehicle name with the variable picker.
Why the second workflow? GoHighLevel's support matrix lists conversations, bulk SMS, calendars, and payments as not supported for custom objects, and it lists emails to associated contacts as coming soon. The documented way to reach the owner is the Add Associated Records to Workflow action, which enrolls the linked contact in a normal contact workflow.
Text to send at 30 days
Hi [first name], the oil change for your [vehicle] is due around [next oil service date]. Book a time here: [booking link].
What the workload looks like
A shop with 1,000 customer families averaging two vehicles has 2,000 vehicles. On a six month time cap, that is at least 4,000 oil service dates a year, about 77 a week (4,000 divided by 52 is 76.9). Per vehicle reminders make each of those a specific message instead of a generic postcard.
Mistakes to avoid
- One rule for every car. Use the manual for each vehicle.
- Counting miles only. Castrol says time matters, so add a six month cap.
- Messaging the wrong driver. Store the primary driver and link that contact if a teenager drives the car.
- Forgetting to reset the date. Set the next date at every visit.
Check before you switch it on
US text messages sent from a standard 10 digit number need A2P 10DLC registration. The HighLevel support portal says registration is required for texts to US recipients from 10 digit long code numbers and that toll free numbers do not require it. HighLevel's opt in guidelines also say a person cannot be forced to agree to text messages in order to submit a form, so keep the consent box optional. One compliance guide separates informational texts, which need documented consent, from marketing texts, which need prior express written consent. Ask your attorney which category your reminders fall into. Families share phone numbers, so confirm who wants texts and store an email address for the others. This is general information, not legal advice.
Questions people ask
Is the 3,000 mile oil change a rule?
A consumer article citing AAA says most newer owner's manuals allow about 5,000 miles under normal conditions, with 3,000 miles for severe driving. Use the manual for each car.
Can GoHighLevel track mileage?
Not by itself. You estimate the next date at the counter and store it.
Can I remind by vehicle in one message?
Yes, if each vehicle is a linked record. Keep one message per vehicle so the family can book each one.
Ready to try it yourself? Start a GoHighLevel account here.
You can also see this in action in our GoHighLevel capabilities demo.