Skip to content
Skip to main content
Messaging, Social Media & Telecoms Operational Explainer

How should delivery and read-status evidence be worded?

Use the service's exact label and describe it as a recorded account, device or session event. Do not translate “delivered” into personal receipt or “read” into human understanding without supporting evidence.

Status meaning is platform-specific

Delivery may mean acceptance by the provider, arrival at an account or availability to an endpoint. Read or seen status may arise when a conversation is opened, perhaps through another linked device, a shared account or an automated process.

Preserve the icon or wording, timestamp and time basis, message and account IDs, endpoint context and platform version where relevant. Compare sender and recipient records and obtain service definitions if the distinction is material.

Write the bounded event

Suitable wording might state that “the service recorded the message as delivered at 14:32” or “the recipient account displayed a seen status.” Then identify any separate evidence of who controlled the endpoint and whether the content came to their attention.

Read events created during examination must remain separate from original activity, as explained in marking a message as read. Where the service meaning is uncertain, retain that uncertainty rather than selecting the strongest everyday interpretation.

The point to remember

Report delivery and read labels as service-defined events, attributing personal receipt, attention or understanding only through additional evidence.

Reference: MSG-120Messaging, Social Media & Telecoms