paidAffiliate disclosure. The partner link in the masthead and in the band beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. A desk about the messages an operator sends has no business leaving its own material unsaid, so its interest is stated here rather than left for a footer: one link funds the site, and no operator, platform, mail provider or product is named, rated or recommended anywhere on it.
The Mailroom / Sent, delivered, read
Four moments on one rail
Sent, delivered, read, acted: four moments that get treated as one
One message is four separate events: the operator sends it, the channel carries it, the reader opens it, and the reader does something as a result. Only the first of the four is reliably recorded, and the third and fourth are the ones that decide what happens next.
Desk spec
- moments
- 4
- delivery
- 0.9 s
- reading
- 41 m 21 s
- ratio
- 2,757
the five kindsA receipt records something that already happened, marketing promotes something, a service note explains a state of the account, a security alert says something changed, and a legal notice is the message whose arrival is itself a step.
the two switchesOne stops marketing and nothing else - 12 of 50 messages on the samples. The other does not stop anything: it changes the channel the remaining 38 travel on, which changes how they arrive and what they prove.
the three countsSent is what the operator's log holds (50 of 50), arrived is what a delivery receipt shows (48 of 50), and read is what a read receipt shows (21 of 50). Three counts, routinely called one.
Direct answerA message has four moments: sent, delivered, read and acted on. On the samples the delivery takes 0.9 seconds, the reading a further 41 minutes 21 seconds, and the action a further 29 minutes 38 seconds - so the carrier is faster than the reader by a factor of 2,757, and only the first moment is recorded for every message.
One message, plotted
The rail above plots a single message: a receipt sent at 09:00, arriving at 09:00:01, opened at 09:41:22 and acted on at 10:11:00. Each of the three gaps is a different kind of delay and only one of them is a channel property.
Sample D and F - the four moments, and which of them the operator can see
| Moment | Reached | Gap from the last | Recorded for |
|---|
| sent | 50 | - | all 50 |
| delivered | 48 | 0.9 s | 48 of 50 |
| read | 21 | 41 m 21 s | 21 of 50 |
| acted on | 14 | 29 m 38 s | 14 of 50 |
| four moments | declining | 0.9 s to 29 m 38 s | a third of the messages have an action |
sample D - the carrier against the reader
sent -> delivered 0.9 s = 0.9 s
delivered -> read 41 m 21 s = 2,481 s
read -> acted 29 m 38 s = 1,778 s
reader / carrier 2,481 / 0.9 = 2,757
so making the channel faster changes almost nothing,
and the 71 minutes 59 seconds between the send and the action
are almost entirely the reader's own time.
The post lane on the same rail
Two of the fifty messages travel by post, and the same rail cannot describe them in the same unit: the second marker moves from just after the send to two and a quarter days later, and the third marker disappears.
sample D - the post lane
email: sent 09:00:00.0 -> delivered 09:00:00.9 -> read 09:41:22
post: sent day 0 -> delivered day 2.25 -> read unknown
2 days 6 hours = 194,400 s; 194,400 / 0.9 = 216,000
read evidence exists for 21 of 50 messages, all of them electronic
read evidence for the 2 posted messages = 0 of 2
so the slowest lane is also the one with no way to show it arrived.
The rail on the home page plots the email lane of this sample: four nodes on one axis, with the gap between read and acted drawn open because it is the part of the journey no carrier controls.
What the four moments are good for
Read as four separate events, the words in a complaint change: "you never told me" is a claim about the second moment, "you never asked me" is a claim about the fourth, and an operator's log answers only the first with any confidence.
- Ask which moment is being described when a message is said to have been sent.
- Treat delivery as a channel property and reading as a reader property - only one of them can be changed in settings.
- Expect the action gap to be far longer than the delivery gap, so a short window is a reader problem, not a carrier one.
- Note that the noisiest channel is also the fastest and best evidenced, which is why routing away from it costs evidence.
- Keep the message itself, because it is the only one of the four moments the reader can evidence directly.
Read next