"It rattles sometimes" is a start. "A metallic rattle for a few seconds on the first start of the morning" gives the next person rather more to work with.
In this example, a small petrol hatchback is being booked over the phone for an investigation. The caller has already explained when the noise happens. By the time the keys arrive, a different person may be looking at the diary. If the booking says only "Noise", the useful part of that conversation has gone missing.
That is where MechanicO's existing Garage notes field earns its space. When a garage enters a booking in the Planner, it can include a short note. Open that booking's details later and the text appears under "Notes". It stays alongside the booking rather than depending on somebody remembering the call. [1]
Keep the customer's observation
In the garage's Booking workspace, open "Planner" and choose "Add booking". While entering the appointment, use the optional "Garage notes" field for the relevant explanation before adding the booking. To read it afterwards, open the booking on the Planner and look for "Notes" in its details. [1]
I'd use that field to preserve the symptom in the customer's own terms. What happens? When does it happen? Where do they think it comes from? Keep the wording clear enough for somebody who did not hear the original conversation.
For our hatchback, a useful example might be: "Customer reports a metallic rattle for a few seconds on the first morning start. Says it is not noticeable once warm. Please discuss the reported symptom at arrival."
That is an invented example of note wording, not a diagnosis or a record from a real garage. It describes what the customer reports. It does not turn an unexplained noise into a confirmed fault simply because the sentence is saved in software.
I'd resist improving "rattle" into the name of a component before the car has been assessed. A confident-looking guess can send the next conversation down the wrong road. The note should help the person asking questions, not answer those questions on their behalf.
Leave something the next person can use
I'd write the note while the conversation is still fresh, as part of entering that phone booking. Two short sentences can preserve a useful distinction without turning the field into a novel. The car has enough characters already; most of them are under the bonnet.
At arrival, I'd read the saved note before asking the customer to explain the problem again. It provides a starting point for checking that the garage has understood the report. New information still needs its own appropriate record and conversation.
Use the field for relevant job context. There is no need to copy the same name, telephone number and registration into the note when the booking already has separate places for those details. A short explanation is easier to find when it is not buried underneath repeated paperwork.
The field does not diagnose the car, authorise extra work or allocate extra appointment time. Those decisions need their own checks. This feature is a place for the explanation that belongs with the appointment, not an instruction to treat every sentence as an agreed repair.
For that little hatchback, the useful result is modest: the person opening the booking can read what was reported, including when it happens. "Noise" may fit in the diary. The detail is what makes it worth reading.
