AI Customer Communication for Repair Shops

Vehicle repair notes may contain abbreviations, test results, and component names that are unfamiliar to customers. A language model can draft an explanation, summarize a digital inspection, translate a routine update, or prepare a message about timing. It should not invent a diagnosis, turn a possibility into a confirmed failure, or promise that a repair will solve a problem beyond the available evidence. Keep the technician’s finding, recommendation, and uncertainty distinct. Before sending, compare the draft with the repair order, estimate, and inspection evidence. A message about added work should state what changed and what the shop needs from the customer. FTC consumer guidance recommends obtaining a written estimate and understanding charges; state requirements can vary, so shops should follow their applicable procedures. AI should not infer customer approval from silence, a read receipt, or a previous unrelated authorization. A person with authority should review scope changes, price, and safety-sensitive advice. Protect customer names, phone numbers, VINs, payment records, and photos. Use approved systems with clear retention and access settings, and send only information needed for service. Offer a person-to-person path for disputes, breakdowns, or questions that the assistant cannot answer. Measure whether messages reduce repeated calls while preserving accuracy, authorization, and customer understanding. Communication quality is not the same as repair quality; confirm the actual work and vehicle state separately.