Contact us
How to reach support and what each channel is for
SynqoraX AEON keeps its support structure simple on purpose, so that a trader who needs help does not have to guess which door to knock on. The workspace is designed to be used without friction, and the same principle applies to getting assistance when something is unclear or when a request falls outside the usual self-service flow. Rather than scattering contact options across the site, the platform routes enquiries through a small number of clearly labelled channels, each suited to a different kind of question.
General enquiries about the workspace, its features, or how a particular strategy behaves are best directed to customer service, which handles the bulk of day-to-day questions. Account-specific matters, including verification steps or anything tied to your funding and balance, are typically handled together with your account manager once your account has reached that stage of onboarding. This separation exists so that routine questions do not get delayed behind account-specific ones, and so that sensitive account details are only ever discussed through the appropriate channel.
The help centre sits alongside these channels as a reference point rather than a queue. It is where explanations of core features, common configuration questions, and walkthroughs of the onboarding steps are kept up to date, so that a trader can often find an answer without waiting for a reply at all. Checking there first is not a formality; it genuinely resolves a large share of questions before they need to become a support request. The specific addresses, forms, and hours for each of these channels are listed elsewhere on this page, and are kept current independently of this text.
What to include so a request is handled in one pass
A support request is only as fast as the information it carries. The single most common reason a reply takes longer than expected is that the first message did not include enough detail for the person reading it to act immediately, which means a second message has to go out asking for the missing piece before any real progress can be made. Taking a few extra minutes before you send a request usually saves far more time overall than it costs.
Start by stating plainly what you are trying to do and what happened instead. If you were setting a risk limit and the interface behaved unexpectedly, say what limit you were setting and what you saw on screen, rather than describing the general area of the workspace. If the question concerns a specific strategy, name the strategy and the market it was running on, since spot and futures configurations differ in ways that matter to whoever is reading your message.
Where relevant, include the approximate time the issue occurred, since this makes it far easier to match your message against activity on the account. If you have already tried something to resolve it yourself, mention what that was, so the same step is not suggested back to you. Screenshots are useful when the issue is visual, but they are a supplement to a clear written description, not a replacement for one. Avoid sending several short, disconnected messages about the same issue, since consolidating everything into a single, complete request keeps the whole exchange easier to follow for both sides.
What happens after you write and what to expect
Once a request reaches customer service or your account manager, it is read, categorised, and directed to whoever is best placed to answer it. Straightforward questions about how a feature works are often resolved directly by the person who first reads the message. Anything that touches your specific account or funding is handled with more care, since it may require a short verification step before details can be discussed, which is a safeguard rather than an obstacle.
Support hours and typical response windows are published separately from this text and are kept current there rather than restated here, since operational details of that kind change independently of the page around them. What stays constant is the approach: a request is not considered closed until the question that was actually asked has been answered, not simply acknowledged. If a fix or a change requires input from another part of the team, you will be told that this is happening rather than left without any update.
It is worth remembering that support can explain how the workspace behaves and help resolve account or technical issues, but it does not provide investment advice, and no message from the team should be read as a recommendation about what to trade or when. Trading digital assets carries substantial risk, including the total loss of capital, and nothing on this website or in any support exchange is investment advice. If a reply does not fully answer your question, saying so plainly is the fastest way to get it addressed, since silence is read as resolution while a follow-up message is read as exactly what it is.