“It clicks at the front left, but only sometimes” is an honest customer description. The workshop still lacks context, vehicle details and timing. A good digital intake collects those parts before somebody has to call back.
What a customer can provide easily
- A photo of the warning light or visible area.
- A short voice note describing the sound and timing.
- Registration or vehicle model.
- Driveability, warning message and preferred appointment.
AI can read visible text, summarise audio and ask for a missing field. It should not claim that a brake fault or engine failure has been diagnosed. The garage receives structured pre-information, not a verdict.
| Output | Benefit | Boundary |
|---|---|---|
| Short summary | faster triage | keep original |
| Recognised warning | better follow-up | no safety clearance |
| Urgency flag | prioritisation | human confirms |
| Part suggestion | internal at most | not a quote |
Keep the original beside the summary
Summaries lose nuance. Preserve photo, audio and customer wording alongside the generated card, with consent and a clear retention period. Personal information accidentally visible in an image should not spread into systems that do not need it.
Our garage AI workflow combines structured intake and callback. Immediate danger also needs a conservative emergency boundary.
Sources
FAQ
Can AI diagnose vehicle damage from a photo?
It can organise clues but cannot replace inspection by a qualified professional.
Should the original be retained?
It should remain available for verification, with limited access and retention.
Why use a voice note?
Customers often describe sounds, timing and behaviour more naturally than in a form.
Can it quote a price?
Only for tightly defined standard services; a damage suggestion is not a reliable quote.