Short answer: treat a publish acknowledgement as a signed, replay-safe receipt, and keep token authority, subscription state, and business delivery as separate records. That decision gives a support agent a useful answer to “did my message arrive?” without turning an untrusted browser acknowledgement into proof that a customer saw it.
In a customer support chat, presence accuracy is a business property, not a green dot. A browser can reconnect while an agent is away, a mobile network can duplicate a publish, and a tab can close after the server has accepted bytes but before the receipt reaches the user. The backend therefore needs a stable event identifier, an explicit acknowledgement state, and an audit trail that survives reconnects.
What should secure realtime publish acknowledgements prove?
The receipt should prove only the narrow fact the server can establish: an authenticated principal was authorized to publish event evt_8f2 , and the service durably accepted that event for the conversation.…