Sr. IT COMM Eng.
Original Message:
Sent: 08-29-2023 08:51
From: Angelo Cicchitto
Subject: Web Messaging - End-User can Clear the Conversation
Detecting browser tab closing is something to research outside of any Genesys Messenger event. From other JS developer forums, it looks like beforeunload event is triggered by browsers just before closing, but we are not testing or validating this approach explicitly, so you would need to test this as external customization.
------------------------------
Angelo Cicchitto
Genesys - Employees
Original Message:
Sent: 08-29-2023 07:26
From: Matthew Raleigh
Subject: Web Messaging - End-User can Clear the Conversation
Hi Anglelo,
Thanks for your response.
Also, I am trying to guard against the case when a user closes the browser/tab while the conversation is still open. It is possible another user at the same computer re-opens the browser and can see the former user's conversation.
I have managed to use the JS SDK to clear the conversation upon restoration of the messaging service. A question I have is what event is triggered when the browser/tab is closed? And is it possible to clear the conversation or session based on this event instead upon restoration?
Thanks in advance.
------------------------------
Matthew Raleigh
Thermo Fischer CRG
Sr. IT COMM Eng.
Original Message:
Sent: 08-29-2023 02:28
From: Angelo Cicchitto
Subject: Web Messaging - End-User can Clear the Conversation
That seems fine @Matthew Raleigh
Inactivity detection will be solved by different Idea > https://genesyscloud.ideas.aha.io/ideas/DIG-I-1056
------------------------------
Angelo Cicchitto
Genesys - Employees
Original Message:
Sent: 08-28-2023 14:35
From: Matthew Raleigh
Subject: Web Messaging - End-User can Clear the Conversation
Hello All,
I am using the follow command to clear the conversation when the conversation is disconnected which works well. However, wondering if there is a way to clear the conversation based on inactivity on the user's part. Maybe an inactivity timer or another way? I saw a typing timer but do not think this will work for this case.
Genesys("subscribe", "MessagingService.conversationDisconnected", function({data}){
console.log(data);
Genesys("command", "MessagingService.clearConversation")
Thanks in advance
------------------------------
Matthew Raleigh
Thermo Fischer CRG
Sr. IT COMM Eng.
Original Message:
Sent: 08-25-2023 08:04
From: Jan Heinonen
Subject: Web Messaging - End-User can Clear the Conversation
Hi Vaun,
You would do something like
Genesys("subscribe", "MessagingService.conversationCleared", function({data}){ /* Add code here */ Genesys("command", "Database.set", { messaging: { customAttributes: { name:"John Smith",account:"abc123"}}});});
------------------------------
Jan Heinonen
Contact Center Specialist
GlobalConnect AB
Original Message:
Sent: 08-25-2023 00:10
From: Vaun McCarthy
Subject: Web Messaging - End-User can Clear the Conversation
Thanks Angelo, that does make sense.
Can you please clarify if I'm understanding things right in that we'd replace the function({data}) part of your example with something like:
|
Genesys("command", "Database.set", { messaging: { customAttributes: { name:"John Smith",account:"abc123"}}}); |
|
------------------------------
Vaun McCarthy
Original Message:
Sent: 08-24-2023 04:00
From: Angelo Cicchitto
Subject: Web Messaging - End-User can Clear the Conversation
Hi Vaun - the idea behind this feature is to reset Messenger to its original state, to ensure privacy for End-Users. In your case I'd suggest to rebuild the necessary custom attributes object by subscribing to the corresponding MessagingService.conversationCleared event and adding the necessary logic to the promise fulfilled callback function.
Genesys("subscribe", "MessagingService.conversationCleared", function({data}){ console.log(data);});
------------------------------
Angelo Cicchitto
Genesys - Employees
Original Message:
Sent: 08-23-2023 22:34
From: Vaun McCarthy
Subject: Web Messaging - End-User can Clear the Conversation
Hi Angelo
A hiccup we have here. If the initial messaging session had database.set attributes sent through, those are obviously wiped out upon clearing the conversation. This means when the end-user tries to start a new conversation, the data items are missing. In most cases those are required for the flow logic. What thought has been put into this please?
------------------------------
Vaun McCarthy
Original Message:
Sent: 07-31-2023 07:57
From: Angelo Cicchitto
Subject: Web Messaging - End-User can Clear the Conversation
Hi everyone,
We are excited to announce the availability of Web Messaging - End-User can Clear the Conversation (see corresponding DIG-I-118 Idea here). This feature allows End-Users to Clear the Conversation, particularly useful on shared devices, to preserve End-User's privacy when conversation is completed. Additionally, to improve business efficiency, if the conversation is currently in Queue/Flow or answered by Agents, it will also be disconnected.
If you are interested, please sign-up by filling out the form below visible also in Beta HQ homepage, we'd love to get your feedbacks!
Web Messaging - End-User Clear - Beta Sign-up Form
After we enable the feature for your org, we will reach out to you to confirm: this may take a few days.
Thanks for your patience and interest!
#BetaAnnouncement
------------------------------
Angelo Cicchitto
Genesys - Employees
------------------------------