Helpdesk software for crypto exchanges and wallets

Why do generic helpdesks struggle with crypto exchange support?

A generic helpdesk assumes the sender is the customer and the answer sits in your own records. At an exchange, the sender may be an attacker, the answer may be on a blockchain, and some answers can't be given at all.

• Identity is the product. Mail from the address on file proves little after phishing or a SIM swap, so reps need recent security activity in view before they reply.
• Tickets carry chain data. Hashes, networks, memos and addresses belong in searchable fields, not retyped into explorers all day.
• Some cases are restricted. Compliance holds and enhanced due diligence requests need their own owners and wording.
• Fraud fills the hardest queue. The CFPB's analysis of more than 8,300 virtual currency complaints found fraud and scams the most common issue, followed by transaction problems, and noted that scammers pose as customer service where platforms are hard to reach.
• The market never closes. Prices move at 3 a.m. on a Sunday, and so does your queue.
• Complaints have rules. MiCA Article 71 requires EU crypto-asset service providers to handle complaints promptly, fairly and free of charge and to record each one. In the UK, the FCA's cryptoasset regime applies its full scope of regulated cryptoasset activities from 25 October 2027, and the Consumer Duty applies to cryptoasset firms.

How should a crypto exchange set up its support inbox?

Build queues around risk and ownership, and give each its own SLA.

Suggested starting targets. Adjust to your policies and any regulatory deadlines that apply to you.

Routing rules

• "Hacked", "unauthorized", "didn't make this withdrawal" or "new phone" go to Account security as urgent, and a workflow posts each one to the security team's Slack channel.
• "Pay a fee to withdraw", "tax to release" or "recovery service" go to Scams and fraud.
• "Complaint", "regulator", "ombudsman" or "lawyer" go to Formal complaints.
• Verification tier, jurisdiction and trading tier work as custom fields, filters and columns, and Growth and Scale add round-robin inside each queue.

Side conversations let a rep ask wallet ops in Slack without leaving the ticket.

What should crypto support reps say in the hardest conversations?

Say what you are doing, what the customer should do now and what you will never ask for. Adapt these five macros; placeholders are in braces.

Account takeover reported

Hi {first_name}, thank you for telling us straight away. We've locked your account, so no withdrawals or changes can go through while we investigate. Please change your email password now, and move to an authenticator app if you use SMS codes. Our security team will contact you from {official_email} within {time}. Our staff will never ask for your recovery phrase, password or 2FA codes, on any channel.

Withdrawal under review

Hi {first_name}, your {asset} withdrawal from {date} is being reviewed, and the funds stay held in your account meanwhile. We'll email you when the review is complete or if we need anything. We can't share details of reviews, and we appreciate your patience.

Deposit sent on the wrong network

Hi {first_name}, thanks for the transaction hash. Your {asset} was sent on {network}, which this deposit address doesn't support, so it wasn't credited automatically. {If recoverable: We can attempt a recovery. It takes {time} and costs {fee}, taken from the amount recovered. Reply "yes" to start.} {If not: We can't access funds sent on this network, so we're unable to recover them.} Next time, check the network on the sending platform matches the one on your deposit screen.

Customer being scammed

Hi {first_name}, please pause before sending anything else. Platforms that demand a fee or tax before you can withdraw profits follow a well-known scam pattern, and paying them doesn't release the money. Please don't send more crypto to {platform_or_address}. We can't reverse transfers that have left your account, but we've recorded your report and our team will be in touch. In the US you can also report it to the FBI at ic3.gov.

Formal complaint acknowledgment

Hi {first_name}, we've logged your complaint under reference {ref}, and {owner_name} from our complaints team now owns it. We aim to send a full response by {date} and will update you sooner if anything changes. {Where required: If you're unhappy with our final response, you can refer it to {regulator_or_ombudsman}.}

How should a crypto support team be staffed for 24/7 markets?

Cover security and scams around the clock, and keep a surge plan for the days prices, networks or tax deadlines move.

Structure

• Tier 1 generalists across time zones and languages for status, fees and how-to questions.
• Specialist pods for account security, payments (with a direct line to wallet ops) and verification.
• Compliance and complaints owning their queues. Reviewers who only comment or approve use free Lite seats: 20 on Growth, 50 on Scale.

Peaks to plan for

• Volatility. A sharp price move brings sign-ups, verification backlogs and delayed-withdrawal questions in the same hour.
• Network events. Congestion, upgrades or paused deposits on one chain create waves of identical tickets. Post a status banner, then answer.
• Listings, delistings and airdrops. Publish details and deadlines before the announcement.
• Tax season. US brokers now report digital asset sales on Form 1099-DA: gross proceeds for 2025, with cost basis added for covered assets acquired from 2026. Expect early-year questions about missing basis and figures that don't match customer records.
• Your own incidents. Pre-write the outage message and name one person to keep it current.

Where does AI help a crypto support team?

At an exchange, the slow work is retyping hashes, rereading 40-message security threads at shift change and replying to the same stuck-withdrawal question in six languages. That work goes to AI. Lock decisions, compliance holds and complaints stay with people.

• Copilot drafts replies that cite their sources, so a rep can confirm a fee or hold period came from the current policy before sending. Copilot is an add-on at $29 per rep a month billed annually, and every plan includes 10 Copilot conversations per rep a month. Teams using it on every conversation see a 2.4× faster median reply, by Aftersales' own measure.
• Summaries turn a long security thread into a handover note for the next shift or for compliance.
• Translation in 31 languages, including right-to-left scripts, lets one team serve customers worldwide.
• Monitors in Insights check each reply your security and payments reps send for a request for a recovery phrase or a missing escalation, so a QA lead can coach on the exact ticket. Helio Energy's quality scores rose 14 points after Monitors replaced sampling.
• Agent takes the routine share (deposit and withdrawal status, fees, verification status) and passes the rest to this inbox. The conversation map and an example procedure are on AI customer service for crypto exchanges.

Which metrics should crypto exchange support teams track?

Measure speed where safety depends on it and resolution where cost does. Split every metric by queue.

If you hold a New York license, the Department of Financial Services asks for a quarterly count of customer service requests and complaints by channel and topic, with average time to resolution. Tag by topic from day one and that report becomes an export.

How do crypto exchanges switch helpdesk software?

Many crypto teams run support on a general-purpose helpdesk such as Zendesk, Intercom, Freshdesk or Salesforce Service Cloud, with complaints in a spreadsheet and AML cases in a separate tool. You can add AI without moving, or move the inbox in stages.

Option 1: keep your helpdesk

Keep your current helpdesk and add Agent inside it for the routine status questions; pricing for Agent on its own is on the pricing page.

Option 2: move to Aftersales Inbox

1. Export open and recent tickets, macros and help center articles.
2. Map custom fields: verification tier, jurisdiction, asset, network and transaction hash.
3. Rebuild queues and SLAs from the table above and connect Slack.
4. Bring macros across, rewriting any that promise timings you can't control.
5. Run both systems side by side until you trust the new queues, then move channels one at a time, starting with email.

Most teams finish migration in an afternoon; we run the migration with you on Growth and Scale. Keep your AML case tool as the system of record and reference its case IDs on the ticket. Scale ($109 per seat a month, billed annually) adds SSO and a multi-brand help center for exchanges with a separate wallet brand. See pricing or our fintech customer service software roundup.

Frequently asked questions