Every few years, someone ships read receipts for email and pitches it as a feature. It is not. It is a pressure signal borrowed from a medium that runs on different assumptions, and it makes email worse at the one thing email is supposed to be good at.
What made email good in the first place
Email's entire value proposition is asynchronous communication. You send a message when it is convenient for you. The recipient reads and responds when it is convenient for them. No one is expected to be present at the same moment. That gap, the time between send and reply, is not a bug in email, it is the feature that makes it usable across time zones, schedules, and attention spans that do not line up.
Chat apps run on the opposite assumption. Slack, iMessage, WhatsApp: the expectation is closer to real-time presence. Read receipts and typing indicators make sense there because the medium already implies both people might be paying attention right now. The indicator just makes that mutual attention visible.
Import that indicator into email and you import an assumption that was never true of the medium. You tell the sender “this person is available right now,” when the entire reason email exists is that they are not obligated to be.
What read receipts actually do to behavior
Once a sender knows a message was read, silence becomes a signal instead of just an absence. “Read at 9:14 a.m., no reply by noon” reads as a choice, even when it was not one. Maybe the recipient read it on their phone in an elevator and genuinely could not respond yet. Maybe they read the subject line in a notification and have not opened the full email. The receipt does not capture any of that nuance. It just produces a timestamp that looks like evidence of neglect.
The result, documented informally by nearly everyone who has used read receipts in a work context, is defensive behavior: people delay opening emails to avoid starting a clock they are not ready to answer. That is the opposite of what the feature was supposed to produce. It makes people read email less promptly, not more responsively.
Typing indicators cause a milder version of the same problem. Watching someone “compose a reply” to your email creates a real-time expectation neither party asked for. Email replies often take drafting, redrafting, checking a fact, stepping away and coming back. Broadcasting the in-progress state turns a private drafting process into a performance with an audience.
The cases people make for it, and where they fall short
“I need to know if my email got through.” Delivery confirmation is a legitimate, separate need from read confirmation, and most email systems already handle delivery failure (bounces, out-of-office replies) without exposing whether a human eye landed on the message.
“I need to know if this is urgent enough to follow up.” This is a real problem, but the fix is upstream: mark the message as urgent when you send it, or rely on the recipient's own triage system to surface it appropriately. A read receipt tells you nothing about urgency, only about a timestamp, and it puts the burden of interpretation on the sender rather than giving either side better information.
“Sales and support teams want tracking.” This is the honest use case, and it is also the one where the surveillance framing is clearest: read tracking in that context exists to monitor the recipient, not to help them. It is a legitimate tool for specific workflows (email marketing platforms already offer it, transparently, as analytics), but it does not belong as a default in a personal inbox.
What STAMP does instead
STAMP has no read receipts and no typing indicators, by design, not by omission. What it does instead is give you honest information about your own inbox: an urgency queue built from real signals (sender history, deadline language, follow-up patterns) so you know what needs attention without needing to surveil anyone else's reading behavior. Snooze with a note gives you a way to signal “I saw this, I will get to it” on your own terms, when you choose to send that signal, not as an automatic broadcast the moment you open a message.
The asynchrony is the point. A tool for managing async communication should protect that gap, not quietly erode it into another channel where everyone is expected to be watching the clock.
The actual fix for anxious senders
If you are the person who wants a read receipt, the underlying need is usually “I want to know this did not fall through the cracks.” A better answer is a personal follow-up reminder: snooze your own sent message to check back in two days if you have not heard anything. That gives you the same peace of mind without putting a surveillance obligation on the person you emailed.
Async, on purpose. hello@stamp.email