Appeals and paperwork · 9 min read

Support ticket or compliance email: where should your exchange review reply go?

Published: Editorial policy

Short answer

Reply through the channel that carried the request, and quote the case reference in the subject and the first line. A support ticket is usually a queue handled by front-line staff, while a compliance email may reach the review team or may sit in a mailbox nobody reads. If the notice names a channel, use it. If you need two channels, send the full answer once and use the second only to point to it.

Questions about your case? Message us:

Key takeaways

  • The channel named in the request is the instruction. Use it, and quote the case reference in the subject line and the first sentence of every message.
  • A ticket is a queue that front-line staff triage, while a case reference points to the review file. A new ticket without the reference may not reach the reviewer.
  • When two channels exist, send the full answer once and use the other only for a short pointer that names the date, the channel and the reference.
  • Check that sender addresses and upload pages belong to the platform you use, and never send a seed phrase, key or password through any channel.

Where should a reply to a compliance review go?

It should go back through the channel that carried the request, with the case reference quoted at the top. The notice is your instruction. If it says 'reply to this message', answer that message. If it points to a secure upload page, use the page. If it arrived inside a support ticket or an in-app inbox, answer in that thread. A reply sent somewhere else may be correct in every detail and still fail to reach the person who needs it.

The reason is how platforms organize the work. Front-line support, the compliance team and sometimes an outside vendor that checks documents are often separate groups, each with its own tools. A message reaches the review only if it lands in the place the review team reads or if it carries a reference that lets someone link it. Platforms rarely publish how this works, so the safest course is to follow what the notice says and to add the reference every time.

If the notice names no channel, do not guess. Open one ticket, quote everything the platform has sent you, and ask a single question: which channel receives documents for this review?

How do tickets and case references work behind the scenes?

A support ticket is a conversation in a queue. A first-line agent reads it, tags it and either answers from a template or passes it to another team. A case reference is different: it identifies the review file itself, the record that holds the alert, your documents and the analyst's notes. The ticket may point to the case, but the two are not the same object.

That difference explains a common failure. A customer opens a fresh ticket to ask about the review, and the new ticket goes to the front of a general queue with no link to the case. The agent who answers cannot see the file, so the reply is a template. Quoting the case reference does not guarantee a link, but it gives the agent something to search for and lets the reviewer connect your message to the right file.

How these systems work differs by platform, and you cannot see inside them. What you can see is the pattern of replies. If answers keep ignoring what you wrote, your message is probably reaching a different group from the one that holds the case.

A decision table: which channel for which situation

The table covers the situations customers meet most often. It rests on general practice, not on the rules of any one platform, so where your notice says something different, follow the notice.

In every row the pattern is the same: one channel carries the answer, and the reference travels with it. A second channel appears only when the first one cannot do the job.

Two rows deserve a note. When no channel is named, a single ticket with a single question is enough, and a stream of follow-ups is not. When two instructions disagree, ask the platform to confirm which one applies, and until it answers, keep your own record of what each message said and when it arrived.

Where to send a review reply, by how the request reached you
How the request reached youWhere to replyWhyWhat to add
Inside a support ticket or an in-app messageThe same ticket threadThe reply stays attached to the conversation that holds the requestThe case reference in the first line
By email from an address that invites repliesReply to that emailThe message is routed back to the group that wrote itThe case reference in the subject line
By email that says not to replyThe channel named in the messageThe mailbox is probably not monitoredA ticket question if no channel is named
With a link to a secure upload pageThe upload pageIt is built to receive documentsA short pointer in the ticket with the upload date
With no channel namedOne new ticket asking which channel to useThe platform must tell you where documents goEvery fact the platform has sent you
Two channels that disagreeThe channel in the most recent written noticeThe latest instruction usually replaces the older oneA line asking the platform to confirm

How do you link two channels so nothing is lost?

Sometimes two channels exist at once: a ticket you opened earlier and an email from a compliance address. Treat one of them as the main channel and the other as a signpost. Send the complete answer, with documents, through the main channel only. Then send a short pointer through the other, so that anyone who reads it knows where the real answer is.

A pointer can be written in a minute: 'Reference [number]. My complete answer with the requested documents was sent through [channel] on [date]. Please link this message to the case and confirm that the documents are attached to it.' It carries the reference, the date, the place and one request. It does not repeat the case or the documents.

  • Put the case reference in the subject line and the first sentence of every message, in both channels.
  • Send the documents once, through the channel the notice names, and never as copies in two places.
  • Ask for confirmation that the documents are attached to the case, and save the reply.
  • Keep a simple log with the date, the channel, the reference and the text of every message sent.
  • Save auto-acknowledgements, upload receipts and sent copies as files.

How can you check that a channel is genuine?

Compare the sender address and the upload page with the platform you actually use. Open the platform's website or app yourself, by a route you already trust, and look for the same notice inside your account. Lookalike addresses and pages are a standard scam pattern, and a convincing review email is easy to imitate.

Be particularly careful if a message reached you before you had any contact with the platform, or if it gives you a new address for documents. Do not take contact details from an unsolicited message. A genuine review does not ask for a seed phrase, private keys or passwords, and it does not ask for a fee paid to a personal wallet. If a request does any of these, stop and check it through the official site.

For identity documents, prefer the platform's own secure upload when one is offered. Plain email attachments travel less safely, and an upload page keeps the files in the platform's own system.

A worked example: two channels and a reply that vanished

A customer has an open support ticket from the week the account was restricted. Later an email arrives from a compliance address asking for source of funds papers and quoting a case reference. The customer answers in the ticket, because it is the thread already open, and attaches everything. Weeks pass with no update.

Rereading the email, the customer sees the case reference appears only there, and the ticket never mentioned it. The documents may have gone to a queue that does not connect to the case. The customer writes once in the ticket: 'Reference [number]. On [date] I sent the documents requested in the email of [date] through this ticket. Please confirm that they are attached to the case, or tell me which channel receives them.' A short pointer goes by email to the compliance address as well.

The platform may confirm, may ask for a resend through a named channel, or may stay silent. In each case the customer now holds a dated record that the documents were sent, where, and under which reference.

What should you avoid, and when is outside help useful?

Avoid anything that scatters the case. The habits below do it fastest, and each is easy to drop once you know the cost.

If the replies keep missing the point, if you cannot tell which channel the review team reads, or if the amount at stake is large, a second reader can help. We are an intake and coordination service: we read the platform's messages with you, help you work out where a reply should go and, where it fits, connect you with independent licensed lawyers or technical specialists. We cannot make a platform read or answer a message, no result can be promised, and the first assessment is free.

  • Do not open a new ticket for each question. Add to the existing thread.
  • Do not send the same documents through two channels at once.
  • Do not contact individual employees through social media or personal messages.
  • Do not use an address or number given in a message from someone who contacted you first.
  • Do not paste a seed phrase, private key or password into any message, ticket or form.

Common questions

Should I answer a compliance request by email or through a support ticket?

Use the channel the request came through, or the one the notice names. If it arrived in a ticket, answer in that thread. If it arrived by email that invites replies, answer that email. Quote the case reference either way.

Can I send the same documents through both the ticket and the email?

Usually not. Two copies can split the case into two threads, and the reviewer may not know which version is current. Send the full pack through the channel the notice names, then use the other channel only for a short note saying where it went.

What if the compliance email says not to reply?

Then the mailbox is probably not monitored. Look in the message for the channel it names, such as a ticket or an upload page. If it names none, open one ticket quoting the case reference and ask which channel receives your documents.

How do I know my reply reached the review team?

Ask for confirmation. Keep the auto-acknowledgement, the sent copy and any upload receipt, then ask in the ticket whether the documents are attached to your case reference. A reply that names the case and the date of receipt is the clearest proof you can get.

How we can help

Keep reading

Information on this page is general and not legal advice.

Tell us what happened

Free assessment. Written answer. No fee before we say whether we can help.

Start your case

CryptoFreezeDesk is an intake and coordination service. It is not a law firm, a bank or an exchange. Legal work is done by independent licensed lawyers and technical work by independent specialists. We may receive a referral fee from them, and we tell you before you commit. We never guarantee a result. How we work and who pays whom

Free case assessmentMessage us. We reply in writing.