How to build a WhatsApp chatbot for your auto repair workshop

Start from what customers actually send. Customers ask for a service slot, an estimate for a repair, whether their car is ready, and whether pickup and drop is available.

Then look at what goes wrong today:

• Service reminder calls go to voicemail. Your service team calls for upcoming service due. Most go to voicemail, no callback. WhatsApp messages get near-universal read.
• Customers call for service status updates constantly. "Is my car ready?" — you get this 20 times a day. WhatsApp job card updates end these calls completely.
• Previous service customers don't return. Customer had great service. 6 months later, needs next service. Didn't remember you. Went to the nearest garage.

Each of these is a conversation with a predictable shape — a question, a lookup, a confirmation. That shape is what a chatbot handles well.

1. What is it for? A list message: Periodic service, Specific problem, Tyres and battery, Body and paint, Accident repair, Breakdown.
2. Which vehicle? Registration number, make and model — or, for a returning customer, "Same car as last time (MH 12 AB 1234)?" with [Yes] [Different car].
3. What is wrong? For a problem, a free-text description and, optionally, a photo or a video of the noise.
4. When? Open drop-off slots, and whether they want pickup.
5. Confirm with the slot, the address and what to bring.

The bot does not diagnose. It turns "car makes a grinding sound when braking" into a booking with the right slot length and a note the technician reads before the car arrives.

Notice what the business side does: it answers with the specific detail (time, reference, next step), it asks for one thing at a time, and it gives the customer a one-word way to reply. Those three habits matter more than how clever the bot is.

Periodic services for common models often have a fixed price, and customers ask for it before booking. Put those prices in the bot, by model, and let it quote them. Everything else — a noise, a warning light, body damage — cannot be priced from a message. The honest reply is: "We'll inspect it and send you an estimate with photos before doing any work." Customers trust that far more than a number that doubles later.

Reputoo supports both, and most auto repair workshops end up using both:

• Keyword flows — a fixed menu or trigger word ("MENU", "BOOK", "STATUS") leads down a set path. Predictable, easy to audit, right for anything with a fixed answer.
• AI chatbot — reads the customer's own words and answers from your knowledge base (website, price list, policies). Right for the long tail of questions nobody wrote a menu item for.

A sensible start for an auto repair workshop: keyword flows for the top two or three tasks, AI for everything else, and a person behind both.

Status questions are most of a workshop's inbound messages during the day. If job cards are updated as work moves, the bot answers directly from them: "Your car is in the wash bay; it will be ready by 5 pm." If job status lives only on a whiteboard, the bot should not guess — it passes the question to the advisor and says when they will reply. The fix, in the long run, is updating the job card, because that one habit answers the question for the bot, the advisor and the customer at once.

A customer stranded on a highway should not be offered a menu. Any message containing "breakdown", "accident", "tow" or "stuck" — in every language your customers use — should skip straight to a person, with the bot asking only for a live location while the handover happens. It is the one moment where speed matters more than structure.

• Complaints, refunds and anything where the customer is upset.
• Anything involving money the bot cannot see — a disputed bill, a custom quote.
• Health, safety or legal questions.
• Any customer who asks for a human. Do not make them ask twice.

For auto repair workshops specifically: extra work beyond the estimate, disputes about the bill, and warranty or insurance claims need the service advisor.

Handover on Reputoo moves the chat into the shared inbox with the conversation so far, so staff never ask the customer to repeat themselves.

Every handover from the bot should arrive with the vehicle, the registration, the problem in the customer's words, any photos or videos, and the reason for the handover. The advisor should never have to ask "which car is this?". The bot tells the customer who will reply and roughly when, especially during the morning rush when advisors are busy at the drop-off bay.

1. Connect your WhatsApp number to Reputoo (official API; takes minutes).
2. Add your website and documents to the knowledge base so the AI answers in your auto repair workshop's own terms.
3. Build keyword flows for the top tasks above. What to connect: A workshop job-card system; each job card has the customer, the vehicle and the status updates need.
4. Choose who gets handed-over chats, and during which hours.
5. Test from a personal phone, then share the number or a QR code with customers.

Accident repairs involve the insurer, a surveyor and paperwork. The bot can collect what the claim needs at the start — policy number, insurer, photos of the damage, a copy of the registration certificate — and pass the file to the advisor handling claims. It should not promise anything about approval or cashless eligibility; those are the insurer's decisions.

• Book a periodic service for a common model and check the price quoted is current.
• Report a noise with a video; check it reaches the job card.
• Ask "is my car ready?" for a car in progress and one that is done.
• Type "breakdown" and check a person picks up immediately.
• Write the registration number with and without spaces, and the model with common misspellings.

Customers who want the car collected need to give an address, a time window and where the keys will be. The bot collects all three, checks the address is within your pickup area, and confirms the driver's slot. It should repeat the pickup rules in the confirmation — the charge if any, and that photos of the car will be taken at collection — so there are no surprises when the driver arrives.

Customers describe car problems in their own words and often their own language: "gaadi garam ho rahi hai", "AC thanda nahi kar raha", "clutch hard hai". Keyword flows need those phrases; the AI chatbot handles the rest and replies in the language the customer used. Registration numbers arrive in every format — with spaces, without, lower case — so the bot should normalise them before looking up a job card.

Customers ask for status because nobody tells them. A bot that sends a short update when the job card changes stage — inspection done, parts ordered, work in progress, washing, ready — removes most of those questions before they are asked. Keep each update to a line, include the expected time only when someone has actually set it, and send the estimate as its own message with buttons so it is never buried in a stream of updates.

Three measures tell you. Bookings made in chat without an advisor typing. Status questions answered by the bot rather than passed on — which rises only if job cards are kept up to date. And the calls the desk takes about status in the afternoon, which should fall. Read the handovers weekly; a recurring reason is almost always a missing price, a missing model or a phrase the bot does not recognise.

The conversation does not end at pickup. A day later, a short check — "Is everything running well after the service?" with [All good] [Something's not right] — catches problems while they are small and before they become a bad review. "Something's not right" goes straight to the advisor with the job card attached. The same message can ask whether the customer wants a reminder when the next service is due, which is the cleanest way to collect marketing consent.