Average response times

Having realistic expectations regarding response times makes the support experience much more serene. In this guide, you will find general indications on how queues work, what influences timing, and how to organize yourself when you have an urgent request.

How the flow is organized

Each request enters a queue dedicated to the channel it was sent to: customer care or technical support. Within it, it is classified by priority based on the operational impact and the nature of the request. This means that the processing order is not purely chronological: a blocking problem is addressed before an administrative clarification, even if it arrived later.

Factors influencing the timing

• the chosen channel: customer care and technical support have separate flows;
• the completeness of the request: a well-structured ticket is processed before one that requires clarification;
• the time window: requests sent outside of office hours are handled during the first available window;
• release phases, important updates, or scheduled maintenance, which temporarily increase volumes;
• periods with particularly attended live events, where questions related to training grow.

Realistic expectations

As a general rule, you receive an initial feedback within a horizon of a few working hours, and a full response within times that depend on the complexity of the case. Simple administrative requests often close at the first exchange; more complex technical cases may require transitions between different teams. Avoid measuring the service on a single urgent case and observe it over a broader horizon.

What to do if the topic is urgent

If you perceive a problem as urgent, indicate it explicitly in the text with measured words and explain what the actual impact is: which operation is blocked, which deadline is at risk. Avoid labels like "extremely urgent" applied to every message: they make it difficult to truly distinguish priorities and, in the medium term, backfire on those who use them.

How to reduce times on your side

The quality of the request is the first accelerator. The guides How to send an effective request and Which screenshots or data to attach describe in detail how to prepare a clear ticket. A second accelerator is the prior consultation of the knowledge base: many answers are already online and allow you to reach support only when truly necessary.

Transparency

The indicated times are not a contractual commitment but an operational reference. Arbicsx provides technological software pursuant to D.Lgs. 58/1998 (TUF); support is part of the service and is provided with the utmost care, but no operational performance depends on the speed of an assistance response.