Snoozing an email lifts it out of your inbox and brings it back at an hour you pick. Setting mail aside is the same move under a plainer name. It’s the second half of every triage decision. An ordinary inbox gives you several ways to mark a message for later, and nowhere to put the when.
- Deferral is the bulk of a triage pass. Most of what a pass produces is mail you’ve decided to handle later.
- A flag records that something’s there. What the message wants and when you want it back both stay with you, and people mostly find their way back some other way.
- A snooze answers one kind of later, a time. Laters that are really events, and laters that are really conditions, want something else.
- Out of sight is the whole point and the whole risk. Mail you can’t see is mail you can’t count.
What does snoozing an email do?
Three things, in order. The message leaves the list you’re looking at. It waits somewhere you can still find it. At the hour you named, it comes back to the top and behaves like new mail.
Only the third is unusual. The rest of what an inbox offers does one or two of the three and stops before the return. The return is the part that matters.
Archiving does the first two. The message leaves and stays in your mail. Coming back to it depends on you remembering it exists. A flag or a star keeps the message exactly where it was, at whatever depth the day pushes it to, wearing a small mark. Marking a message unread works by throwing away a fact. The one thing you knew about that message was that you’d read it, and the reminder costs you that.
Both mainstream clients have the feature now, under the same name. Google’s help says that when you snooze, “the email is removed from your inbox temporarily”. It “comes back to the top of your inbox when you want it to, whether that’s tomorrow, next week, or in the evening”, and it waits under a Snoozed label until then. Microsoft’s description of the Outlook version is shorter and the same shape. A snoozed message reappears “at a specified time” (both checked August 18, 2026). The mechanism is ordinary and well established. The interesting question is what it can express, and where it runs out.
One more thing is easy to miss. A snooze is entirely private. The sender’s copy stays as it was, their thread still shows no reply, and the arrangement stays on your side. A snooze buys you quiet. The person waiting on you gets nothing from it, which is worth holding on to when what you’re deferring is somebody else’s decision.
Why most of triage ends in later
Triage ends in three answers, and only one of them is now. How email triage works sets out the pass and where it breaks under volume. What matters here is the pile it leaves behind.
The closest measurement of that pile is Characterizing and Predicting Email Deferral Behavior, a 2019 paper presented to the ACM conference on web search and data mining by Bahareh Sarrafzadeh, Ahmed Hassan Awadallah, Christopher H. Lin, Chia-Jung Lee, Milad Shokouhi and Susan Dumais. It runs on two tracks. One is fifteen interviews with Microsoft staff, conducted in their own offices with their own mailboxes open. The other is a log analysis of forty thousand enterprise users of Outlook’s web client, across the two weeks from May 6 to 19, 2018, some three million recorded actions. Their definition is the one worth keeping. An email is deferred when “the user deliberately postpones completing the task related to it to later”.
All fifteen said they defer, routinely. One put the rate at half of everything that arrives.
The logs read lower, and the gap is instructive. Measured through actions, 16% of active users deferred at least one message a day on weekdays, deferral showed up in at least 12% of triage sessions, and 3% of all messages were deferred. Those are floors. The only deferral a log can see is one that ends in a reply, a reply-all or a forward. Something you set aside and settled by phone, or read properly and closed, or left sitting, stays invisible to the count. A second figure gives the better sense of shape. Around 10% of messages get a reply, reply-all or forward at all, and 26% of those are written in a later session than the one where the message was first read. A quarter of your replies are already being deferred. That deferral lives in your head.
What gets deferred will surprise you. The interviews produced five factors, ranked by how often they came up. First, how much time and effort handling it would take. Then who sent it. Then how many other people were on the thread. Then the reader’s own workload at that moment. Urgency came last of the five. The message you put down is usually the one that would cost you twenty minutes, rather than the one shouting. That’s a separate observation from the one important versus urgent makes, and it points the same way.
The logs agree from the other side. Deferred messages averaged 3.9 recipients, against 7.0 for messages handled on the spot. They carried roughly twice the rate of explicit requests and reply requests. They were likelier to come from a person than a machine, and likelier to come from an important sender. Quietly, they were likelier to come from a sender the reader was hearing from for the first time. Addressed to you, written by a human, asking for something, from someone new to you. That’s also a fair description of a new client.
It builds fastest when you have least room for it. The same logs show deferral rising with workload. The more unhandled mail already sitting there, the likelier the next message was to be put down. The probability climbed from about 3% to about 4% as the meetings on a calendar went from one to five. The deferred pile grows fastest on the days with the least room to service it.
Fifteen people at one software company and forty thousand enterprise Outlook accounts are a long way from a five-person practice, so take the direction rather than the decimal. The direction holds.
Why a flag is not a return date
You do mark the mail you mean to come back to. That’s the right instinct. What the numbers show is that the mark itself is rarely the road back.
A companion study measured it directly. The Lifetime of Email Messages was presented at the 2018 conference on human information interaction and retrieval by Tarfah Alrashed, Ahmed Hassan Awadallah and Susan Dumais. It pairs two things. One is a log analysis of one hundred thousand active enterprise users of Outlook’s web client, February to May 2017, some 800 million actions. The other is a survey of 395 Microsoft employees in the United States, each asked to recall the last message they had gone back to.
Three of its numbers sit badly together.
People mostly saw it coming. 62.3% said they had known at first reading that they would need to return to that message. Then, of everyone surveyed, 38.5% left the message as it was, 27.4% moved it to a folder, and 19.2% flagged it or marked it unread. When the moment came, 71.6% found their way back by searching for it. Browsing the inbox or a folder accounted for 20.9%. Filtering for flagged or unread mail accounted for 1.5%.
One and a half percent. Search is the road back, even for the people who set a marker.
The deferral study reaches the same place from the other end. Its authors pulled every message in their sample that had been flagged or marked unread, 10,551 of them. They asked whether each went on to get a reply, a reply-all or a forward in some session after the one it was read in. About 14% did. Their own summary of that result is the sentence to keep. It suggests “users often do not go back to messages they explicitly mark”.
Two caveats belong with it. The window was two weeks. A message can also be settled by a phone call or a fresh thread rather than a reply, which their interviews describe people doing. So 14% is the share that came back as a reply, which is what people said they had in mind when they marked it.
The reason is plain. A flag carries one bit: something here. What the message wants stays in the message, so you reread it to find out. When you want it back stays in your head, so the choosing happens again on every pass. That one bit even changes meaning between people. The interviews found flags meaning “still pending” to people who let mail pile up, and meaning “important or urgent” to people who keep the inbox or the unread count at zero. A signal that means two things carries less than one.
Filing the pile away has its own failure and its own guide. A deferred queue sorted into action and waiting and someday is a ranking you’ve hidden from yourself, and inbox zero versus a calm inbox covers where that lands.
A snooze fixes exactly one thing here, and it’s the right thing. It attaches a when, so the message comes to you on its own.
What kind of later is it?
One of the people interviewed in the deferral study said the useful thing outright: “every time you flag something for later you should indicate what kind of later it is.”
There are three kinds, and only one of them is a time.
A later that is a time. Thursday morning. After the quarter closes. When I’m back from leave. A snooze expresses this one, and expresses it exactly.
A later that is an event. When the client returns the signed copy. When the bank confirms. When the surveyor’s report lands. The hour here belongs to somebody else, so naming one is a guess in both directions. Too early and you look at it again for nothing. Too late and you found out late. Most of what people describe as waiting is this kind, and a snooze is the wrong instrument for it.
A later that is a condition of your own. When I have half an hour and the file open. Another participant in the same study: “when I have 30 minutes I want to devote it to something longer […] and then for easy tasks I’m gonna do it when I have five minutes and I won’t do it when I have 30 minutes.” The researchers found people choosing the moment by optimizing two things at once. One is how little context switching it would cost. The other is how few separate sittings the message would take. That’s a genuine scheduling problem, and you’re asked to solve it mid-pass, in a second or two, about a message you’ve only skimmed.
That’s the honest limit of a snooze button. It answers the first kind well. It hands you the hardest part of the job: choosing an hour, one message at a time, at the worst possible moment for choosing anything. The button leaves that work with you. The work goes away when something else proposes the time, or watches for the event instead of asking you to name an hour that stands in for it.
When the later has a date in it because the message asked for something by then, you’re looking at an obligation with a deadline. That wants a different mechanism, and a better one.
Where snoozing goes wrong
Four ways, and three of them are one mistake in different clothes.
The message snoozed twice. A return time you can’t act on produces another guess, made on the same information as the first. Repeated snoozing is rarely a discipline problem. It’s usually a later of the second kind dressed as one of the first. You’re waiting on an event and expressing it as a date, so the date keeps arriving before the event does.
Monday morning. Snooze menus offer round times, and round times collect. Tomorrow, next week, Monday morning. What returns is a small avalanche. It lands on top of everything that arrived overnight of its own accord, at the hour of the week you can least absorb it. Deferral moves the pile at the same size, and it can stack it.
The count you gave up. Out of sight is the feature and also the cost. Once the mail is hidden, the glance that told you how much you owe goes with it. Set-aside mail wants to be visible as one list with its return times on it. Otherwise you keep a copy in your head, which is the job you were trying to put down.
Snoozing instead of declining. Some mail is deferred because you’d rather leave it alone, and a snooze is an excellent way to keep leaving it alone, on a schedule, with a clear conscience. The tell is the third return of the same thread. That message is usually waiting on a decision, and the decision is usually no, or a two-line answer you’ve been treating as a longer job than it is.
How Point sets mail aside
Start with the part that changes the arithmetic. In Point, everything that arrived overnight is read and ranked before you open the app, into now, later and other. How much a message matters and how soon it’s due are weighed as two separate things. The later call has already been made on the bulk of the pile. What you set aside by hand is the handful left over, and choosing an hour for those is affordable.
When you do set something aside, you pick the moment it comes back. It returns on its own at that moment, into the same ranked feed. Later is a section of that feed, sitting where you already look.
The second kind of later has its own mechanism, and this is the part a snooze button leaves alone. Point keeps track of what you’re waiting on, and reminds you to chase at the point chasing is worth it. A thread that’s gone quiet comes back to you before it goes cold, at the moment that matters rather than an hour you guessed at three weeks earlier. You can also ask in plain words to hear when a particular message lands or a condition is met, and that request sits there watching what comes in. That’s an event expressed as an event.
Where a message asks something of you with a date attached, Point lifts the ask out as a task. The task carries the due date and a pointer back to the sentence that produced it, so it still reads clearly three weeks later. Turning an email into a task covers that properly.
The controls sit around all of it. How far Point goes alone is a separate setting per kind of action, running from suggest-only through review to handled outright. Review is the default out of the box. What Point does goes into a plain-language record, in order, and any row there is one click from being taken back. The full inventory is on the benefits page.
Common questions
Where do snoozed emails go?
Somewhere you can still find them. A snoozed message is held out of the inbox view and stays findable while it waits. At the time you set, it returns to the top. Google describes Gmail’s version as the email being “removed from your inbox temporarily”, waiting under a Snoozed label. Microsoft describes Outlook’s as a message that reappears “at a specified time” (both checked August 18, 2026). The message is still in your mail, and the sender is still waiting on your reply.
What is the difference between snoozing and archiving an email?
Archiving decides the message is finished with. It leaves the inbox, stays in your mail, and coming back to it depends on you remembering it exists. Snoozing decides the message still wants you, just later, so it leaves and returns on its own. This is the one difference worth holding in mind: reaching for archive where you meant snooze is the common way something disappears entirely.
Is snoozing better than flagging an email?
For deferring, yes, and the difference is the date. A flag records that a message matters and leaves the when to you, so the choosing gets redone every time you scan the flagged list. In the survey above, filters for flagged or unread mail accounted for 1.5% of how people actually got back to a message. A snooze is the one common marker that brings the message to you.
Why do I keep snoozing the same email?
Usually because what you’re waiting for is an event, and you’ve been writing it down as a date. If the message depends on someone else replying or a document arriving, every hour you pick is a guess, and it keeps arriving before the thing does. That case wants a tracked follow-up or a standing watch. The other common reason is a decision still sitting with you, in which case the snooze postpones the decision rather than the email.
Should I snooze it or turn it into a task?
Snooze it when the message is fine as it stands and simply belongs at a different hour. Make it a task when it carries an obligation with its own deadline. A task records what’s owed and by when, where a snooze records when to look again. The rule of thumb: if you’d have to reread the message to remember what it wanted, make it a task.
The short version
Deferral is most of what a triage pass produces. The tools email gave it are a flag, an unread mark and a folder, and all three leave the when to you. The measurements are unkind about how well that works. People know at first reading that they’ll return. Most leave the message as it is, and when they have marked one, they overwhelmingly find their way back by searching. A snooze is the one common repair, and it repairs exactly one kind of later, a time you can name. Laters that are really events want something watching for the event. Laters that are really obligations want a dated task. What makes any of it affordable is the ranking being done before you sit down, so the call on each message is already made.
What ends up in the deferred pile depends on the work. It reads differently in an accounting practice than in a law firm, and there are eight versions of the morning written out.