A remote assistance request should be checked by contact path, device screen, and data boundary. The reader should know who opened the contact, what the page task is, and what information belongs outside the conversation.
Confirm the contact path
Start with how the contact request began and which page or app entry is involved. For support-style records, the computer and phone entry boundary guide helps define what belongs in the note.
Keep the device screen independent
The device screen should not be treated as a chat instruction. It should match a known Ledger Wallet task or remain separate from the conversation. The screen-confirmation layer is covered in the Secure Element overview.
Set the data boundary before sharing context
The local note can include page title, contact path, device state, and time. It should not include recovery phrase words, PINs, or private setup details. For phrase boundary context, use the PIN and recovery phrase guide.
Pause when the request changes the task
If the contact request asks the reader to move away from the intended page task, pause and return to a known Ledger Wallet route. The final record should state the reason for pausing and the next checked entry.
