An unanswered email is real work with nothing to look at. The thing you’re waiting for hasn’t arrived, so your inbox stays quiet. You asked, so the doing belongs to somebody else. What you have is a message in your sent folder, filed under the day you wrote it rather than under what it was for. And a fact you’re carrying around in your head.
You asked the client on Tuesday whether to go ahead with the March work. It’s Friday, and the thread has been quiet since. The one thing that brings it back to you is you happening to think of it.
- Everything else in your day arrives at you. An absence lands nowhere.
- Replies come fast or they come in a long tail. Half arrive inside the hour. More than nine in ten arrive within a day. The rest take as long as they take.
- The mail you most need answered is the slow kind by construction. It asks for something, it leaves your firm, and you took trouble over it.
- You already hold two dates for every message you send. One is when you expect an answer. The other is when you decide something has gone wrong. Both live in your head.
What an unanswered email really is
Three different things get filed under waiting. This is one of them.
There’s the message that arrived and put an obligation on you. Somebody asked for the revised quote by Friday, so now it’s yours to do. That one has a well understood repair. The ask gets lifted out and dated, and nobody retypes it. That’s what email task management is about.
There’s the message you decided to deal with later. That’s deferral. The timing is yours, and it comes back when you said. Snoozing and setting mail aside covers it, including the part where the arrangement stays entirely private and leaves the other person’s side exactly as it was.
Then there’s the message you sent. You did your part. What’s outstanding is somebody else’s reply, and that one finishes on their desk rather than yours. You can write it down, and you can write the second message. That’s the whole of your influence over it.
That’s why the third one has nowhere to live. An inbox records arrivals. A task list records what you owe. A debt owed to you is a third thing, and it survives in your head.
When silence starts to mean something
The largest measurement of how fast replies actually arrive comes from Yahoo. It’s Evolution of Conversations in the Age of Email Overload, a 2015 paper for the World Wide Web conference. Farshad Kooti and Kristina Lerman at USC wrote it with Luca Maria Aiello, Mihajlo Grbovic and Amin Mantrach at Yahoo Labs. They took 1.3 million pairs of opted-in users who wrote to each other regularly, 187 million messages between them, inside a wider set of 16 billion.
The shape is worth knowing by heart. The most likely reply time is two minutes. Half of replies arrive within 47 minutes. More than nine in ten arrive within a day. The mean sits at 1157 minutes, a little over nineteen hours, with a standard deviation near two weeks. That’s what a long tail does to an average.
Read it as what it is, a distribution of the replies that came. It covers answered mail, and it makes no claim about how much mail goes unanswered. What it does establish is the second morning. A thread still quiet then has left the part of the curve that resolves itself. It’s somewhere in the tail now, where the answer might arrive this afternoon or in three weeks. That’s precisely why day two is unreadable. And these are people who correspond often, which is the friendly case.
People handle that unreadability with two numbers, and somebody wrote them down properly a long time ago. When Can I Expect an Email Response? was presented at the 2003 European conference on computer supported cooperative work. Joshua Tyler and John Tang interviewed 40 people, 37 of them at two large technology companies. They asked how each one judged that a reply was late, mostly at their own desks with their own mail open.
Two answers came back where they expected one. There’s the response expectation, the hour by which you think the reply should have come. Then there’s the breakdown perception, their name for the later moment “when the sender believes that something has gone wrong, and will take further action”. The gap between the two is wide, and people mean it to be. They describe someone who expects an answer within the hour and still waits a full day before walking to the person’s office. And someone who expects fifteen minutes and reaches for the phone after one.
At the breakdown point, they write, the sender “will either give up on the request or follow it up”. The follow-ups they observed were a phone call or a visit. Or a second email carrying “more urgency or adamancy in the subject line”. Or a look at the recipient’s calendar for something that would explain the quiet.
That’s forty people at two American technology firms in 2003, describing their own perceptions rather than timestamps anybody verified, which the authors say plainly themselves. The framework outlived the tools because it’s about people. You make both of those judgments on every message you send, whether or not you notice making them. The second one is a date, specific to that message, formed while you still remember what you asked for. Mail clients have had nowhere to put it.
Why the mail you need waits longest
Some of what you send comes back quickly, and some of it sits. The pattern is unkind. Characterizing and Predicting Enterprise Email Reply Behavior is a 2017 paper for the ACM SIGIR conference. Liu Yang with Susan Dumais, Paul Bennett and Ahmed Hassan Awadallah measured which messages get answered, across 938,035 messages from 279 accounts of a defunct technology company.
Three of their findings describe the mail a small practice actually sends.
Messages carrying a request were answered nearly twice as often as plain ones, 14.81% against 7.45%. They were also slower, at a median of 81 minutes against 55. The authors’ reading is the honest one. Such mail is “associated with tasks”, so somebody has to find a file or read something or write something before they can answer you at all. The very thing that makes your message worth answering is what pushes it down the pile.
Messages going outside the company were answered 2.26% of the time, against 7.76% for internal ones. They took a median of 135 minutes rather than 66. Every message you send a client crosses that line, in both directions.
Length costs you too. Reply rates climbed as a message grew to around forty words, peaking near 9.64%. Past that they fell, reaching 2.82% by five hundred words, with reply time rising the whole way. The careful message, the one you wrote at length because the matter deserved it, is the one that waits longest.
That’s one company’s archive, its mail dating from around the turn of the century. The rates count every message, including the bulk anybody would ignore, so those levels belong to that archive rather than to your inbox. Keep the ratios. They stack. A message that asks a client for something, leaves your firm, and runs longer than a few lines carries all three properties at once.
The Yahoo study adds the kindest finding in this whole subject. As people’s daily mail rose, the share of it they replied to collapsed, from around a quarter at low volume to under 5% for someone receiving a hundred messages a day. Their conclusion was that users “are unable to keep pace with rising incoming email traffic”. Your client’s silence is mostly a fact about their Tuesday. It’s rarely a verdict on your message, and almost never a decision they would recognize taking.
The list nobody keeps
So the debt is real. The wait is longest on exactly the mail that matters. And the judgment about when it’s gone wrong is one you’re already making. The question left is where any of it gets recorded, and for most people it lives in their head.
The sent folder is the only artifact, and it’s the wrong shape. It’s ordered by when you wrote. It holds everything you wrote, including the notes that were only ever telling somebody something. It marks the ones still open exactly as it marks the ones long closed. And what you’re hunting for sits outside it. You’re looking for a message with a reply missing beneath it, which is a fact about two messages, one of which was never written. Mailboxes are built to find messages. An absence is something else.
Which leaves two places. Your head, which works until the week it slips, and the week it slips is the week you needed it. Or a list you keep by hand. That’s a real repair, and it’s the one disciplined people use. It costs you a transcription for every message you send, and a sweep to keep it honest.
Tyler and Tang found that effort, though they found it pointing the other way. Patty, a solutions manager, reviewed her mail week by week to check she’d kept up with what she owed other people. Her own words: “I also take a look a lot at what’s happened in the last seven days, and did I respond to everything that’s been going on.” That’s the diligent version, done by hand. It works on the half of the problem where the messages are at least sitting in front of her. The mirror image went undescribed, because on the outbound side there’s nothing to scan.
Which gives a short specification for anything that claims to solve this. It gets set at the moment you send, while you still know what you asked and roughly when you need it. It hangs on the other person rather than on a clock, because what you want is the reply. And it stands down quietly when the answer arrives, because a chase for something already settled costs you more than staying quiet would.
The explicit version of that has existed for years as an add-on to ordinary mail. You mark a message on the way out and name a date, and it returns to you if the reply is still outstanding by then. It works, and it fires on the messages you remembered to mark. That’s a real distinction rather than a quibble. Point compared with Boomerang takes that difference apart properly.
What a returning thread cannot fix
A returning thread doesn’t make anybody answer. Bringing the thread back puts you in front of the decision again. The second message is still yours to write, and still theirs to leave.
It can’t tell you why the thread went quiet. Vacation, workload, a decision they’re still making, a no they’d rather keep off paper. All four look identical from your side, and silence keeps its reason to itself.
It can’t decide what the debt is worth. Some threads should be allowed to die. Chasing everything you’re owed is its own way of spending a morning badly, and that judgment stays where it was.
It will sometimes return a thread that was settled elsewhere. The client called. Somebody mentioned it in a meeting. That costs you a moment. The other error costs you a client asking why they never heard back, which is why the two are priced differently.
How Point brings a thread back
Point is a full email client, so both halves of the thread sit in one place. The message you sent, and the reply you’re waiting on.
You’ve answered somebody and the next move is theirs. You say so in plain words on the thread, in the same breath as sending. Point confirms it. The follow-up becomes a task with a date on it, so it lives on the same list as everything else you owe, with the plan on the task and one link back to the thread. Come the day, if the thread is still quiet, it returns to the top of your feed and Point nudges you to follow up. What you send is yours to write.
Open loops come back before they go cold, rather than at an hour you guessed at weeks earlier, and Point keeps the list of what you’ve handed off. If the answer arrives first, the thread is live again. Point notices work you’ve already finished, too. A task gets marked as looking done, with its reason in plain sight, and Point waits for you to agree.
Sometimes what you’re waiting on is an event rather than a reply. You can ask to be told when a particular message arrives or a condition is met. That request sits there as a standing task, marked as watching. You hear once when it fires, with a record of which watch it was and when. Waiting stops meaning checking.
How far Point goes on its own is a level per kind of action. The level runs from suggest-only, through preparing something and holding it for your review, to handling it outright. Every kind starts on review. What Point does is written down in order in plain sentences, and undoing something starts from the line that recorded it. A message already sitting on somebody else’s server is beyond recall. The rest of what Point does with your mail is on the benefits page.
Common questions
How do I find my unanswered emails?
The only trace is in your sent folder, filed by when you wrote rather than by what you’re still owed. Your inbox stays quiet on these by definition, because what defines them is that something stayed away. What you actually want to search for is a message with a reply missing beneath it. That’s a fact about two messages, and one of them was never written, so a search has nothing to match. Which is why every workable answer marks the debt on the way out rather than reconstructing it weeks later.
Does an unanswered email mean I am being ignored?
Very rarely, and the measurements point elsewhere. Reply rates fall steeply as somebody’s daily volume rises. Mail that asks for something is answered more often and later, precisely because answering it involves doing work. And anything crossing out of their organization is slower again. Your message is in a pile rather than under judgment. That’s also why a second message so often works. It arrives at the top of the pile on a better day.
How long should I wait before chasing?
The useful number is the one you already formed when you sent the thing. Research on this found people carrying two distinct times, the hour they expect a reply and the later point at which they decide something has gone wrong. The second is the one worth capturing, because it accounts for what you asked and who you asked. As a sense of scale, more than nine in ten replies that come at all arrive within a day. So a thread still quiet after two is genuinely quiet rather than merely early.
Is this the same as snoozing the thread?
No, and the difference is what ends the wait. A snooze runs on a time you named, kept privately on your side, and it returns whatever has happened since. A follow-up on an unanswered message runs on somebody else. It fires while the reply is still outstanding, and stands down quietly the moment it arrives. Reaching for a snooze here is the common way a wait turns into a series of guessed dates, each guess as blind as the last.
What if they reply before the follow-up is due?
Then the follow-up stands down and your day carries on. A chase sent for something answered on Tuesday costs more than the chase was ever worth, because what it tells a client is that you’re reading their mail carelessly. So judge any tool that does this on how quietly it stands down. The answer arriving should be enough to call the chase off, with you free to forget it was ever set.
Should the software send the chase for me?
The return is the part worth handing over. The message itself usually stays with you, because a thread that went quiet is a live relationship. The second note wants a sentence only you can write, about the March job or the missing statement or what you agreed on the phone. In Point the thread comes back and nudges you. How far Point goes on its own is a level you set per kind of action, starting on review.
The short version
An unanswered email is the one piece of your work that lives entirely in your head, because it’s made of something that stayed away. The wait is worst on exactly the mail that matters. Messages that ask for something get answered more often and more slowly. Messages leaving your firm are slower still. The careful long ones are slowest of all. Meanwhile the person you’re waiting on is replying to a shrinking share of what lands on them as their day fills, which means the silence is usually about their week rather than your message. You already decide, on sending, when quiet would stop being normal. The whole repair is putting that date somewhere other than your own memory, and having the thread come back to you on the day it’s still open.
Which debts hurt most depends on the work. An unsigned engagement letter in an accounting practice is a different animal from an unapproved layout in a design studio. There are eight trades with their versions written out.