Start with the outcome you need
State the issue in one sentence and explain what you want the support team to review. Examples include checking an account-access problem, locating a pending verification, reviewing a deposit status or clarifying a displayed transaction. A precise request helps the team route the case and reduces repeated questions.
Include identifiers, not secrets
Provide the account email, ticket number, transaction hash, network, asset, amount and relevant timestamps. Never include a password, one-time code, recovery phrase or private key. Legitimate support does not need those secrets to review an account or public blockchain record.
Write a short chronological timeline
List what you attempted, what the interface displayed and what happened next. Include dates and time zones. Separate what you personally observed from information supplied by another service. Avoid sending many disconnected messages because they can make a simple timeline difficult to reconstruct.
Attach useful evidence safely
Screenshots should show the relevant status or reference while hiding unrelated personal information. Keep original files and do not alter transaction identifiers. If an attachment contains identity information, use only the secure upload route requested by the verified service rather than ordinary email.
Follow one verified channel
Use contact information published on the official website and keep the ticket reference. Be cautious if someone moves the conversation to a private messaging app, requests remote access or promises a guaranteed result. Verify every new contact independently.
Follow up with new facts
When following up, quote the existing ticket number and add only information that changed: a new confirmation count, provider response or requested document. A clear update is more useful than opening several duplicate requests. Keep a copy of the final response and any action you take.