Usually feels like
Days
Tomorrow is the right time to look, not tonight.
It sits in days because the queue is worked by staff in shifts, and the size of the queue when you joined it is not shown anywhere.
The wait, in plain words
Support queues are not conversations. A ticket joins a list held by the market, and the list is worked through by people whose shift it is. How long that takes depends on how many tickets arrived before yours and how many hands are on them, and neither of those is shown to you.
What is shown is your ticket, unchanged, which is why this wait produces such a strong urge to add to it. Adding is usually the wrong instinct. On some systems it reorders your place, on others it splits the history, and on all of them it lengthens the thing that has to be read.
The other half of this card is about timing. A ticket is the wrong tool for a wait that has not finished being a wait. Asking staff why an order has not arrived while the order is still inside its ordinary window produces an answer that says so, at the cost of a place in a queue you may want later.
Underneath, while nothing moves
An answerable ticket has a shape. It names one thing, gives the identifiers needed to find it without asking, says what you already tried, and states the outcome you want. A reader who can act without writing back to ask a question is a reader who closes your ticket in the shift they opened it.
- One subject. Two problems in one ticket get half an answer, and the half you needed is usually the second one.
- The identifiers the question turns on: the order, the account, the address. Not a narrative with them buried in it.
- What you already did, so nobody suggests it back to you and waits a day for your reply.
- The ask, in one sentence. Staff can do a small number of things, and naming the one you want saves a round trip.
- Nothing else. Background that cannot change the answer only delays it.
Written that way, one ticket does the work of three. Written as a story, it gets read, set aside at the part that needs checking, and returned to later, which is precisely the delay you were trying to avoid.
Underneath sits the deadline question again. If the ticket concerns an order, the settlement window keeps running while the ticket waits, and staff answering a question is not the same as a case being decided. If you need the case decided, the route is a dispute being looked at, and a ticket is not a substitute for it. Where the window sits is covered on escrow running down to auto release.
Behaving, and not behaving
A ticket that is behaving is one a stranger can act on. The failure mode here is not rudeness. It is unanswerability.
A ticket that can be answered
One question, the identifiers attached, what you already tried, and a clear request at the end of it.
Filed once, with nothing added since, because nothing has happened since that changes the question.
A ticket that cannot be answered
An account of how the week has gone, with the actual question somewhere in the middle of the fourth paragraph.
Three tickets about one problem, so whoever picks one up has to work out whether the others are duplicates before doing anything at all.
The reader is not judging you. They are deciding whether your ticket can be closed now or has to be parked, and a parked ticket rejoins the list at whatever position the system gives it.
This is also why the first day matters so much. A first ticket is read against an empty history. A fourth is read against three earlier ones, and reading those takes longer than answering the question would have taken at the start.
Safe to do meanwhile
While a ticket sits in a queue, all the useful work is on your side of it.
- Read your ticket as a stranger wouldIf the question is not obvious in the first two lines, it will be read slowly and answered late.
- Wait before adding anythingAn addition earns its place only if the situation changed. Restating is not a change.
- Check that it is a ticket at allOrder outcomes get decided in disputes. Staff answering questions is a different function entirely.
- Rule out the ordinary causesSome of what gets ticketed resolves itself while the ticket is still in the queue.
- Make sure it is not a cooldownA lock that lifts on its own does not need anybody to look at it.
What makes it longer
Queues stretch, and some of the stretching is done by the people waiting in them.
- Duplicates, which have to be identified and merged before either of them can be answered.
- A ticket filed during a busy stretch, when the queue is being fed faster than it is being worked.
- A question that needs a second team to answer, which is a queue behind a queue.
- A ticket about something that has not gone wrong yet, which cannot be answered except by saying so.
- Following up through another channel, which quietly creates the second ticket you did not mean to file.
What this card is not. This card is not a support channel, and nobody here can see, open or answer a ticket at any market.