Exness Customer Service: Coming Back to the Same Case · Pakistan
A second message about the same matter saves time only if the first one can be found again — by the reference it was given, by the words it used, and by the time the event itself happened.
Open Exness Account →Writing a second time about the same matter is a different job from writing the first time. Three things carry over and shorten it: the case reference from the first reply, the wording used originally, and the time the event happened together with the offset it was read in. Three things carry over badly: a summary of the answer received, a screenshot taken after the screen had already cleared, and the time the first message was sent rather than the time of the event.
What carries over from the first message
| What was kept | What it does on the second message | What it cannot do |
|---|---|---|
| The case reference from the first reply | Points at the existing thread instead of describing it | Cannot re-open a case that was closed on its own terms |
| The original wording, repeated | Keeps the second reading of the problem identical to the first | Cannot stand in for the account number the event sits on |
| The time of the event, with its offset | Narrows the search to one window in the record | Cannot help when only the day is remembered |
| A frame captured while the state was still wrong | Shows what prose otherwise has to describe | Cannot carry what happened before or after that frame |
| One line on what changed since | Marks the follow-up as new information, not a repeat | Cannot replace the reference that ties it to the first thread |
Live chat, email and support tickets, and the help centre are all reached from inside the Personal Area, and which of them is open can change — so a follow-up is built from the record rather than from a remembered channel.
The three items worth copying out of the first exchange
A case reference is the only item that points at a thread instead of describing one. Copied exactly, it puts the second message on top of the first; retyped from memory it points at nothing, and the exchange starts again from the beginning.
The original wording matters more than an improved version of it. A problem described two different ways reads as two different problems, and the second description has to be worked through from scratch by whoever picks it up.
Local clock time sits at UTC+5 all year with no seasonal change, so an offset stated once stays correct — but it still has to be written down. The time of the event, with that offset, is what turns a search of the whole record into a look at one window.
What is not worth carrying over
A summary of the first answer is the commonest thing to keep and the least useful: it records a conclusion without the question that produced it, and a retelling binds nobody to anything.
A screenshot taken afterwards shows a screen that has already moved on. The frame that carries weight is the one captured while the state was still wrong, even when the picture itself is poor.
The time the first message was sent is not the time of the event, and a search built on it lands in the wrong window. The bare date has the same problem, only wider.
When a second message is the wrong move
Some threads are waiting rather than stalled — a document under review, a transfer still inside the window named in the first answer. A follow-up does not move those, and it splits one thread into two that then have to be reconciled.
The signal that a follow-up is worth sending is a change on your own side: something new was tried, the state on screen moved, or the window given in the first answer has passed. Without one of those the second message repeats the first, and it is read as the first.
Building the second message
- Open the first thread and copy its reference exactly as it was written there.
- Paste the original description above anything new — the same sentence, not a tidier one.
- State the time of the event with its offset, and the account number it sits on.
- Add one line for what changed since the first answer: what was tried, and what the screen shows now.
- Attach the frame captured while the state was still wrong, if there is one; a later screenshot documents a different moment.
Response times and available channels are shown inside the Personal Area and the official help centre, and can change.
Two forms of the same detail
| Detail | The form that continues the thread | The form that restarts it |
|---|---|---|
| Case reference | The number copied from the first reply | A description of when the first message was sent |
| The problem | The original sentence, repeated | A cleaner rewrite of it |
| Time | Clock time plus the offset it was read in | Yesterday evening |
| Account | The account number the event sits on | The sign-in address on its own |
| Evidence | A frame captured while the state was wrong | A screenshot taken after it cleared |
| Progress | One line on what changed since | The first message sent again |
Frequently asked questions
What should a second message about the same issue open with?
Why repeat the same wording instead of explaining it better?
Which time should be given — when it happened, or when it was reported?
Is a screenshot still useful after the screen has cleared?
When is it better not to send a second message at all?
What is worth keeping once a case is closed?
Where are the current contact channels listed?
Reviews
What traders say about Exness customer support:
Very good customer service and accessibility. Reliable and Accessible
Awesome. Provides confidence and support
Poor customer support. The customer support process was quite slow and unhelpful, for account verification process took 2-3 weeks as their response is always delayed. Later case was closed without any follow-up
Card verification not working. Already informed support team but there’s no action taken