document somewhere that unsent replies are visible to all users

[redshiftzero]

It may not be clear to users (despite SD's shared inbox) that replies that fail to send (i.e. those that are in "draft" form) are visible to all users of that workstation, including those that are not logged in to the client.

[ninavizz]

I'd thought draft messages were not a feature in the Workstation, yet? Are you referencing the bounced message w/ the error bubble?

Off the top of my head, I'm not sure it would even occur to a user that some parts of the UI are visible to others, and some aren't. Especially when these failures are clearly indicated as a non-cancellable state in-context, vs as toast messages. Agreed wrt documentation "somewhere," but I don't feel it needs to either be in the UI or in the primary user guide.

[eloquence]

I think a note in the primary user guide that if a reply failed to send, other users on the same system will be able to see it, would be appropriate.

[gonzalo-bulnes]

Taking a mental note here that I find the name "draft reply" somewhat unexpected. I think I'd get a better intuition of what they are if they were called "failed replies" or something along those lines. Edit: If I understand well, "draft" is a state before the reply fails, so my suggestion wasn't that good either.

[cfm]

[In the neighborhood for #1634:] I'm curious if we have a clear use-case or user story for this behavior. It seems to me that it:

1. entrenches a state partition between the Client and Server;
2. requires edge-case handling in the current sending and sync implementation; and
3. may apparently surprise users enough to warrant documenting explicitly.