A message that mentions a device model, order context, or contact detail should still be handled as a normal entry check. Familiar information can help identify the topic, but it should not replace the known Ledger entry, Ledger Wallet context, and device-screen review.
Known details should be recorded as context
Write down the detail mentioned, the sender path, the requested action, and the time received. Keep the record factual and narrow. The next step is to compare the requested task from a known Ledger entry rather than from the message path alone.
The entry verification checklist helps separate contact path, app state, device state, and local record.
Ledger Wallet state should carry any device task
If the message asks for setup, recovery, update, connection, or approval, open Ledger Wallet from a known path and read the app context first. The app and device screen should describe the same task before the user continues.
- Record only non-secret details from the message.
- Compare the requested task from a known entry.
- Keep recovery phrase and PIN values out of replies and forms.
Device-screen wording remains the practical checkpoint
Device-side action is reviewed on the hardware screen, not in a message thread. The Ledger Wallet download guide is a stable reference when the app path or platform entry needs to be checked again.
Close with a compact comparison record
End with contact path, known detail, Ledger Wallet state, device-screen wording, and final decision. That keeps the article useful without turning familiar details into the basis for action.
