Service operations
A repeat visit often starts before the first one.
A follow-up visit may be unavoidable. But an incomplete model reference, vague symptom or undisclosed access constraint are preparation problems that can be addressed earlier.
Separate the causes
Measure returns caused by unavailable parts, missing information, diagnosis requiring confirmation, access problems or a new fault separately.
Prepare what can be prepared
The useful question is not ‘can everything be diagnosed remotely?’ but ‘which reliable information changes preparation?’
- Exact model and variant
- Code and failure context
- Access constraints
- Available repair history
- Documents and tools to consult
Keep measurement honest
Define first-time fix before tracking it: do diagnostic-only calls, ordered parts or separate faults count?
RepairGraph currently publishes no measured repeat-visit reduction result.