Usually feels like
An evening
You put the machine down and come back to it the same day.
Nothing here is automatic. The wait is the shape of somebody else's day, which is why it sits above the machine waits and below a vendor gone quiet.
The wait, in plain words
Sending is not delivery, and delivery is not reading. Your text landed in a box belonging to someone who is not sitting in front of it. Most people who run a shop work their messages in sittings, once or twice in a day, when they are at the machine and have time to answer properly.
So the honest shape of this wait is the shape of a stranger's schedule. It is not a technical delay you can inspect. There is no queue position to read, no delivered marker worth believing, and no indicator that would be telling you the truth if one existed.
Put the machine down. If the answer has to arrive before you can act, it will still need to arrive after you have cooked something and washed up.
Underneath, while nothing moves
Messaging on a market of this shape is a store and forward box rather than a live channel. Your text is held encrypted, sits in a table, and appears the next time the account it belongs to loads its inbox. Nobody is paged. No sound plays anywhere in the world. The interface is drawn to look like chat and behaves like post.
Vendors are somewhere, and it is not your somewhere. A message written at your lunchtime can land in the middle of somebody's night, and a reply that reaches you at breakfast was written at the end of a working session you never saw. Time zone is the largest single factor in this wait and the one almost nobody allows for.
Batching does the rest. Answering messages one at a time as they arrive is the slowest possible way to run a shop, so people who run shops do not do it. They open the box, work down it, and close it. A message that lands just after a sitting waits for the next one. A message that lands just before it can be answered while you are still at the keyboard. You cannot tell which of those you got, and the difference between them is not about you.
One more thing sits underneath all of it. A vendor answering a message is not doing the work that pays them, so the box gets worked when the packing does not need doing. That ordering is rational from where they sit and invisible from where you sit, and it explains most of the replies that arrive at odd hours in one burst.
Behaving, and not behaving
The difference between an ordinary silence and one worth reading is not a length. It is what else the account is doing while the silence goes on.
A silence that is only a schedule
No reply, but everything else about the shop looks alive. Listings are up, the account is not marked away, nothing has changed since you wrote. Silence here is the default state of a message that has not reached the top of a list.
You wrote once, clearly, and what you sent contains everything the reply needs. There is nothing outstanding on your side and nothing for you to add.
A silence that is telling you something
The silence runs alongside other changes. Listings have come down, the account reads as away or closed, or the item you asked about has quietly disappeared from the shop.
Or a deadline is running underneath it, and the silence now costs money rather than patience. When that silence outlives the evening it becomes a vendor gone quiet, which is a different card with a different set of moves.
The move at the end of the evening is not to write again. It is to ask whether the message was answerable in the first place. A message that asks several things at once, or that asks nothing precisely, cannot be closed in one reply, so it gets put back down and left for a sitting with more room in it.
Write so one reply finishes the matter. Give the order reference if there is one, say what you observed, say what you want, and stop. No story. No pressure. Do not put the same question three ways, because that reads as three questions and gets treated like three questions.
Safe to do meanwhile
Nothing on this list touches the vendor. That is the point of it.
- Read back what you actually sentA good share of slow replies are slow because the question could not be answered in a single go.
- Look at the clock instead of the inboxIf a deadline is what makes this feel urgent, the deadline is the thing to check, not the thread.
- Do the step that does not need the answerThere is usually one thing you were going to do anyway and can do now.
- Leave the thread alone until tomorrowIf it is still silent then, the wait has changed band, and the card for that state is not this one.
What makes it longer
This wait stretches for reasons that are mostly social. The few technical ones are small and boring.
- Writing again before the first message has been read, which adds to the pile you are waiting on.
- Sending during the far side of somebody else's night, which you cannot know about and cannot avoid.
- A weekend, a public holiday in a country you do not live in, or an ordinary day off.
- A message that asks several unrelated things, which needs a long answer and therefore a longer sitting to write.
- An angry message, which gets read, put down, and answered last. The pause you add yourself is the cheapest fix for that one.
- A rush at the shop, where every message in the box waits behind every other message in the box.
What this card is not. This card cannot tell you whether a particular vendor is still trading, and it knows nothing about any account anywhere.