but when we retrieve this latest conversation, looks like it is not same as previous conversationid.
Just wondering is it mean us doing something not correct, so not return back to previous conversationid?
Or is there any setting to make this new conversation to re-use the same conversationid as before, consider user is still same browser ?
Any suggestion will be appreciate, but our client do not want to use custom javascript to solve this approach.
@fransiska.hendra the behavior you observe is correct: those are two different conversations, because End-User made an explicit decision to Clear the previous one. The cookie identifier is still the same across both conversations, so looking at the Customer Journey all 3 Web Messaging conversations would be correlated to the same user: not ideal for now, but Agents could retrieve the previous conversations via External Contact. We plan to improve the UX by showing the previous message conversation transcripts inline with current transcript.
The alternative for now would to disable Conversation Clear, to show all messages within single Async transcript to Agent.