The snooze button is the most controversial primitive in modern email. Productivity people swear by it. Other productivity people swear at it.
The truth is in the middle. Snooze, used correctly, is one of the highest-leverage actions in your inbox. Used incorrectly, it is procrastination with a UI.
The case for snooze
Snooze answers a question your inbox cannot: “I have read this thread, I know what to do, but I cannot do it now.”
Without snooze, you have three options:
- Leave it in the inbox. It piles up. You see it 50 more times.
- Reply now. You context-switch. You do a worse job.
- Star it and hope. Stars get lost in noise.
Snooze gives you a fourth: take it out of the inbox now, bring it back at a known time. The mental cost of seeing the thread drops to zero. The mental cost of forgetting it drops to zero.
Done right, snooze is a calendar for email.
The case against snooze
Most people use snooze badly. Three failure modes.
One: snooze as procrastination. You snooze a hard email to Tuesday morning. Tuesday morning, you snooze it to Thursday afternoon. Thursday afternoon, to next Monday. The thread never closes. Snooze became your way of pretending you are not avoiding it.
Two: snooze without context. You snooze a thread without notes. When it returns Tuesday morning, you do not remember what you intended to do with it. You re-read the entire thread. The snooze cost you time.
Three: snooze pile-up. You snooze 12 things to Tuesday morning. Tuesday morning, you have 12 things plus your normal inbox. You triage 30 percent harder than usual.
These are real failures. Most snooze advice ignores them.
When snooze earns its keep
Three specific cases.
Waiting on someone else. A vendor said they would send a contract Friday. You snooze the thread to Friday afternoon. If the contract arrived, you reply immediately. If not, you nudge.
Action requires another tool. You need to update the dashboard before replying. Snooze until you are at your desk after the next meeting.
The reply is good but the day is not. A thoughtful reply is better in the morning. Snooze a 6 p.m. ask to 9 a.m. tomorrow.
In all three cases, the snooze has a why. Without a why, you are stalling.
How STAMP does snooze
STAMP attaches three pieces of context to every snooze.
- The time. Default suggestions: tomorrow morning, end of day, next Monday, next Tuesday morning.
- The reason. A free-text note. “Waiting on contract.” “Reply when at desk.” The note shows up when the thread returns.
- The original tag. When the thread comes back, it carries the tag it had when you snoozed. You do not lose the “Frustrated, 3rd follow-up” context.
This makes the wake-up moment usable. You see the thread, the original tag, and your note from yesterday. You act, in seconds, with the same brain you had when you snoozed.
A snooze without a note is a delay. A snooze with a note is a calendar entry.
The snooze-without-context problem
Most clients (Gmail included) snooze without context. The thread reappears. You re-read it. You decide again. You snooze again.
This is why a lot of users stop using snooze after the first month. The cognitive cost of re-deciding kills the leverage. The fix is to capture the decision at snooze time, not at wake time.
The pile-up problem
If you snooze 12 things to Tuesday morning, Tuesday morning is awful.
The fix is to spread snoozes deliberately. STAMP shows you, at snooze time, how many threads are already snoozed to that slot. If Tuesday morning is full, we suggest Tuesday afternoon. Same idea as a calendar app surfacing conflicts.
You can override. Most users stop overriding within a week.
The recurring snooze
A small but powerful pattern: a thread that you want to revisit weekly until it closes. STAMP supports “snooze until next Monday, repeat weekly.” The thread reappears every Monday morning until you archive it.
This is a substitute for “ongoing tasks” in a separate to-do app. We are not trying to be a to-do app, but a 90-percent-good email-native version saves users from leaving the inbox for ten more apps.
What we did not do
We considered (and skipped) two snooze features other clients have shipped.
Snooze on send. You write a reply, snooze the thread until two days later regardless of recipient response. We think this trains laziness. If you sent it, watch it.
AI-suggested snooze times. Some clients pick a time for you. We tried this. Users disagreed with the suggestions enough that they all ended up overriding. The override cost more than picking the time themselves. We removed it.
What to try this week
Pick three threads in your inbox that you keep seeing and do nothing about. Snooze them. Add a one-sentence note to each. See if they come back into a state where you can act in 30 seconds.
If yes, snooze is your friend. If no, you might be using it as procrastination. We have all done it.
Where to go from here
For the broader workflow, keyboard shortcuts every email power user should know. For the philosophy, the 7-email rule.
Snooze with intent. hello@stamp.email