Collision News | General

Search Autoparts/Abrn/Collision-news-general/

Mitchell Providing Collision Repair Industry Instant Access to Real-Time VIN-Specific Recall Data

Tuesday, October 31, 2017 - 07:00
Print Article

Mitchell, a leading provider of technology, connectivity and information solutions to the Property & Casualty (P&C) claims and Collision Repair industries, has now integrated VIN Specific Recall Notices into its estimating solutions providing real-time recall data directly from the manufacturer when the VIN is decoded.
Debbie Day, Executive Vice President and General Manager, Auto Physical Damage for Mitchell says, “It is estimated that tens of millions of vehicles on the road today currently have open recalls and there are many reasons why vehicle owners might not be aware that the vehicle they are driving has a safety system recall. As part of our commitment to proper and safe repairs within the automotive collision repair and claims industries, we are working closely with original equipment manufacturers (OEMs) to give their customers and their repair facilities access to these and other important recall notifications.”
To better enable its recall data to reach the collision industry market, Mazda is the first OEM to provide Mitchell access to its recall data, giving collision repair users of Mitchell Estimating/UltraMate estimating solutions instant notification of an open Mazda recall when the VIN is decoded.
“As our vehicles age, many owners turn to independent repair and body shop facilities to have service work performed,” said Rob Milne, Director, Takata Action Team, Mazda North American Operations. “Our partnership with Mitchell enables us to increase the opportunity to inform Mazda owners that their vehicle is affected by an open safety recall.”

Mitchell is currently in discussions with other OEMs to make sure this important safety data gets out to the market in a smart and efficient manner – every time a vehicle goes in for a repair.

Article Categorization
Article Details
< Previous
Next >
blog comments powered by Disqus