A person, not a macro
Answers come from someone who can open Robinscan, read the block around your trade and quote the rule that fired.
One form, one desk, no queue. Tell us which part of the engine you are looking at and the answer comes back with the block, the route and the rule behind it.
Answers come from someone who can open Robinscan, read the block around your trade and quote the rule that fired.
Passes and payments are handled first because they block you. Bug reports get a reference you can follow up on.
The form creates nothing. It carries your message, the topic and the email you want the answer sent to.
Copy questions are answered on chain, not from memory. These three steps are the difference between one reply and a week of back and forth.
The panel writes the rule behind every skipped candidate. Nine times out of ten the answer is already there, and quoting the line makes the reply instant.
Leader address, transaction hash, the minute in UTC and what you expected. Anything less turns one reply into three.
Every submission returns a PCT reference. Quoting it in a follow-up email pulls the whole thread up without repeating yourself.
Pons Copy Trading writes from hello@ponscopytrading.com and nowhere else. Anything else claiming to be support is an impersonation, and forwarding it here helps the next person.
Fastest route. Your panel already carries the wallet, the leaders, the settings and the decision log, so nothing has to be explained twice.
Best for anything with attachments: transaction hashes, exports, screenshots of a copy that failed.
A live support bot that answers passes, wallets, sizing, exits and copy questions on the spot, and hands you to a person when the answer is not in its list.
Routed to the person who handles that area rather than a shared inbox nobody owns.
Anything blocking a live position is picked up first and the rest follows in order. We do not publish a response time we cannot hold in every timezone, so treat the dashboard as the fast lane and this form as the thorough one.
The leader address, the transaction hash of their trade and the minute in UTC. With those three the blocks can be read directly and we can tell you which rule stopped the copy, or whether the trade was never detectable in the first place.
The index counts from the moment it starts, drops addresses whose code shows they are contracts, and only sees trades that moved tokens through a pool. A wallet that has been quiet during the current window simply has nothing to show yet.
No. Transfers on Robinhood Chain are final and no operator can reverse them. What we can do is show you the exact path of the transaction on Robinscan so you know what happened.
Access is a flat payment for a period and it starts the moment it activates. If something on our side stopped the engine from doing its job during that period, write in and we will make it right.
Everything official comes from hello@ponscopytrading.com or from inside your own dashboard. We do not run support accounts on other platforms, so anything else claiming to be us is an impersonation, and forwarding it here helps other people.
Yes, and they are the most useful mail we get. Pick the bug report or partnership topic, describe the workflow you want rather than the button you imagine, and it reaches the engine roadmap.