For automotive vendors
The fix is in the support history.
A support ticket can show the failure, the correction, and how your team knew it worked. Daimon Lab explores whether permitted vendor knowledge could become a useful AI task, dataset, or evaluation. Your team can also bring a task it needs tested.
Put your team's work to use
Implementation notes, support workflows, product QA, and expert demonstrations can explain decisions a finished ticket cannot. A scoped project might use approved material or ask participating experts to create new examples.
Company-created material and customer platform records can carry different rights. We begin with the task and source description, then define permitted use in an agreement.
Test the product you're building
A vendor support assistant might recommend a fix and mark a ticket resolved before anyone checks the affected workflow. An evaluation could test whether it verifies the result, asks for the missing evidence, or hands the issue to a person. A separate custom-data project could focus on expert-created troubleshooting examples.
Can we do both?
Yes. You can explore contributing material, commissioning an evaluation, or both. Each role gets its own scope and terms, including who receives material and how it can be used.
Examples of vendor work a project could focus on
Implementation and onboarding, support and exception handling, product QA, and internal operating processes can each provide a starting question.
Have individual expertise rather than a company source? Explore the Automotive experts page.