A delayed withdrawal creates pressure to resend funds or trust an unofficial “recovery” contact. A disciplined escalation distinguishes platform processing from on-chain settlement and preserves the evidence support needs. The workflow applies to a hosted exchange, a wallet provider, or a payment service. It does not promise recovery and never requires a seed phrase or private key.
Classify the current state
Record whether the withdrawal is draft, risk review, queued, broadcast, confirmed, failed, or credited. The platform’s status and an explorer status answer different questions. Save asset, amount, network, destination, fee, request time, and transaction hash if one exists. Do not send again while the first request is unresolved unless official support confirms the state.
Verify the destination independently
Compare the withdrawal address and network with the recipient’s original deposit record. Check memo or tag requirements and the exact account entity. If the destination page has changed, preserve both versions. A successful blockchain transaction to a wrong address is not a platform delay; it is a separate incident requiring the recipient or network-specific support.
Use the authenticated support path
Open a ticket from the logged-in help center or published support domain. Include the request id, hash, asset, network, amount, timestamps with timezone, and screenshots redacted for personal data. Ask a precise question: “Has this request been broadcast, and what state is the destination?” Avoid long emotional explanations that bury the technical facts.
Reject social-engineering offers
Fraudsters may copy a support logo and ask for a “verification fee,” remote access, one-time code, seed phrase, or transfer to a recovery wallet. The official ticket should remain the source of truth. Never follow a new link received in a private message to unlock a withdrawal. If the account email or session is compromised, secure the account from a clean device before continuing.
Track responses and clocks
Keep ticket number, agent response, promised review time, and next follow-up date. A platform maintenance notice can explain a queue but not prove a specific account is affected. If support asks for identity documents, use the secure upload area and record what was provided. Escalate through the published complaint route when the stated timeline passes, without opening duplicate tickets that make reconciliation harder.
Check on-chain evidence
If a hash exists, inspect the correct network and destination address using a trusted explorer. Confirm amount, confirmations, and whether an exchange credit requires additional internal processing. If no hash exists, the platform may not have broadcast the withdrawal. Save the explorer URL and block time, but do not treat it as proof of account ownership or a guarantee of finality.
Close or document the case
When credited or formally rejected, save the final response and update the ledger. If unresolved, keep the case open with an evidence index and a next review date. A complete case note helps a family, accountant, or regulator understand what happened without exposing credentials. Never claim that a support ticket alone proves wrongdoing or guarantees reimbursement.
Worked example: no transaction hash
A withdrawal request remains “processing” for hours and no hash appears. That usually means the platform has not broadcast it, although only the provider can confirm the internal state. Record request id, asset, network, amount, destination, and status-page evidence, then open one authenticated ticket. A social account asking for a release fee is unrelated evidence. If a hash later appears, append it and inspect the correct network; do not close the case until the destination credit is separately confirmed.
Operational handoff
If the platform requests an identity document, use its secure upload form and record only the document type and submission time in the case note. Redact unrelated balances and addresses. A status page may show a broad incident while an account has an additional risk review; ask support to identify which state applies without requesting confidential internal details. Keep one owner for the ticket and one next-action date so multiple family members do not send conflicting instructions.
Frequently asked question
What should I do if someone offers instant recovery?
Stop contact, preserve the messages, and use the platform’s official support and security pages. Legitimate staff do not need a seed phrase, private key, or payment to a personal wallet to inspect a withdrawal.