A client was in for a service a year ago, nobody reminded them about the next one, and the car ended up at a workshop across town — not because that one is better, just because it reached out first. A workshop with no reminder schedule loses clients for a reason that's entirely avoidable.
This page covers how to set buffer time and a daily limit in a booking schedule, when to send a service reminder, and where Google even gets its data on your workshop's popular hours.
Why a workshop loses clients over missing reminders
A client rarely remembers exactly when their last service was — it's the workshop that has that date on record, if it records it at all. Without a system that reminds on its own, that information sits in a paper client card or in the memory of whichever mechanic handled that job. When the mechanic changes, or the client list grows, the reminder simply doesn't go out.
This isn't a goodwill problem — it's a scale problem. A workshop serving ten regular clients a month can remember each one individually. A workshop with a hundred clients has no chance without a schedule that counts on its own who needs a reminder and when.
A schedule with buffer time and a daily limit — what can be set
An appointment schedule lets you set a minimum lead time for booking, buffer time between appointments, and a maximum number of bookings per day (Google Calendar Help, Create an appointment schedule). Buffer time is the gap left between one job and the next — without it, one late client pushes back the whole day at that bay.
A daily limit guards against a different trap: accepting more cars than the workshop can realistically handle, just because the schedule formally had open slots. Set once, the limit rejects excess bookings on its own instead of leaving that to on-the-spot improvisation at the front desk.
How many reminders is it worth sending
The same schedule lets you send up to 5 reminders per booking, though the content of the reminders themselves can't be freely edited (Google Calendar Help). In practice, fewer than the limit makes sense for a periodic service: one reminder with lead time, one right before the appointment — more starts to feel like nagging rather than reminding.
Popular hours on a Google profile: where they come from and what can't be changed
Google calculates popular times, wait times, and visit duration from aggregated, anonymized data from users who have opted into Location History — not from data a workshop could enter itself (Google Business Profile Help, Popular times, wait times & visit duration). This information appears on a profile only once the workshop has enough visits recorded this way — a small workshop with little foot traffic may simply never see it.
An important caveat: this data covers physical visits to the location, not phone calls. A workshop that mostly gets calls and books remotely won't see the real picture of its phone line's load in "popular times" — that's a different kind of traffic than what Google measures.
How this helps plan mechanics' shifts
Since the data is read-only, the one thing a workshop can do with it is use it for staffing: if the profile shows a peak of visits on Monday mornings, that's when it's worth having more than one mechanic on the floor — not on a quiet Wednesday afternoon. It's information for staffing the schedule, not for changing opening hours.
Do reminders actually reduce no-shows
Microsoft describes its booking tool as one where email and SMS notifications "reduce no-shows" — fewer cancelled, wasted appointment slots (Microsoft Learn, Microsoft Bookings overview). That's the tool vendor's own claim, not independent research — worth distinguishing before promising clients or a workshop owner a specific drop in no-shows.
The mechanism behind it is simple and makes sense on its own: a reminder the day before gives a client the chance to cancel or reschedule ahead of time instead of simply not showing up — and the workshop could fill that slot from a waitlist in the meantime. That's a mechanism, not a guarantee of a number.
A reminder cycle that depends on the vehicle, not one date for everyone
Service frequency — an oil and filter change once a year or by mileage, depending on the vehicle manufacturer's recommendations — varies between makes and models. A workshop that sends the same "a year has passed" reminder to every client, without exception, ignores the difference between a car doing 8,000 km a year and one doing three times that.
A practical fix is two fields on the client card instead of one: date of the last service, and approximate annual mileage if the client gives it. The system calculates the next reminder date from what it actually knows about that car, not from one fixed rule for everyone.
Two kinds of phone calls: booking a service and "something's knocking"
A call to book a routine service and a call about "something's been knocking under the hood since yesterday" are two different requests that need two different paths. The first can be fully automated — a time slot, a confirmation, a reminder. The second needs a human right away, because only a mechanic can ask the right questions and judge whether it's something that can wait a week or something that needs the car in today.
Mixing these two paths into one universal booking form is a common mistake: a client with an urgent problem lands in the same slot as someone booking a routine oil change two weeks out, and neither side comes out satisfied.
When seasonality needs its own window
Tire-change season is a separate case: traffic concentrated in a short window that needs a denser, more frequent schedule than ordinary services spread evenly through the year — it's worth keeping a separate pool of slots for it, so it doesn't push regular service clients further out.
What not to hand to the system
A diagnosis based on a client's description of "something's off, but I don't know what" stays with the mechanic, not with the automated messaging system. A system handles a repeatable, predictable task well — remind, confirm, ask for a time. It doesn't handle judging whether a sound the client calls "knocking" is a loose heat shield or a suspension problem — that takes questions only someone who actually fixes cars knows to ask.
A clear division of roles protects both sides: a client with a concerning symptom reaches a human faster, and the automated schedule never tries to play diagnostician, which it wasn't built to do. We cover the broader line between what a system can and can't take on in Process automation in a company: what can realistically be handed over to a system and what cannot.
What to do yourself: a list of clients from a year ago
- Pull from your records (paper or spreadsheet) every client whose last service was a year ago or more.
- Split them into those with an approximate annual mileage on file and those without it.
- For clients with high annual mileage, consider reminding them earlier than the one-year mark.
- Set a buffer time and a daily limit in the schedule before sending reminders in bulk — otherwise more requests will come in than the workshop can handle in a single day.
- Separate "book a service" from "report a problem" right at the description stage — different paths, different response times.
- Keep tire-change season as its own separate pool of slots on the calendar.
On what implementing this kind of automation in a small business actually costs, see How much does process automation cost in a company? 2026 ranges and what changes them. It's also worth tracking how many clients actually came back after a reminder — on choosing numbers like that, see Reporting automation: how to set up numbers that the owner actually looks at.
What this looks like when a system manages it
Instead of a client card checked from memory, data on every client's last service lands in one place:
- 01last service date
- →02reminder a month ahead
- →03reminder a week ahead
- →04a call if there's no response
Automatic messages send these reminders on their own — by SMS, email or WhatsApp. Booking Systems let a client pick their own open slot for a routine service, with no phone call and no double-booking. When someone calls with an urgent issue, AI reception and telephony answers and qualifies the request right away, passing on what needs a human. CRM and automations keep customer data in one place instead of a record someone has to remember to open, and Integrations tie that to the calendar and till the workshop already uses. Diagnosing "what's knocking" always stays with the mechanic — the system's only job is to make sure no client a year past their last service falls out of view. We cover the broader picture of workshop automation in Car workshop automation: phone, appointments and maintenance reminders.
Frequently asked questions
How many reminders can be set in a booking schedule?
A booking schedule allows up to 5 reminders per booking, though their content can't be freely edited. For a periodic service, two are usually enough: one ahead of time and one right before the appointment.
Do reminders actually reduce the number of no-shows?
Booking tool vendors claim that email and SMS notifications reduce no-shows — that's a vendor claim, not independent research. The mechanism makes sense: a client gets the chance to cancel ahead of time instead of simply not showing up.
Where does Google get its data on a workshop's popular visiting hours?
From aggregated, anonymized data of users with Location History turned on, and only once the workshop has enough of these visits recorded. The data covers physical visits to the location, not phone calls.
Can a workshop manually add its popular hours to a Google profile?
No. A workshop can't enter or change this data itself — it appears only once Google has gathered enough aggregated visit data.
How do you separate a call to book a service from a call reporting a breakdown?
A routine service booking can be fully automated through an online schedule. A "something's knocking" call needs a human right away, since only a mechanic can judge urgency from questions an automated form won't ask.
What should you do about a client who doesn't respond to reminders?
If reminders (say, one a month ahead and one a week ahead) go unanswered, the next step is a phone call from a person, not another automated message — it's also a good moment to check whether the client is even still using that contact.