How to contact the right support

Arbicsx support is organized into specialized channels. Contacting the correct channel means receiving a faster and more precise response. This guide helps you choose where to open the ticket based on the type of request.

Before the ticket: try Arbicsxpedia

Many questions already have a published answer in Arbicsxpedia. The search bar (⌘K) returns articles and FAQs relevant to your keyword in real time. Consulting the knowledge base before writing to support is almost always the fastest route.

Types of requests

Requests are usually divided into three main families:

• Technical: the platform does not behave as described (displayed error, dashboard malfunction, synchronization issue with the broker).
• Commercial: subscriptions, services, renewals, information on available offers.
• Operational: doubts about the correct use of the platform or the dashboard, clarifications on metrics or functionalities.

The support page helps you direct the ticket to the correct channel based on these categories.

How to write an effective ticket

A well-written ticket is closed in fewer steps. Always include:

• a one-line summary of the problem or question;
• the exact scenario: what you were doing, what you expected, what happened;
• any error messages, reported textually or via screenshot;
• the browser and device, when it is a technical problem;
• attempts already made to resolve it.

What not to ask via ticket

Arbicsx support does not provide financial advice and does not comment on operational choices. Arbicsx provides technological software pursuant to D.Lgs. 58/1998 (TUF): capital remains at risk and no return is guaranteed. Questions about "what should I do" in the market do not have an official response from the platform.

The life cycle of a ticket

A ticket is not an isolated message: it is an interaction. After opening, the support team takes charge of it, may ask you for clarifications, update the status, and finally close it. Each of these phases is useful: if the ticket is "abandoned" without a response, the team cannot complete it. Responding even just to confirm that the issue has been resolved contributes to the quality of the service.

If multiple topics emerge during the ticket, consider whether to open separate tickets for each. A "single-topic" ticket is processed faster than one with multiple intertwined issues.

Practical advice

• One topic per ticket.
• Clear and concise title.
• Respond promptly to requests for clarification.
• Close the ticket when the problem is resolved.

Response times

The support team works during office hours and handles tickets in order of priority. Normally, the response arrives within a few business days. In the meantime, avoid reopening the same ticket with new emails: it slows down the queue and dilutes the context. If the topic is urgent and concerns account access, indicate it clearly in the first line of the ticket.

If your ticket is complex, the support team may direct you to a specific knowledge base resource for follow-up. Consulting Arbicsxpedia independently remains the fastest way to resolve general requests.