Describe the failure, not just the result
Tell the assistant the year, make, model, affected system, and what work was performed. Include the scan tool and the exact wording of the failure message when available. Say whether the issue occurs before the procedure starts, during target recognition, during a drive, or when saving the result.
If you have already checked something, state the result. A useful question separates an observed symptom from an assumption about its cause. Do not share customer names, registration details, or other personal information from a scan report.
Use the code-entry and scan-photo tools
Tap ADAS Error Code to enter the code or codes without writing a whole diagnostic question. You can also use the camera shortcut beside the tip to attach a diagnostic scan photo. Include the vehicle and system details in the chat if the scan does not show them clearly.
An error code is a starting point for investigation—not proof that a particular part needs replacement. The same-looking code can require vehicle-specific interpretation. GlassCal should not turn an unsupported code interpretation into a repair instruction.
Keep current OEM procedures as the source of truth
I-CAR’s OEM Calibration Requirements Search states that access to OEM information is required to perform post-repair calibration and directs users to current vehicle-maker information. Equipment, tooling, and test-drive requirements may also apply.
Use the exact OEM procedure to establish whether calibration is required and how it must be performed. Do not take universal target distances, torque values, drive conditions, or release-to-customer decisions from a generic chat answer. A conversation cannot verify that a calibration succeeded.
