Ticket

Ticket is a written support request opened on a panel, and it is normally the only record of a dispute that you and the panel can both refer back to later.

Panels handle support through a ticket system on the site, sometimes alongside a chat channel. The ticket is the part that persists. A conversation in a chat window is hard to produce weeks later, and the staff on it change, so anything you may need to rely on belongs in a ticket even when the first answer arrived somewhere else.

Put the order ID first. Then the counts with the times you read them: what the profile showed before you ordered, what the order records as the start count, what it showed when the status last changed, and what it shows now. Then the arithmetic, written out, so the shortfall you are claiming is a number rather than an impression. Then say what you want, whether that is a refill, the cost of an undelivered part, or an order chased upstream. A ticket saying an order did not work invites a question back; a ticket with an ID, dated counts and a figure invites an answer.

On a reseller chain your ticket does not reach whoever delivered the order directly. The panel you bought from opens its own ticket with its provider, quoting its own order ID, and waits, and that provider may do the same again. Each step adds delay, and each step can only repeat what the one above it said. Open the ticket while the refill window is still comfortably open, not on the day it closes, because the answer can take longer than the window has left to run.