Testing Customer Support at Exchanges

Support quality is invisible until something goes wrong, which is when it determines the outcome. We test it deliberately.

The method

We open a ticket with a specific, answerable technical question that requires someone to look at an account rather than send a template.

Something like: why does a particular deposit require a different number of confirmations than another asset on the same network, or what the exact withdrawal minimum is for a specific asset on a specific network and why it changed.

Then we record the response time and whether the answer addresses the question.

What we are looking for

A response from someone who read the question. A template reply to a specific question indicates a support function that will not help when something is actually wrong.

Accuracy. We verify the answer independently.

Escalation behaviour. Whether a question beyond the first tier reaches someone who can answer it.

Channel. Whether support is a ticket system authenticated by your account, or a chat with someone who may or may not be who they claim.

That last one matters beyond convenience. A ticket raised from inside your account is authenticated by the account itself, which means the agent already knows who you are and has no reason to ask you to prove anything.

The security dimension

The moment any support interaction moves toward seeing your screen, or toward you revealing a recovery phrase, it has stopped being support.

Real support asks for a transaction hash, which is public. Nothing else about your holdings is needed to resolve a transaction question.

Venues where support is a ticket system rather than a direct message, such as a platform we ran a full withdrawal through, remove an entire category of impersonation risk, because there is no channel through which a stranger can approach you claiming to be staff.

What we found

Response times varied from hours to over a week. Accuracy varied more.

The strongest correlation was with regulatory status. Venues operating under a framework with complaints-handling obligations answered specific questions accurately and within a stated timeframe, which is what those obligations require.

Why this is in our reviews

Because everything else we test happens when things work.

Support is the only thing we can assess that tells you anything about what happens when they do not, and it is the part of a platform that most users never evaluate until they need it.