The conversation that goes nowhere
"It's making a noise." "What kind of noise?" "A sort of grinding, but only sometimes." "When you brake, or turning, or all the time?" "I'm not sure." Five minutes on the phone, no registration, no idea whether it is a wheel bearing or a stone in the brake shield, and the driver wants a price. You cannot give one, so you say bring it in, and they hear that as the start of the overcharging story.
A fault needs a look. The website's job is to make the first conversation useful, so that when the car comes in you already know the vehicle, have seen the symptom, and have agreed what the look will cost.
Separate faults from bookings
The first fix is on the Book online page and every service page: say which jobs are fixed price and bookable, and which need diagnosis. Servicing, tests, brakes, tyres and air con book straight into the software with a stated price. A noise, a warning light, a leak, a misfire, a smell goes to the fault form. A driver who books a "repair" for an unknown fault arrives with the wrong expectation; the split prevents it.
The fault form
Six or seven fields, on a dedicated page linked from the header as "Report a fault" or similar, and from the Repairs and diagnostics page.
- Registration. Looked up where your software allows, so the make, model and engine arrive with the form.
- What is happening. A short box with a placeholder: "e.g. grinding noise from the front when braking".
- When it happens. Tick options: all the time, when braking, when turning, when cold, at speed, when idling. Drivers can tick a box when they cannot describe a sound.
- Warning lights. Tick which, with a small picture of each common one. Most drivers know the shape, not the name.
- Photos or a short video. A large "Add photos" button opening the camera. A photo of the dashboard, the leak on the drive, the tyre. A ten-second video captures a noise better than any description.
- Is the car driveable? Yes, no, not sure. This decides whether the reply is a slot or a recovery conversation.
- Name, mobile, and a call-back slot. Two or three windows: this morning, this afternoon, after five. The driver picks when they can talk; the desk rings when it is quiet.
Nothing else. No full address, no account.
Where it lands
The form lands in your garage software as a job lead with the attachments, or as a notification on a phone with the photos, within a minute. Autoflow, Garage Hive, Shopmonkey and Tekmetric take web requests or enquiries; where the software does not, an automation forwards the form to a phone and a shared inbox. Either way, the photos and the registration are in front of the technician before the call-back.
The call-back, and the diagnosis slot
The call-back is short because the form did the work. "Thanks for the video. Sounds like the front pads are down to the wear indicators, but I'd want to see it. We charge [fee] for a diagnosis, which comes off the repair if you go ahead. Can you do Thursday morning?" The diagnosis slot is bookable from the site too, with the fee stated, for drivers who would rather skip the call.
The diagnostics fee belongs on the Services and prices page. Stating it removes the suspicion that the look is free until the bill arrives.
The reply promise
On the form and on the confirmation: "We reply to every fault enquiry the same day." Then keep it. A holding reply within the hour when you can ("Got your photos, I'll ring at the time you picked") and a proper call the same day always. The promise is what makes a form feel as reliable as walking in.
Auto glass, body shops and mobile mechanics
The same form, tuned. An auto glass business asks for a photo of the chip and whether the driver is claiming on insurance; many quotes go out without a visit. A body shop asks for two angles, a coin for scale and the registration for the paint code, and most estimates go out the same day. A mobile mechanic asks for the address and parking access, and uses the photos to decide whether the job can be done on a driveway at all.
Privacy and spam
Registration, mobile and photos are personal data. A line beneath the button: "We use your details only to look at this fault." Photos stored in the software or a secure store, not a public uploads folder, and deleted after a few months if the job did not happen. A honeypot field and server-side file checks for the bots; no CAPTCHA unless spam becomes real, because it costs completions.
What changes
Garages that add a fault form report call-backs that take two minutes instead of ten, diagnosis slots booked that would have been "I'll bring it in sometime", and fewer cars arriving with a fault nobody described. The technician sees the video before the car.
Where this sits
The fault form with photos and a call-back slot, wired to the garage's software and phone, and the split between bookable jobs and faults are part of every automotive business website we build. The look still has to happen; the site makes sure it is the second conversation, not the first.