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 / The silence
In time, late, or never
The silence: what happens when a message was never sent
Every page so far has assumed a message existed. This one takes the harder case: the change happened and nothing arrived - or arrived after the date it was about - and asks what the reader can actually establish.
Desk spec
- cases
- 3
- in time
- 1
- late or never
- 2
- notices in the month
- 2
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 answerThree cases exist: a notice arrives inside its window, arrives after the window has closed, or never arrives. The samples carry two notices in a month of fifty messages; a reader can evidence the second and third cases far better by their own records than by the operator's, because what is missing is the only thing the operator's log cannot show.
The three cases
The distinction matters because the remedy differs. A late notice is a timing problem with a date attached; a missing notice is an evidence problem, and it is the reader's own correspondence that usually settles it.
Sample I and F - three cases, and what the reader can show in each
| Case | Window left | What the reader can show | What the operator can show |
|---|
| arrived inside the window | 30 d | the message and its date | the send log and the receipt |
| arrived after the window closed | -0.25 d | the message and the date it took effect | the same log, which dates the fault |
| never arrived | no window at all | the absence, and every other message received | nothing conclusive |
| three cases | 1 of 3 has a full trail | 2 of 3 rest on the reader | a log proves sends, not absences |
sample F and I - why an absence is hard to evidence
sent (log) = 50 of 50 = 100.0%
the log records what was sent, so it can show a send
it cannot show a non-send, because a missing row looks like
a row that was never created
arrival evidenced = 48 of 50 = 96.0%
read evidenced = 21 of 50 = 42.0%
notices in the month = 2 -> 4.0% of the volume
so the two messages whose absence matters most are also the
two smallest counts in the whole sample, and the least likely
to be noticed missing.
What a reader can put together instead
The reader's own material is what turns an absence into a question with an answer attached: a list of messages received, the dates, and the one change that was never announced among them.
sample A and E - building the reader's side of it
messages received in the month = 50
of which the reader can produce from their own account = 50,
because a message received is a message the reader holds
fields the operator's log keeps = 9 of 12
fields the reader's copy carries = sender, subject, date, and any
amount or condition in the text = 4 of 12
50 received messages x 4 fields = 200 data points the reader owns
against 9 fields the operator owns per message, of which the
one that matters here (a send that did not happen) is none.
How to handle a change nobody announced
The checklist is about ordering: what to gather before asking, so the question is answerable the first time it is put.
- Write down the change and the date you noticed it, before contacting anyone.
- Collect the messages received around that date, so the absence has a shape.
- Ask for the date the notice was sent and the channel used - a dated answer is checkable.
- Keep the answer with the message list, because the pair is what dates the fault.
- If the window has closed, ask what the window was and where it was published, rather than arguing the merits.
Read next