SOLUTIONS · AUTOMOTIVE · QUALITY AND SAFETY
File every vehicle complaint and warranty claim under the right system and component
A quality team finds a trend by counting: how many complaints this month mention a brake pedal going soft on one model, against last month. The counting only works when every complaint, claim and call is filed under the same component codes, and the text rarely makes that easy. Drivers write "the car jerks when I pull away", technicians write "replaced TCM per TSB", and call-center notes are shorter still. StayCharted learns your coding from the cases your engineers have already filed, codes each new one with a confidence, and sends the unsure ones to an engineer, so engineers can build consistent trend reports sooner.
- Your component codes, learned from cases your engineers already filed.
- A confidence on every case. Route uncertain answers to an engineer and sample confident answers too.
- Tested before you rely on it, on cases it never saw, category by category.
Where it fits
- Consumer complaints and owner feedback: from your website, app, social channels or a regulator's public data.
- Warranty claim narratives: the technician's complaint, cause and correction, coded to your failure modes.
- Call-center and roadside notes: short notes filed by system before they're lost in free text.
- Supplier quality: returned-part reports and 8D narratives filed under your defect codes.
- Parts and damage photos: with Vision, photos of returned parts or damage can be classified the same way. See the car damage photo benchmark.
How it works
- Export cases your engineers have already coded, with the text and the code. Leave out names, addresses, phone numbers and VINs; StayCharted also masks email addresses, phone numbers and card numbers before training.
- Train and read the report: accuracy per system and component, and which ones it confuses.
- Code new cases by filling a file each day or week, or through the API from your quality system. Every case gets a code, a confidence and a review flag.
- Engineers review the unsure ones in the Review Queue, and their answers train the next version.
Test on a representative sample from a new dealer or market before relying on automatic routing. Review a sample of confident answers as well as the cases below your cutoff.
What StayCharted doesn't do
It files cases. It doesn't decide whether something is a defect, a safety issue or a reportable trend, and it doesn't replace your engineers' investigation. It helps organize the cases engineers investigate; classification errors and missing source records can still affect the counts.
Common questions
Can it use our own failure codes rather than NHTSA's?
Yes. Train on cases your engineers have coded using your own system, component or failure categories.
How much history do we need?
A few dozen coded cases per component is a start; look-alike components need more. The report shows where.
Does it read other languages?
Use a multilingual AI model and representative labeled cases. Check performance for each language and market, including European languages or Arabic, before relying on its answers.
Can the data stay in our cloud?
On Business, models can be trained in your own Amazon Bedrock or Microsoft Foundry account. The cases you classify are still sent to StayCharted, under our DPA.
Which plans?
Essentials and Business include the API and the Review Queue.
Put it into practice
Normalize dealer op codes and repair-order lines →