-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE REQUEST]All unread historical messages need to be set as one click read. #2305
Comments
Hello! Thank you for filing an issue. If this is a bug report, please include relevant logs to help us debug the problem. Join slack 🤖 to connect and communicate with our developers. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
skiffer-git
changed the title
[FEATURE REQUEST]
[FEATURE REQUEST]All unread historical messages need to be set as one click read.
Sep 29, 2024
All unread historical messages need to be set as one click read. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why this feature?
In this application project, we provide services to customers by building a group. In addition to customers, there will also be multiple role personnel in the group, which can provide comprehensive services to customers, solve problems encountered, and everyone can see relevant messages in the group. At the same time, the system will also send some reminder messages in the group. Because there are too many messages, some personnel do not need to read them one by one, which leads to new news that is not as eye-catching, affecting the timeliness and efficiency of communication with customers. All unread historical messages need to be set as one click read.
Suggested Solution
Providing an interface in the Client SDK is sufficient, while the Server API is not required. This feature is related to the personnel on the user end.
Additional Information
No response
The text was updated successfully, but these errors were encountered: