1. Start with the transaction hash
The transaction hash is the first fork in the investigation. If the exchange has broadcast a transaction, you can compare explorer confirmations, destination address, network choice, fee level, and timestamp. If no hash exists, do not invent one in a support ticket — say clearly that the withdrawal is still pending inside the venue.
2. Separate chain delay from venue delay
Chain congestion, finality requirements, and network-specific confirmations are different from an exchange wallet queue. Treat “pending”, “processing”, “awaiting approval”, and “wallet maintenance” as different states. Keep the amount small until the route is proven.
3. Read maintenance language carefully
Wallet maintenance can be routine node work, a chain incident, liquidity management, or a venue-side pause. The safer response is the same: stop adding exposure, preserve evidence, and wait for a successful small withdrawal before scaling activity.
4. Prepare a ticket-ready evidence pack
Support requests move faster when they contain the asset, network, amount, destination address, memo or tag if used, timestamp with timezone, transaction hash if available, and the exact status shown in the account. Never send seed phrases, private keys, passwords, or 2FA codes.