Waiting for a reply, and what silence means

Silence is the cheapest thing another person can produce and the most expensive thing you will ever have to interpret. It costs them nothing. No keystroke, no decision, no second of attention. It can cost you an afternoon.

You sent the message and nothing came back. Since nothing came back, you have to supply the meaning yourself, so you invent a story to fill the gap.

The story is almost always worse than the truth.

Waiting hurts more than a no

A clear no ends a message, and silence keeps it running. That is the whole reason the wait is heavier than the rejection you are dreading.

When someone turns you down, you get your attention back. You are irritated for ten minutes, and then you go and do something else, because the loop is shut and there is nothing left to think about. Silence gives you none of that. The outcome stays open, and open things take up room whether or not you agree to let them.

I have watched this in myself with pitches for Unvent. A flat no on a partnership email lands badly for about an hour, and by lunch I have forgotten it. Two days of nothing on the same email and I am checking my inbox at a red light. The no was the worse news. The silence was the worse experience.

Part of it is that a gap has no content of its own, so it takes the shape of whatever you bring to it. Read your unanswered message on a good morning and it seems obvious that they are busy. Read the same silence at eleven at night and it becomes evidence.

The message you sent is finished. The message you are waiting on is still being written, in your head, all day.

The readings we invent, and the boring truth

The explanations people invent for silence are strangely consistent and almost always unkind. Three do most of the damage.

• They are angry, and the silence is the anger being polite about it.
• They are deciding against you, and the delay is the sound of the decision going the wrong way.
• They saw it and chose not to answer, which is the cruelest reading because it makes the silence deliberate.

Now the real causes, which are so dull that nobody bothers to imagine them.

• Your message was read on a lock screen while they were walking somewhere, and lock screens mark things read without answering them.
• The answer needs a fact they do not have yet, from someone who has not replied to them either.
• They wrote you a reply and it is sitting in their drafts, half finished, exactly like the ones in yours.
• Your message is forty down the list, under a thread about something on fire.

I believe the boring causes because I am the boring cause. There is a message in my inbox right now that I have opened four times, that I intend to answer properly, and that its sender has probably built a whole theory about. The theory is wrong. I liked the message. I just needed twenty minutes I did not have on any of the four occasions.

Reading silence as a statement about you is a form of vanity, and I mean that about myself first. It assumes you were the main event in someone else's day.

Rereading what you sent is the worst use of the wait

Rereading your own sent message is the single worst thing you can do while waiting, because it cannot change the message and it does change you.

The words are fixed now. Your reading of them is not. On the third pass you notice a sentence that could sound clipped. On the fifth you find the small joke that might read as a dig. You are not discovering what you wrote. You are assembling evidence for the story you already picked.

There is a version of this that feels responsible, where you reread it as though you were them. It is not responsible. Your model of them is built out of your own mood, so what you are actually doing is reading your message as an anxious person and then attributing that reading to somebody who is on a train.

It has a real cost, too, and it arrives late. By the time a reply finally lands, you have prosecuted your own message so thoroughly that an ordinary neutral answer reads as cold. Then you reply to the coldness that is not there. Now there are two people in a thread that has gone slightly wrong for no reason at all.

Close the sent folder. If the message has to have your attention, spend it on the next one rather than the last one.

Decide the deadline before you send

Set your own deadline at send time: how long you will wait, and what you will do when the time runs out. Write it somewhere you will see it.

This is the position I will defend hardest, because it is the one that changed my week. The sender owes themselves a deadline, and the only honest moment to set one is before the anxiety starts. At send time you are the calmest you will ever be about this message. Every hour after that you are a worse judge of how long is reasonable.

A deadline set while you are waiting is set by the waiting. It will pick two hours, or it will pick never, and both of those are moods pretending to be judgment. Chasing on mood means you nudge at hour three on a bad day and at day nine on a good one, so your timing ends up describing your state rather than the importance of the thing.

Mine are roughly these, and yours can be different as long as they exist before you hit send.

• A yes-or-no question to someone on my own team: end of the next working day.
• Anything that needs them to think, dig, or ask a third person: three working days.
• A cold message to a stranger: a week, one chase, then let it go for good.

The deadline does a second job that I did not expect. It gives the wait a visible edge before any reply arrives. Much of what makes waiting heavy is that it has no end you can point at, and "Thursday" is an end you can point at. Between now and Thursday there is nothing to decide, which means there is nothing to think about, which is the closest thing to peace available in an open thread.

You are allowed to decide something is not worth chasing. What you are not allowed to do is call that decision waiting.

Write the chase without the wait in it

Your follow-up should read as though no time has passed, because the accumulated feeling of the wait belongs to you and the reader was not there for any of it.

Four days of imagined slights leak into the text in small ways, and every one of them is legible to somebody who has no idea they were being tried in absentia.

• The timestamp that is really an accusation, as in "as I mentioned on Monday".
• The politeness that has gone stiff, where you suddenly start using their full name.
• The pre-emptive excuse, "I know you are swamped", which quietly asks them to confirm that they are swamped.
• The shrinking ask, where each attempt gets smaller until you are requesting permission to have asked at all.

One test catches all four. Would this sentence still make sense if they had replied within the hour? If not, it is residue from the wait, and it goes.

What remains is a message about the thing, which is the only message that ever gets answered. The mechanics of the chase itself, the ask and the date and the default, are a separate craft. This part is only about tone, and tone is where the wait shows.

I sometimes write the four-days-of-silence version deliberately, because the feeling needs to go somewhere and my head is a worse place for it than a text box. Then I take the residue off before it goes out, which is a lot of what I built Unvent to do: the ask survives, the four days do not.

The thing that changed most once I started dating my own waits was not my inbox. It was how quickly I answer other people. When you understand what your silence is doing on the other end, the eight-second holding reply stops feeling like a non-answer and starts feeling like the decent minimum. "Got it, I need until Thursday." That sentence cancels a story somebody else was about to spend two days writing about you.