In this piece
- 01The signal is narrower than it looks
- 02What it cannot tell you
- 03The off switch
01The signal is narrower than it looks
That small double-tick, the word "Read," the faint timestamp — they feel like confirmation that your message landed with another human being. They are not quite that. They are a report from a piece of software running on a device, and the gap between those two things is worth understanding.
When a read receipt fires, here is what actually happened: the receiving app opened the conversation thread and marked it as seen, then sent a read acknowledgement back to the server or directly to your client. The trigger is typically the message appearing on screen — the app's window coming to the foreground with that conversation active. Nothing in that sequence requires the other person to have read a word, formed a thought, or decided anything at all.

Nor does a receipt confirm comprehension, agreement, or intent to respond.
A phone can generate a read receipt while sitting face-down on a table, unlocked, with a notification preview having briefly lit the screen. A desktop client can mark a thread read when a user switches to that tab and immediately switches away. Background sync on some platforms will mark messages seen without the conversation ever being opened. The receipt reflects a device state, not a cognitive one.
02What it cannot tell you
The receipt also says nothing about context. The other person may have read your message in a meeting, on a crowded train, mid-conversation with someone else — any situation where replying immediately is simply not possible. The receipt records the moment the app registered the message; it records nothing about the moment's circumstances.
Nor does a receipt confirm comprehension, agreement, or intent to respond. These seem obvious when written out, but the anxiety a delayed reply can generate suggests the brain quietly treats the receipt as a social contract rather than a technical log entry. It isn't one.
There is also the question of what "delivered" means before a receipt even arrives. A message passes through several systems before any read signal is generated — server queues, push notifications, local storage — and at each stage the message exists independently of any human attention. A receipt is the last in a chain of automated confirmations, not the first moment a person was involved.
03The off switch
Most platforms let users disable read receipts, and many people do. When receipts are off, the sender typically sees only delivery confirmation — evidence the message reached a device, not that it was opened. This is a deliberate privacy affordance, and it cuts both ways: you lose the ability to see when others read your messages, and they lose it for yours.
A receipt, when it arrives, is useful for one thing: confirming the message was not lost. Everything beyond that is inference.
--- An independent explainer on instant messaging. Not affiliated with, endorsed by, or connected to Trillian, Cerulean Studios, or any messaging service.