Car Service Booking Chatbot on WhatsApp, with Service Reminders That Reach Customers

The Challenge

The client runs several branches offering routine servicing, oil changes, tires, brakes and air conditioning for private motorists. Its workshops already ran job cards, parts and invoicing on StarBiz, so this project was about the front door: how customers book, and how they are reminded to come back. Bookings came in by phone to each branch, by WhatsApp messages to staff mobiles and through a website form that someone had to remember to check. During the morning rush, calls went unanswered, the same slot was sometimes promised twice, and bookings taken on a personal phone never reached the branch diary. Reception re-typed every booking into StarBiz when the car arrived, so the system knew nothing about the day ahead.

Service reminders were the second problem. Staff sent them in batches from personal WhatsApp accounts, working from an exported customer list that was often out of date. Customers ignored messages from numbers they did not recognize, and sending in bulk from personal phones put those numbers at risk of being blocked or reported. Many reminders never arrived, the ones that did offered no easy way to book, and nobody knew who had been contacted. Reminders that never reach the customer are a familiar problem across Automotive.

• Missed calls and double-booked slots at busy times
• Bookings on personal phones that never reached the branch
• Bookings re-typed into the workshop system on arrival
• Reminders sent from personal numbers, often ignored or never delivered
• No view of demand by branch, service or time of day

Our Approach

We mapped the booking journey with branch managers and reception staff, from the first message to the moment a car enters a bay, and agreed what a good booking needs: the customer, the vehicle, the service, the branch, a slot and any notes. Each branch calendar was set up with the slots it can really handle, so the assistant never offers a time the workshop cannot honor.

Integration design was the heart of the project. StarBot reads from StarBiz to recognize returning customers and their vehicles. Because StarBot is read-only by default, the client approved a narrow write scope for bookings only: StarBot can create a booked workshop job, move or cancel it when the customer asks, and add a new customer as a contact. Every lookup is scoped to the role and identity of the person asking, and each action is recorded in the audit log.

For reminders, we connected the business WhatsApp number, wrote message templates for service-due and appointment reminders in Arabic and English, and submitted them for approval before launch, because WhatsApp only allows approved templates when a business starts a conversation. Opt-in wording that names the business clearly was added to the website booking flow and to the check-in form at the reception counter, in line with WhatsApp's opt-in guidance.

We started with a pilot branch, reviewed every conversation with the reception team, adjusted the flow and the slot rules, then rolled out to the other branches. Reception staff were trained on the handover inbox and on how booked jobs appear in StarBiz.

The Solution

A Booking Assistant on WhatsApp and the Website

Customers start a booking on WhatsApp or in the website chat widget and are guided step by step through the service, the vehicle, the preferred branch and an open slot from that branch calendar, using buttons and quick replies. Customers can write in Arabic or English, and StarBot answers in the language they chose. On WhatsApp it recognizes returning customers by their mobile number and offers their registered vehicles, so nobody types a plate number twice. Customers can reschedule or cancel in the same chat, and requests such as accident repairs or insurance work are handed to the branch with the full transcript attached.

Every Booking Arrives as a Workshop Job in StarBiz

When a customer confirms, StarBot creates a booked job in StarBiz for the chosen branch and slot, carrying the customer, the vehicle, the requested service and any notes. Calls that still reach reception are booked into the same branch calendar, so a slot taken by phone disappears from the chat straight away. Reception opens the day with a list of expected cars instead of an empty screen, managers see booked demand by branch and service before the day starts, and the service advisor starts the job card from the booking when the car arrives. New customers are created as contacts in the CRM, and customers can ask whether their car is ready and get the answer from the live job status. How job cards then carry parts, labor and job costing is covered in our car workshop management software case study.

Service Reminders That Reach the Customer

Reminders are driven by service history in StarBiz rather than a spreadsheet. When a vehicle nears the next service date recorded on its last job, StarBot sends an approved template from the business's own WhatsApp number to customers who have opted in, with a button that opens the booking flow. Opted-in customers with an appointment receive a reminder ahead of the visit, with options to confirm or reschedule. Opt-out requests are recorded and respected, and retention rules decide how long transcripts and personal details are stored.

A Clear View for Managers

The StarBot analytics dashboard shows booking conversations by channel, language, hour and topic, the services customers ask about most, and how many conversations were resolved without a person. Branch managers can also ask StarBot plain questions on WhatsApp, such as yesterday's sales by branch, and receive answers from live StarBiz data limited to what their role allows.

The Results

• Customers book a service on WhatsApp or the website at any hour, picking a branch and an open slot without calling.
• Bookings arrive in StarBiz as workshop jobs for the right branch and slot, so reception no longer re-types them.
• Every booking, whether by phone, WhatsApp or the web, is checked against the same branch calendar, so one slot is no longer promised twice.
• Service reminders come from the business's own WhatsApp number with a booking button, and customers act on them in the same chat.
• Opted-in customers get an appointment reminder ahead of the visit and can reschedule in the chat, which frees the slot for another customer instead of leaving a bay idle.
• Customers check whether their car is ready without calling the branch, and complex requests reach a person with the conversation attached.

Lessons for Similar Projects

1. Collect WhatsApp opt-in wherever customers already deal with you, on the website and at the reception counter, and name the business clearly.
2. Drive reminders from the service history in the ERP, not from an exported list that is out of date soon after it is made.
3. Limit the chatbot's write access to what a booking needs, and keep everything else in the ERP read-only.
4. Set slot capacity per branch from what the workshop can really handle, or the assistant will promise times the bays cannot honor.