Checking What to Confirm in a Support Ticket Before a Trade Dispute

When I open a support ticket that might turn into a trade dispute, I treat it like a dated record, not a quick message. I want the ticket to show the same facts I will rely on later. If something is missing, I add it before the conversation goes far.

First, I confirm the account and order identifiers. I include the account number or label, the ticket number, and the order or trade ID if the platform shows one. I also state the instrument, side, quantity, order type, and whether it was opening or closing a position. For example, I might write: “Order 12345, ES, sell, 2 contracts, stop order, opened 10:14:32 ET.” The exact fields depend on the provider, so I check its current terms and platform labels.

Then I check timestamps. I write them with a timezone and date, not just a clock time. If my screenshot says 09:42 and the ticket says 09:47, that gap matters. I paste the visible timestamp into the ticket and note where it came from: order history, fills, statements, or an email confirmation. I keep the original screenshot file and its file date. I do not edit screenshots; if I crop one, I keep the full version too.

I also confirm what I am asking for. A dispute is easier to follow when the ticket says, “I am asking for a review of this fill” or “I am asking for a correction to this order record,” rather than only describing frustration. I list the facts I can prove and the facts I cannot. If a plan costs $150, for example, I keep the billing question separate from the trade question unless they are truly connected.

Before I escalate, I reread the ticket and add a dated note. I write what happened, what the support reply said, and what is still unresolved. I save the ticket and replies together as my dispute record. I keep a short set of prop support notes next to my trading log so I can compare my record with the ticket. That habit helps me spot a missing order detail or a timezone mistake before a dispute gets formal.

The goal is simple: make the ticket specific enough that someone else can follow it without guessing.

— Alex Morgan