Does merging of messages from two accounts now support it?
Closed this issue · 4 comments
Checklist
- Conducted a thorough search for similar issues, found no matches.
- Discussed this feature request on the [OpenIMSDK Slack](https://join.slack.com/t/openimsdk/shared_invite/zt-1tmoj26uf-_FDy3dowVHBiGvLk9e5Xkg) and received positive feedback.
Is this feature request related to a problem?
No.
Problem Description
Is there support for merging messages from two accounts? In developing a system like openkf, there's a scenario where a user switches from a temporary to a logged-in account, and there's a need to merge messages. Is this supported currently?
Proposed Solution
Upon switching accounts, messages from one account should be merged into the other, maintaining the chronological order based on the timestamp of each message to ensure there's no confusion in the sequence of the conversation.
Benefits
In openkf, this feature would significantly enhance user experience. Many current commercial customer service systems lack this functionality, which results in multiple conversation windows for a single account on the customer service representative's end, thus increasing communication overhead.
Potential Drawbacks
No response
Additional Information
No response
Thank you for bringing this to our attention and for the detailed feature request. The idea of merging messages from two different accounts, while maintaining chronological order, is indeed an interesting feature that could enhance user experience, especially in a customer service setting like openkf.
@IRONICBo
@sqzxcv @cubxxw Thanks for your advices! We have noted your requirements, I think it may be possible to do the matching process of user messages in kf's storage, or you can do the message migration on the openim side, but the implementation still needs to be evaluated for the impact the solution may have on other modules of the system.
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.
This issue was closed because it has been stalled for 7 days with no activity.