You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reading receips standard is ambiguous.
I tested it and it shows up as a reading mark even though I didn't read it.
Please let me know the standard.
(I wonder what the standard of message reading processing is.)
To Reproduce
I'll tell you the criteria I tested.
Send a message and leave the chat window
I send a message to the customer right away
Customer indicates that message has been read
After a few seconds, the sign that I didn't read it is moxibustion.
Looking at this situation, it seems that the 'do not read' mark applies from a few seconds after leaving the chatty window, so please let me know the exact criteria for the 'do not read' mark
Expected behavior
No response
Environment
app.chatwoot.com
Cloud Provider
None
Platform
Browser
Operating system
No response
Browser and version
V3.8.0
Docker (if applicable)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
I'm not sure if I understand the issue. I didn't understand this piece "After a few seconds, the sign that I didn't read it is moxibustion."? Can you please provide screenshot or more information on what the expectation is?
I said it confusingly! I'm sorry.
First, I have a question, please let me know what is the standard for processing reading in Chatout. Are you processing reading as soon as the customer reads it?
It's because when I did a chat test on my mobile, it was marked as read in the chat room even though I wasn't in the chat room.
That's why I wrote the error report because I thought this was an error.
Describe the bug
The reading receips standard is ambiguous.
I tested it and it shows up as a reading mark even though I didn't read it.
Please let me know the standard.
(I wonder what the standard of message reading processing is.)
To Reproduce
I'll tell you the criteria I tested.
Looking at this situation, it seems that the 'do not read' mark applies from a few seconds after leaving the chatty window, so please let me know the exact criteria for the 'do not read' mark
Expected behavior
No response
Environment
app.chatwoot.com
Cloud Provider
None
Platform
Browser
Operating system
No response
Browser and version
V3.8.0
Docker (if applicable)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: