Support model
Router first
Customers should identify the issue lane before they create noise in the wrong queue.
AttnomSolutions
Loading page
Bringing in the next surface without the heavy transition shell.
Loading page
Bringing in the next surface without the heavy transition shell.
Funding, KYC, trading, security, and access questions start with the right issue lane, current status, and scam guidance before a ticket is opened.
Support model
Customers should identify the issue lane before they create noise in the wrong queue.
Status linkage
Funding, trading, and KYC issues route through the relevant status and control surfaces instead of one generic inbox.
Case context
Reference IDs, networks, device state, and timestamps are requested up front so support can respond faster.
Good help copy explains response paths, dispute lanes, and scams in the same product language users see everywhere else.
Market access, trust, and service updates in one system.
Support model
Customers should identify the issue lane before they create noise in the wrong queue.
Status linkage
Funding, trading, and KYC issues route through the relevant status and control surfaces instead of one generic inbox.
Case context
Reference IDs, networks, device state, and timestamps are requested up front so support can respond faster.
Fraud controls
Scam education sits beside the router to help spot social-engineering attempts.
Markets, trust signals, and account entry.
Pairs, spreads, and launch coverage.
Verification standards and monitoring.
Account and wallet protections.
Support lanes and anti-scam guidance.
Service updates and incidents.
Trade, wallets, KYC, tax, and support.
Risk, treasury, and review link.
Users should know how help works, what context they need, and when to check status before opening a ticket.
Help signal
Support model
Customers should identify the issue lane before they create noise in the wrong queue.
Help signal
Status linkage
Funding, trading, and KYC issues route through the relevant status and control surfaces instead of one generic inbox.
Help signal
Case context
Reference IDs, networks, device state, and timestamps are requested up front so support can respond faster.
Help signal
Fraud controls
Scam education sits beside the router to help spot social-engineering attempts.
Issue-specific routing, support payloads, and FAQ search sit together so customers can self-sort before pressure escalates.
Decision router
Selected support payload
Recommended route
Use this lane when funds have not reached the account state you expected after the published confirmation window.
Risk reminder
Do not resend funds until the network and destination address have been verified against the original instruction screen.
FAQ 01
How long should a BTC deposit remain pending before I contact support?
FAQ 02
What happens if I fund USDT on an unsupported network?
FAQ 03
Why does my bank transfer show sent but not credited?
Fiat deposit matching, withdrawal delays, failed settlement references, and payout confirmation issues.
MFA reset requests, suspicious login reports, device changes, and account-freeze escalation paths.
Order history questions, deposit routing, withdrawal allowlisting, and chain mismatch education.
Contact path
WalletsDeposits, withdrawals, address confusion, and chain-specific support should inherit wallet context first.
Contact path
ReviewIdentity verification, document review, and deposit gating should route into onboarding context instead of a general ticket.
Contact path
SecurityAccount access, suspicious sessions, MFA resets, and recovery should move through the security module with clear next steps.
Contact path
StatusBefore opening a funding or trading complaint, customers should see whether the issue is already acknowledged as rail health or maintenance.
Scam guardrail
Users need a clear rule set that makes fake support agents easy to detect before a conversation becomes dangerous.
No password requests + no OTP capture + route-owned contact paths
Scam guardrail
Network mismatches and new-address mistakes are better handled by visible education and staged warnings than by apology-heavy support after loss.
Network verification + allowlist cooling + wallet lane guidance
Scam guardrail
A help center that ignores scams creates more confusion and weakens customer account safety.
Scam flags + route-specific warnings + status-aware triage
No Attnom Exchange support agent should ever ask for your password or OTP.
Withdrawal requests to newly added wallets may be delayed for review.
Never trust social-media claims of guaranteed returns, insider tips, or official giveaways.
Always verify the network shown on the deposit and withdrawal confirmation screen.