Looking up parts in an auto repair shop is technician time taken away from repairs. You have to enter the VIN in TecDoc, pick the right variant from the list, check that the part really is the right one, then enter the same number in the Inter Cars or LKQ portal, compare prices and delivery times, and then call the customer with the total. When a customer sends a photo with the question "how much will this cost", the answer is often put off until evening because the technician is under the lift. A mistake in the variant means a returned part and downtime on the lift.
The agent receives the VIN and photo from the customer's message or the mechanic's phone. A Claude model with image recognition through the API identifies which assembly is in the photo and what damage is visible, and from the VIN, using the vehicle record in Tekmetric or Shopmonkey or a VIN decoder, confirms the variant, engine and trim. The agent then finds the required part numbers in the TecDoc catalogue, checks prices, stock and delivery times in the connected supplier portals, Inter Cars or LKQ, through an API or a login on your behalf, selects original and alternative options and builds a draft order: for each part the number, supplier, price, lead time and a link to the catalogue entry. The technician reviews the draft on a phone or computer, changes the supplier or option if needed and approves. Only after approval is the order sent to the supplier on your account, and the parts, with your markup, are added to that car's repair order in Tekmetric or Shopmonkey. The agent never spends money on its own and never builds orders without approval. We choose how to integrate the suppliers and the shop software, by API, export or login, after a check. The model runs on the Anthropic API or Amazon Bedrock in an EU region, photos and VINs are not used to train the model, and supplier logins are stored in your environment. The data protection on the workstations that technicians connect from is covered by our IT support for businesses.