The enquiry that cannot be priced from a menu
A knocking from the front left over bumps. A warning light that comes and goes. A judder at seventy. These are the jobs a fixed-price menu cannot cover and the phone handles badly: the driver describes it poorly, the person answering is under a car, and the call ends with "bring it in and we'll have a look", which is a booking the driver may never make.
A fault form does the first conversation properly. It collects the registration, the symptoms in a structured way, photos or a short video, and when the driver can take a call. The garage rings back at a time it chose, already knowing the car and the problem. Here is how to build it.
The fields
Keep it to what a technician would ask on the phone:
- Registration. Looked up where your software or a lookup service supports it, so make, model, engine and year arrive with the form.
- What is happening. A short free-text box, with the prompt "Describe it as you would to a friend".
- When it happens. Tick boxes: on start-up, when braking, when turning, at speed, over bumps, all the time, intermittently.
- Any warning lights. Tick boxes with the common symbols named in words: engine, ABS, battery, oil, tyre pressure, other.
- Sounds. Knocking, grinding, squealing, whining, hissing, none. A driver cannot always describe a noise, but they can pick one from a list.
- Photos or video. A camera button that accepts several images and a short clip. Dashboard lights, a leak on the driveway, a worn tyre, a fifteen-second video of the noise.
- Is the car driveable. Yes, carefully, or no. This decides whether the reply is a call-back or a recovery conversation.
- Call-back slot. Morning, lunchtime, afternoon, early evening, with the mobile number.
Eight fields, most of them taps. Under two minutes on a phone.
Where it lands
The form should create a job lead or enquiry in the garage software you already run, with the photos attached, so the call-back happens from the diary rather than from an email nobody watches.
- Autoflow, Garage Hive, Shopmonkey, Tekmetric, Workshop Software: where the software offers an enquiry or appointment request form, embed it or post to it, and let its notifications reach the front desk. Where it does not, the site form posts through an automation tool that creates the customer and vehicle record and attaches the images.
- No garage software yet: the form emails a dedicated address that the front desk phone receives with notifications on, images resized so they arrive, plus a copy to a shared inbox.
Whichever route, the person who does the call-back sees the registration, the symptoms and the photos on one screen before dialling.
The call-back promise
The thank-you message states it: "We will call you in your chosen slot. If the car is not safe to drive, ring us now on [number]." The same line sits at the top of the form. A fault form without a stated reply time becomes a black hole in the driver's mind and they ring a competitor while waiting.
The call-back itself is short: confirm the symptoms, give an honest range or a diagnostics fee, and book the car in with the slot from the diary. The form has already done the part that used to take ten minutes of a busy mechanic's time.
Framing the quote
The form is where you say which jobs are priced from the menu and which need a look. A line above the fields: "Services, MOTs, brakes and tyres are priced on our menu and bookable online. For anything else, tell us here and we will call you back with an honest range or a diagnostics fee." Drivers trust a garage that says plainly what it can and cannot price in advance.
Photos of cars and driveways
Images may show a registration plate, a house and a person. Store them in the garage software or a private store, not a public uploads folder; delete enquiries that did not become jobs after a few months; use them only for the quote. A line under the camera button says so. In the UK and EU a registration number is personal data; treat the whole form as such.
Sub-types
A body shop wants photos from two angles with a coin for scale and the registration for the paint code, plus an insurance-or-private question. An auto glass form asks chip or crack, size, position and insurer. A mobile mechanic adds the address and parking access and a line about jobs that need a workshop. A motorcycle workshop swaps registration lookup for make, model and year where lookup is weaker for bikes. Same form, different fields.
Testing it
Submit from a phone with three photos and a short video. Time it from submit to the notification reaching the front desk. Check the images open at a usable size and the registration resolved. Do it monthly; integrations break quietly, and it is on the care plan for every garage site we look after.
Where this sits
The fault form with photos and a call-back slot is one of the six must-haves on every automotive business website we build, alongside the fixed-price menu it complements. The menu handles the jobs you can price; the form handles the rest, and it lands in the same diary. Together they mean the phone rings less and the calls that do happen are useful.