You read it fast and answered the wrong thing

A message arrives about an order. It is read in about eight seconds. A reply goes out that answers something the message did not ask. Two exchanges later the situation is tangled and the vendor looks incompetent or evasive.

Sometimes the vendor is both. Often the message was clear and the reading was not.

Why these messages get skimmed

They arrive at moments of anxiety. The reader is not reading for content, they are scanning for reassurance or for bad news. Scanning finds one of those two things and stops. The middle of the message, where the actual instruction usually sits, does not get read.

The format makes it worse. Vendor messages tend to be short, unpunctuated and written by somebody in a hurry in a language that may not be their first. A message like that rewards careful reading and punishes scanning, and scanning is exactly what anxiety produces.

The three things most often missed

1. A conditional. The message said what happens if something, and the reader read it as a statement of what happened.
2. A time. The message gave a window, and the reader converted it to a promise with a deadline in it.
3. A request. The message asked for something small, and the reader replied without providing it, which stalls everything.

The third one causes the most damage relative to its size. An exchange stalls, the reader reads the silence as being ignored, and the whole relationship curdles over a piece of information that was requested politely and never sent.

How to catch it after the fact

Go back and read the thread from the top in order, without skipping your own messages. Reading your own replies is the uncomfortable part and it is where the answer usually is. If a reply of yours does not respond to the message above it, the tangle started there and not with the vendor.

Do this before escalating anything. An escalation built on a misread thread is worse than no escalation, because it burns the goodwill that a plain question would have preserved.

What follows from getting it right

The immediate gain is that you stop treating a confused counterparty as a hostile one. Those two require completely different handling and the wrong handling makes the confused one hostile.

The longer gain is a habit. Read the message twice before replying once. It costs perhaps twenty seconds and it removes an entire family of failures that otherwise get filed under the vendor going silent, where they do not belong.

Writing your own messages so they survive skimming

The same failure runs in the other direction. Your message will be skimmed by somebody handling a lot of them at once. A long paragraph with a question buried in the middle of it will not get the question answered, and then you will be annoyed about it.

• One question per message. Two questions get one answer and it is usually to the easier one.
• Put the question first and the context after it, not the other way round.
• Give the order reference in every message rather than assuming the thread carries it.
• Do not stack a complaint and a request in the same message. The complaint gets answered and the request gets lost.

None of this is politeness for its own sake. It is a way of making the reply useful, and a useful reply is the thing you actually wanted.

• Back to the cases you caused
• When the silence is really the vendor
• What a wrong attribution costs you