How to reach a real person when swap support only sends auto-replies

05 September 2026

You almost certainly cannot reach a real person. The support system is designed to prevent it, and the auto-replies are a deliberate barrier, not a broken process.

The reason is straightforward: many swap sites operate with minimal staff, often one or two people, or none at all. The "support team" is a script that matches keywords in your message to pre-written responses. If the script cannot match your problem, it sends a generic reply that looks like a person typed it but was generated by a template. Reaching a human requires bypassing that script, and the site has no incentive to let you do that.

What the auto-reply system actually does

Every message you send goes through a triage engine. Common phrases like "transaction failed" or "refund" trigger canned answers. Less common phrases like "contract address mismatch" or "memo missing" also trigger canned answers, just different ones. The script never escalates. If your problem fits no template, the system sends a variation of "we will look into this" and stops. No human ever reads it.

Why the barrier exists

A real support conversation costs time. If every user who sent funds to the wrong network could talk to a person, the site would need dozens of staff. Instead, the site relies on the fact that most problems are self-correcting: a stuck transaction eventually clears, or the user gives up and moves on. The few problems that genuinely require human intervention - like a lost memo or a frozen swap - are expensive for the site. The auto-reply system is the cheapest filter.

The only methods that sometimes work

• Use the exact words from the site's FAQ. Copy a full sentence from a help article that describes your problem. The script recognises its own language. Paste it as your message. This may trigger a different branch of the script that actually updates your swap status, because that branch is designed to handle common issues automatically.

• Send the same message repeatedly, hours apart. Some scripts log your first attempt and ignore duplicates. Others reset after a set period, usually 12 to 24 hours. Sending the same message after a full day can cause the system to treat it as a new issue, which may advance it to the next tier of the script.

• Use a different email or account. If the site ties your support ticket to your swap ID, creating a new support request from a fresh account with a different email address sometimes bypasses the old ticket's dead end. The script treats you as a new user and runs its full sequence again.

• Mention a regulator or law enforcement agency by name. This is not a threat; it is a pattern that some scripts flag for manual review. The script sees "reporting to [agency name]" and may put your ticket in a queue that a human eventually looks at, if only to close it. Do not bluff. If you intend to report, actually do it. But the possibility that a human will see the ticket is real.

What almost never works

• Demanding to speak to a manager. The script has no manager.
• Using angry or emotional language. The script filters for keywords and emotion is not one of them.
• Asking for a phone number or live chat. The site does not offer either.
• Threatening a chargeback. The script does not process refunds. The human who might see that message later will probably ignore it.

When to stop trying

If you have sent three messages over three days with no change in the auto-reply, you have exhausted the script. No human will appear. Your next step is to accept the loss or, if the amount is large enough to justify legal action, to contact a lawyer who handles cryptocurrency disputes. That is not support; that is litigation.

None of this replaces the checks you should have made before sending. If you are reading this page because something already went wrong, the page titled "How to test a swap address with a tiny amount first" covers the step that would have prevented your current problem. Read it before your next swap.

Back to card purchases