Exness Live Chat: How Long the Wait Is

Ask the team

Exness support channels at a glance

Three clocks run on one question

Elapsed time on a request is rarely one measurement. Calendar time runs from the moment a message leaves the sender and never pauses. Working time runs only while a desk is actually staffed, so a question left late on a Friday can show a long calendar gap and almost no working gap. A third clock belongs to whatever the answer depends on: when a step only moves on a banking day, that clock ignores both of the others.

Most impatience comes from comparing the wrong pair. Read against calendar time, a Saturday afternoon looks enormous; read against working time, it looks like nothing happened at all. Both readings are correct and neither is much use alone. The habit worth having is to decide which clock the question depends on before deciding that it is late.

The distance between the sender's day and the answering day is the quiet fourth factor. A question typed at the start of one day can arrive near the end of another, which puts the first reply into what feels like tomorrow for one side and the same afternoon for the other.

In processing and sent are different states

The wording on a status line is not decoration. Received means the request exists and holds a place in a queue; nothing has been decided yet. In progress means it is open and the clock that matters has switched from queue time to handling time. Sent means the answer has left, which is not the same as arrived — delivery to an inbox, a messenger or a phone adds its own short leg.

Reading sent as completed is the most common misreading of a wait. A request can be closed on one side while the last message is still travelling, and a follow-up written inside that window reads as silence to one side and as a duplicate to the other. Letting one delivery cycle pass usually costs less time than the round trip a duplicate creates.

Between the named states there are also holds that belong to nobody's handling time. A request that is complete but waiting on a step which runs once a working day sits in something that reads as active and is really just parked until that step comes round again.

What lengthens a wait, and what only feels like it does

A first message that leaves out the detail the answer depends on does not add a little time — it adds a whole round trip. The question waits, the clarification waits again, and two waits are stacked where one would have done. This is the thing a sender controls most directly.

Sending the same question twice shortens nothing. Each copy takes its own place in a queue, and afterwards two answers have to be matched against each other. A reminder written before the first reply was due has the same shape: the reminder is itself something that has to be read.

Things that feel like delay and are not: a short acknowledgement arriving before any substance, which is the queue confirming rather than the answer starting; and an answer that arrives in parts, where the clock on the remaining part is shorter than the clock on the first, because the reading behind it is already done.

Reading a timestamp without arguing with it

A timestamp answers one question only: when that particular event happened. It does not say when the clock a reader cares about started. The moment a message left, the moment it was accepted and the moment work on it began are three separate marks, and subtracting the wrong pair produces a duration nobody spent on anything.

Two marks that disagree are usually both honest and describing different events — creation against last update, or acceptance against first handling. The useful question is never which mark is right; it is which event each mark belongs to.

Dates printed on a page follow the same rule. A last-updated line describes the page, and a capture date beside measured figures describes the moment of the reading. Neither of them is a statement about how long the next answer will take.

How to spend one wait instead of three

1. Decide which clock the question runs on before sending it: staffed hours only, calendar hours, or a step that moves once a working day.
2. Put the deciding detail in the first message — what was expected, what happened instead, and when. A question that can be answered without a clarification is answered inside one wait.
3. Note the moment the message left. That is the mark to count from; the time spent drafting it is not part of the wait.
4. Let one delivery cycle pass before treating quiet as a stall — sent and arrived are different marks.
5. If an answer is needed by a particular time, say so in the first message rather than in a follow-up: a deadline stated late cannot shorten a queue already joined.
6. When the answer depends on a step that only moves on a banking day, count the wait in that step's working days rather than from the message.

Timing for an individual account is always the timing shown inside that account's Personal Area, and processing times can vary. This page is about reading a wait, not about setting one.

What a wait is being measured against

The stages describe how elapsed time reads, not a schedule; the timing that applies to one account is the timing shown in that account's Personal Area.

Same question, two different waits

A way of reading elapsed time, not a commitment about it.

Related Exness pages