CFDs are complex instruments and come with a high risk of losing money rapidly due to leverage. Trade only with money you can afford to lose.
Open Exness Account →

Exness Customer Service: Coming Back to a Case — Philippines

A follow-up and a first question are different errands: one needs the whole story, the other needs a reference and the single detail that changed since last time.

Open Exness Account →

100+ instruments  ·  Founded 2008

Support threads have memory, and it is shorter than most people expect. A ticket keeps its reference, its attachments and everything written in it, so a follow-up can start from the middle. A chat session keeps nothing once it closes, so the second conversation begins where the first one began. Almost every repeated explanation comes from that difference rather than from the agent on the other side.

Which route survives a follow-up and which starts empty

The routes below are the ones the broker publishes. What changes between the two right-hand columns is not speed but memory — whether the route keeps anything about the errand once it is over.

RouteFirst questionComing back to the same case
Live chatFits a short question that can be settled inside one sessionOnly if the reference is repeated — a fresh chat opens with nothing in it
Email or support ticketFits anything that needs a document attachedThe natural home for it: the ticket is what carries the thread
Help centreAnswers the question before it becomes an errand at allKeeps no record of an individual case

Where a case already has a reference, quoting it is worth more than repeating the story; where it has none, the story is all an agent has to work from.

Why the same thing gets explained twice

A chat is a session, not a record. When it ends, the transcript stops being the thing anyone looks at, and the next conversation opens without it. Repeating the story is the price of having chosen the faster route the first time.

A ticket is the opposite trade: slower to start, but everything inside it survives. Its reference is the handle that lets a second person pick the case up exactly where the first one put it down.

The third source of repetition is the account number. One profile can sit behind several trading accounts, so my account is ambiguous in a way that account 12345678 never is.

What to keep on your own side

Nothing on the support side is designed to be your archive. The reference, the date of the first message and the name of the document that was attached are cheap to write down and expensive to reconstruct.

Where a case runs across several days, a one-line log of what was asked and what came back turns the next follow-up from a re-explanation into a single sentence.

How to reopen a case without starting over

  1. Reply inside the existing ticket rather than opening a new one; a new ticket has no history behind it.
  2. Put the reference on the first line, before any explanation.
  3. Say what changed since the last reply, and stop there.
  4. Name the trading account by its number rather than by its type.
  5. Attach a document again only when the reply asks for it — sending it twice slows the thread down.

If the first contact was a chat and no reference was issued, treat the second one as a first message and give the whole story once more.

What a follow-up needs that a first message does not

What you sendFirst messageFollow-up
The case referenceDoes not exist yetThe single most useful line in the message
The full storyRequired — nothing is known yetNot required once the reference is quoted
Documents already sentSent for the first timeStill attached to the ticket; re-send only if asked
What changed since last timeNothing to reportThe actual content of the message
The trading account numberRequiredRequired again — one profile can hold several accounts

A follow-up that repeats the whole story without a reference reads as a new case, and it is handled as one.

Frequently asked questions

Does Exness support remember a previous conversation?
A support ticket keeps its thread and its reference, so a follow-up can start from the middle. A closed chat session is not a record that can be pointed at later, which is why the second conversation usually begins again.
What is the fastest way to continue an existing case?
Reply inside the existing ticket and put the reference on the first line. Everything already attached to that ticket stays attached to it.
Why is the account number asked for again?
One client portal can hold several trading accounts, so the profile on its own does not say which account a question is about.
Do documents have to be sent twice?
Not usually. Anything attached to a ticket stays with it, and a second copy is worth sending only when the reply asks for a newer version.
When is chat the wrong route?
When the answer will outlive the session. Anything that needs a document reviewed leaves no trace once the chat window closes.
What should a follow-up message actually contain?
The reference, the account number and the one thing that changed. The full story belongs in the first message only.

Reviews

Traders on what happens on the second contact:

★★★★☆
Nice Broker with top-notch UI and an excellent Support System
— PALE OBSCURA2026-04-05
★★★☆☆
It's quite good, just need to speed up on responding on the app...
— Lazarus Amon2026-04-13
★☆☆☆☆
too much slippage, support closes tickets and don't even bother to update you
— Johnathan Shuttleworth2026-04-17
★☆☆☆☆
No customer service. I’ve been trying to contact you for the past week concerning changing the number registered to my account yet no one has responded but the useless robot
— Duran00002024-10-15

Related Exness pages