A WhatsApp Playbook for Car and Motorcycle Workshops: Bookings, Estimates and Service Reminders

A motorcycle workshop services forty bikes a day. Most customers come back only when something breaks, to whichever workshop is nearest. The owner knows that regular servicing every few months would double repeat visits, and that a reminder would bring many of them back. There is simply nobody free to work out whose service is due and write to them. A WhatsApp playbook for workshops turns that intention into six small routines.

The record that makes it possible

Reminders need data. For each visit, record five things:

• Customer name and WhatsApp number.
• Vehicle: plate number, model, year.
• Date and odometer reading.
• Work done and parts replaced.
• Next recommended service: date or distance, and what it will involve.

This takes a minute at the counter. Without it, every flow below is guesswork. With it, the customer's next visit is already scheduled in your records before they leave.

Flow 1: booking

Customers ask the same four things: can you do it, when, how long, roughly how much.

A reply that settles it in one message:

"Good morning, Mr. Anton. Yes, we can do a regular service for your Vario 125. We have slots tomorrow at 09:00 or 13:00. It takes about an hour. A regular service starts from 85,000, and we will confirm the total after checking the bike. Which time suits you?"

When they choose, confirm:

"Booked: Wednesday 09:00, regular service, Vario 125, plate B 1234 XYZ. Please arrive ten minutes early. Reply here if you need to change the time."

On the morning itself, a short reminder reduces no-shows:

"Reminder: your service is at 09:00 today. See you soon."

Flow 2: estimate and approval

The mechanic finds something beyond the booked work. Nothing extra is done before the customer agrees in writing.

"Mr. Anton, during the check we found the rear brake pads are worn to about 1 mm, with a photo attached. We recommend replacing them today.

Regular service: 85,000 Rear brake pads, original: 65,000 Fitting: 15,000 Total: 165,000

Shall we go ahead with the brake pads? Reply YES to approve, or NO to do the service only."

Three things matter here:

• A photo. It shows the problem and builds trust.
• An itemised price.
• A clear yes or no.

If the customer declines, note it in the record: "Rear pads at 1 mm, replacement declined on this date." It protects the workshop and gives the next reminder its subject.

Flow 3: progress

For jobs longer than a few hours, one update prevents three calls.

"Update on your Avanza: engine oil and filter done, brake pads fitted. We are waiting for the AC part, arriving at 14:00. Estimated finish 16:30. We will message you when it is ready."

Send an update when something changes: a delay, a part not available, a new finding. Silence is what makes customers anxious.

Flow 4: ready for pickup

"Your Vario is ready, Mr. Anton.

Work done: regular service, rear brake pads replaced. Total: 165,000. Payment by cash, transfer or QRIS. We are open until 17:00 today.

Next service recommended: around 12 February, or at 14,000 km."

The last line plants the next visit while the customer is paying attention.

Flow 5: follow-up after service

Two or three days later:

"Good afternoon, Mr. Anton. How is the bike after Wednesday's service? If anything does not feel right, tell us and we will check it at no charge."

This message does three jobs. It catches problems before they become bad reviews. It shows care. And when the customer answers "all good, thank you", it is the right moment to ask:

"Glad to hear it. If you have a minute, a review on Google helps a small workshop like ours a great deal: [link]."

Flow 6: the service reminder

This is the flow that pays for the others.

About two weeks before the recommended date:

"Good morning, Mr. Anton. It has been almost three months since the last service on your Vario, plate B 1234 XYZ. It is due for a regular service and an oil change. Last time we also noted the front tyre was getting thin. Would you like to book a slot this week?"

Notice what makes it work:

• It names the vehicle and the plate.
• It refers to something specific from the last visit.
• It offers an action.

If there is no reply, one gentle follow-up a week later, then stop until the next cycle.

"Hello, Mr. Anton, just following up on the service reminder. We have slots on Saturday morning if that is easier. If you have already serviced it elsewhere, no problem at all, just let us know and we will update our record."

Other reminders worth sending

From the same records:

• Declined work. "Last visit we recommended replacing the rear pads. Would you like to do that now?"
• Seasonal checks. Before the long holiday journey home: tyres, brakes, battery, lights.
• Document dates, if you record them: vehicle tax or inspection due dates, where you offer help with them.
• Warranty follow-up on a major repair.

Rules that keep the number safe

• Message people who are your customers and who gave their number for service. Reminders about their own vehicle are expected. Unrelated promotions to a bought list are not.
• Offer a way out. "Reply STOP if you prefer not to receive reminders", and honour it.
• Do not blast. Send reminders in small batches through the day, personalised with name and vehicle. Identical bulk messages to many people are how business numbers get restricted.
• Use a business number, owned by the workshop, not a mechanic's personal phone.

Who does what

In a small workshop:

• Counter staff record the five items at every visit and handle booking and pickup messages.
• The mechanic sends photos and findings to the counter for the estimate.
• One person, each morning, opens the list of services due in two weeks and sends the reminders. Fifteen minutes.

That morning list is the heart of it. It can be a spreadsheet sorted by next service date. It works better as a filter in a customer system, where the reminder can be drafted for you.

What to measure

• Reminders sent, and bookings that followed.
• No-show rate on bookings.
• Share of customers who returned within six months.
• Estimates approved versus declined.

If a quarter of reminders turn into bookings, the fifteen minutes each morning is the most profitable time in the workshop.

In Polynusa

Polynusa keeps customers, notes and conversations together in one inbox on your business WhatsApp number, with follow-up tasks by date, and its AI agents can draft booking replies and reminders for a person to approve. See the pricing page.

Summary

Record customer, vehicle, odometer, work done and next service at every visit. Use six flows: booking with confirmation, written estimate approval with a photo, progress updates, a pickup message that names the next service, a follow-up two days later, and a personalised reminder two weeks before the due date. Send in small batches, offer a way to opt out, and give one person fifteen minutes each morning to work the list.

FAQ

How often should a workshop remind customers about service?

Base it on the vehicle, not the calendar alone: the interval recommended for that vehicle in distance or months, whichever comes first, counted from the last service you recorded. One reminder about two weeks before the due date and one follow-up a week later is enough. More than that starts to feel like pressure.

Should estimates be approved by chat?

Yes, in writing, before extra work begins. A message listing the work, parts and price, answered with a clear approval, protects both sides. It prevents the commonest dispute in a workshop: a bill higher than the customer expected for work they do not remember agreeing to.

What customer data should a workshop keep?

The customer's name and number, each vehicle with its plate, model and year, and for each visit the date, odometer reading, work done, parts used and the next recommended service. Keep only what you use, protect it, and honour requests to stop receiving reminders.