Exness Contact and Support — One Case or Two? — South Africa
A support thread stays one case only while it keeps one account, one event and one reference — this page is about telling a continuation from a fresh request.
Open Exness Account →Two messages are one case when they concern one account, one event and one reference. The same topic is not the same case: two deposits made on different days are two matters even when both are described in identical words. A reply inside an existing thread continues that record; a fresh conversation about an event already reported creates a second record of one event, and the two then disagree about what has already been said.
Same matter or a new one — how each contact counts
| Situation | Counts as | What carries it |
|---|---|---|
| You reply inside a thread that already carries a reference | The same case | The reference already on the thread |
| You start a fresh conversation about an event you have already reported | A duplicate of one case | Nothing, until the reference is quoted |
| You raise the same kind of question about a different transaction | A separate case | Its own new reference |
| You add a document that was asked for inside a thread | The same case | The thread it was asked in |
| You write again after a thread has been closed | A new case that points at the old one | The old reference, quoted first |
A reference belongs to the matter, not to the place it started in: quote it and the same record continues.
Same words, different matter
The commonest way one matter becomes two is repetition of the description. A transfer that has not appeared, and a transfer that has not appeared a fortnight later, read as the same sentence, but they are two events with two dates and two amounts, and each needs its own record. The description is what you notice; the event is what the case is about.
The reverse happens just as often. A question about an order that closed at an unexpected level and a question about the balance afterwards can look like two problems and turn out to be one. When a single answer settles both messages, they were one matter described twice, whatever they were called when they arrived.
How a case keeps its name
Every thread acquires a handle of some kind — a case or ticket reference, or at minimum the date and the place it began. That handle, and not the subject line, is what makes a later message a continuation. Quoting it in the first line of the next message is the whole of the technique: it turns a new arrival into the next entry in an existing record.
Changing where you write does not end a case and does not carry it either. A message that moves from one window to another is a new arrival in a new place; the reference is what tells the new place which record it belongs to. Without it, the second arrival is correctly treated as a first.
When a closed case comes back
A closed record is a finished statement, not a locked door. Writing again about the same event after closure rarely reopens the old entry; it usually opens a new one that points at it. That is not a loss. A pointer to the earlier reference hands the new record everything the old one established, and it makes the second attempt legible as a second attempt rather than as a first report of something already discussed.
The signal that the pointer was missed is easy to read: the new answer repeats what the first answer already said. When that happens the two records are not linked, and quoting the earlier reference is what links them.
Keeping one matter inside one record
- Fix the event before writing: which account, which transaction or order, and which date. Those three facts are the identity of the case.
- Send one message per event. Two events described in one message are answered as one, and half of the answer goes missing.
- Keep the reference the thread was given and quote it in every later message about that event.
- Do not open a second conversation about an event you have already reported — add to the thread that already holds it.
- If the thread was closed, open the new message with the old reference and say what has changed since.
The account, the event and the reference are what make two messages one case. Wording is not one of them.
What makes two contacts one case
| Test | One case | Two cases |
|---|---|---|
| The account involved | The same account in both messages | Different accounts, even under one profile |
| The event described | One transaction, one order, one requested document | Two events that happen to share a description |
| The reference | One reference quoted in both | Two references, issued separately |
| The answer | A single reply settles both messages | Each message needs an answer of its own |
Case identity is decided by the account, the event and the reference — not by how the question is worded.
Frequently asked questions
How is a new message recognised as part of an earlier case?
Is a second message about the same problem a continuation or a new case?
Does writing somewhere else keep the same case?
What happens if I open a second conversation about something already reported?
Can a case be continued after it has been closed?
Two questions were settled by one reply — were they one case?
Do two accounts under one profile share a case?
What is the shortest way to keep a matter in one record?
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