MessageReceipt

MessageReceipt refers to a metadata artifact used by messaging systems to indicate that a message has been processed or observed by the recipient. Common forms are delivery receipts and read receipts. They typically include elements such as message_id, timestamp, and recipient_id, and may indicate status (delivered, read) and the time of these events.

Delivery receipts are generated when a message reaches the recipient’s device or server, while read receipts are generated when the recipient’s client opens or displays the content. Some systems support both, while others implement only one. Implementation varies: explicit receipt messages versus client-side indicators; some standards exist for specific ecosystems, such as XMPP XEP-0184 for read receipts, and email protocols that use Return Receipt or Disposition-Notification. Mobile messaging often relies on delivery reports or in-app indicators.

Privacy and design considerations are central to MessageReceipt. Receipts can reveal presence and reading behavior, so users may opt out or privacy policies may suppress them. End-to-end encryption can complicate or prevent receipts from being generated or verified. Receipts may also be spoofed, delayed, or lost in transit, and privacy-conscious deployments may avoid universal receipt signaling.

Limitations and usage contexts vary. Receipts are not universally reliable and may be unavailable in offline scenarios or across different platforms. They are useful for audit trails, confirmation of delivery, and user experience cues, but designs typically include opt-in controls, clear user consent, and settings to balance transparency with privacy.