Restraint-system recall scope can vary across production windows; vehicles built outside the published window may still warrant inspection if symptoms are reported. Verbal confirmation that 'this VIN is not affected' should be cross-referenced against any documented symptoms before being accepted as final.
Mobile service appointments produce app-ticket documentation; service center appointments produce app-ticket documentation; both are valid for recall record purposes if the campaign reference is included.
App message threads can be modified or replaced when a ticket is updated. Local screenshots are the only reliable preservation of original message content for direct-service vehicles.
Sister-vehicle considerations apply: where R1T and R1S share architecture, recall campaigns issued for one model can prompt re-inspection or related campaigns for the other. The applicability should be checked at any service visit involving safety components.