Hello @OneEagle ,

If you add a Messenger block directly on the Organization's view page (similar to how Messenger works on view-group pages), then the behavior will be the same as in Groups. In this case, all members of the Organization are added as individual participants of that conversation, and each member will have their own read/unread status. So if one agent reads the message, it will still remain unread for the others - exactly as you expect. However, if you use the Organization as a single profile in a conversation (for example, users start a direct chat with the Organization profile), then the message belongs to the Organization entity itself, not to its individual members. In that scenario, when any member reads the message "as the Organization," it becomes read for all, because it’s tied to the Organization identity, not separate users.

So both behaviors are possible - it just depends on how the conversation is created.