A Ledger contact entry check should separate service context from device-side action. Contact wording can explain where to continue, but the user should still return to a known entry, compare Ledger Wallet context, and read the device screen before any device task is completed.
Support path should be verified before conversation details
Start with the path used to reach support or service information. Record the page path, app version, device model, and the task described. Do not let a phone call, chat, or message become the action path if it does not match the known Ledger entry.
The entry verification checklist helps keep source path, app state, device screen, and local record in separate lines.
Device tasks still belong on the device screen
If the conversation refers to an update, setup, or recovery task, compare the message with Ledger Wallet and the device screen. A contact path should never require recovery phrase words, PIN values, or secret backup details. Keep those outside all support records.
- Record the contact entry path before responding.
- Compare contact wording with Ledger Wallet context.
- Do not read or type secret backup details into a conversation.
Safe records should stay factual and limited
A safe record can include date, source path, device model, app state, and final decision. It should not contain private backup content. The Ledger Wallet download guide is useful when the app entry itself needs to be rechecked before continuing.
Repeat the same check if the contact path changes
If a new contact page or message appears later, start from the same known entry and compare again. That keeps the security note operational and brand-protective: the focus stays on entry, screen, and records rather than suspicion or pressure.
