What does “read” or “seen” mean?¶
It means the service recorded an interaction satisfying its read or seen rule. The event may reflect display or conversation opening; it does not prove that the intended person read, understood or accepted the content.
Determine the trigger¶
A phone, desktop, web session or linked device may generate the status. Some apps mark several messages read when a thread opens; previews or notification interaction can also matter. Privacy settings may suppress receipts, and synchronisation can delay them.
Preserve the exact label, message ID, associated time, service and linked-session context. Obtain the platform definition where the distinction is material.
Attribute awareness separately¶
A shared or compromised device can produce the event. Absence is also limited because content may be viewed in a preview or receipts disabled.
A reply addressing the content, later reference or consequential action can support awareness when connected to the relevant user. Report the service-generated state first, then the independent evidence for personal reading or knowledge.
The point to remember
“Read” or “seen” is a service interaction state; identify its session and corroborate the person and awareness separately.