Product updates
Follow the latest SynaNoteAI features and improvements available to automotive service teams.
Follow the latest SynaNoteAI features and improvements available to automotive service teams.
DTC Analysis
DTC Analysis now accepts both 16- and 17-character VINs. If an older VIN cannot be decoded automatically, the assistant confirms it with you and guides you through the missing vehicle details before generating the report.
Many older vehicles use 16-character VINs that modern vehicle databases may not fully recognize. DTC Analysis now keeps the diagnostic workflow moving instead of rejecting the VIN or forcing you to start over.
You no longer receive an error simply because a vehicle has a legitimate 16-character VIN. The assistant preserves the chat, records your confirmation, and collects only the vehicle information that is still missing before preparing the DTC analysis.
This update improves vehicle identification for older cars while preserving the existing 17-character VIN workflow for modern vehicles.
Open DTC Analysis, enter the VIN, and follow the assistant prompts. The Help button remains available beside the composer whenever you need guidance.
Job Story Builder
Job Story Builder now includes five more OEM checklist options. Select the completed step once, and the tool adds a clear statement in the correct part of the repair story.
Final relearn and adaptation steps are important, but they can be easy to leave out of a repair story. Job Story Builder now gives you more one-click OEM Compliance options, so completed work can be recorded clearly without rewriting the same sentence every time.
Five new checklist options are available:
The full OEM Compliance checklist is also arranged alphabetically, making the right option faster to find.
1. Open Job Settings in Job Story Builder.
2. Select only the OEM operations that were actually completed.
3. Add your technician notes or supporting document and generate the story.
For each selected new option, Job Story Builder adds a clear, separate sentence to the Reassembly / Service Operations part of the narrative. Options that are not selected are not added.
Technicians should not have to repeatedly type common relearn and adaptation statements. The expanded checklist saves time, helps prevent completed OEM steps from being missed, and keeps the final story consistent and easy to review.
The checklist does not assume that an operation was performed. You stay in control by selecting only the work you completed, and Job Story Builder places that information in the right part of the final narrative.
Recall Builder
Recall Builder now guides mileage and document intake, follows the active repair branch, enforces required completion facts, and returns the final narrative in one focused chat.
Recall procedures can include multiple inspection outcomes, repair paths, and conditional operations. Recall Builder now turns that process into one guided conversation while keeping the complete official document as its source of truth.
The chat opens with a clear request for mileage in, mileage out, and the official recall source. Paste the recall text or attach a supported PDF or DOCX document. Analysis begins only after the required intake and source are provided.
Reply with confirmed findings, operations, measurements, software information, label application, and corrections. Each answer is evaluated against the original recall document and the established conversation. When the applicable path is complete, Recall Builder returns the final narrative directly in the chat.
Use New Recall to clear the in-memory conversation and begin again with a different document.
Open Recall Builder or read the Recall Builder guide for step-by-step instructions.
Narrative Polish
Narrative Polish now carries the latest polished narrative forward, applies corrections without losing established facts, separates unrelated repair cases more reliably, and adds faster help, history, new-conversation, and copy controls.
Technician stories rarely arrive in one perfect message. Diagnostics develop, measurements are added, corrections happen, and the final repair needs to read as one accurate narrative. Narrative Polish now treats that full story as the source of truth throughout the conversation.
A new relationship gate decides whether the latest note belongs to the active case before any content is merged. Independent concerns—such as an overnight battery draw added during an overheating conversation—are kept separate, even when they involve the same vehicle. Related diagnostic, repair, and verification steps remain together.
The refreshed compose area now includes:
Open Narrative Polish to build a complete service story, or read the Narrative Polish guide for the full workflow.