Contact us

SynqoraX AEON is built so that most day-to-day questions can be resolved directly inside the workspace, through the help centre and the resources linked from your account. When a question needs a person rather than an article, this page explains how contact support reaches the right team and what to expect once you have written in.

How to reach support and what each channel is for

Different questions call for different channels, and SynqoraX AEON separates them so that each one moves faster. The help centre is the first stop for anything you can usually solve yourself: how a strategy is configured, how risk limits behave, how funding and withdrawals work, and how alerts are set up. It is written to be searched rather than read from top to bottom, so start there if your question is about how something works rather than something going wrong.

For issues tied to your specific account, such as a stuck order, a verification step, or a balance that does not match what you expect, customer service is the right channel. This is a person-to-person line rather than a knowledge base, and it exists precisely for the cases where the general documentation does not cover your situation. Keep this channel for account-specific problems so it stays responsive for the people who need it.

During onboarding, and at points afterward when your setup changes meaningfully, you may also be in contact with an account manager. This is the same verification and setup step described elsewhere on the site, extended into an ongoing point of contact for traders whose needs go beyond the self-serve flow. An account manager does not replace customer service; it exists alongside it for the parts of the relationship that benefit from continuity with one contact rather than a new person each time.

The exact addresses, forms and numbers for each of these channels sit on this page directly, next to the labels above. Use the one that matches your situation rather than sending the same message to more than one channel, since that only slows down whichever team ends up handling it.

What to include so a request is handled in one pass

The single biggest factor in how quickly a request gets resolved is how complete it is the first time. A message that says something is not working, with no further detail, almost always triggers a reply asking for the details that could have been included at the start. Building those details into your first message removes a full round trip.

Start with the account email you use to sign in, since that is how any request gets matched to your workspace. Describe what you were trying to do, what you expected to happen, and what happened instead, in that order, since this sequence is usually the fastest way to explain a problem clearly even to yourself. If the issue involves a specific order, position or transaction, include its identifier or the approximate time it occurred, since searching a whole account history for one event takes far longer than checking a single reference.

Where the issue is visual, such as a display that looks wrong or a setting that will not save, a screenshot removes a lot of back-and-forth that text alone cannot. Note the device and browser you were using as well, since some issues are specific to one combination and not others. Finally, mention anything you already tried, such as refreshing, logging out and back in, or checking a different device, so the reply does not simply repeat steps you have already ruled out.

None of this needs to be formal. A short, structured message with these elements will move through customer service faster than a longer one without them, because it gives the person reading it everything needed to act rather than everything needed to ask a follow-up question.

What happens after you write and what to expect

Once a message reaches SynqoraX AEON, it is logged against your account and routed to the team best placed to handle it, whether that is general customer service, a technical specialist, or your account manager where one is already assigned. You will typically receive an acknowledgment that the request has been received, followed by a substantive reply once it has been reviewed.

Support hours and the pace of replies can vary with the nature of the request and the channel used, since a quick account question and a more involved technical issue do not move through the same process at the same speed. Rather than commit to a fixed figure that would not hold for every case, the practical guidance is this: the more complete your first message, the fewer exchanges it will take to reach a resolution, and the platform’s own channels will always tell you directly once your specific request has moved forward.

If a reply asks for more information, it is worth sending it promptly and in the same thread rather than opening a new one, since a fragmented conversation is one of the more common reasons a straightforward issue takes longer than it should. If you do not hear back within a period that feels unreasonable for the type of request you sent, it is reasonable to follow up on the same channel rather than start over on a different one.

SynqoraX AEON treats every message that comes through these channels as a real account matter, not a queue to be cleared as quickly as possible. The goal on both sides is the same: get you back to trading with the issue actually resolved, not just acknowledged.