Hi Chad ,
I did raise a ticket with care and they were able to simulate same issue on their setup as well . Your analysis was correct , even though agent side of cobrowse session ends , but customer side of cobrowse sessions remains open for 2 days , leading it to showing it as a live interaction for 2 days in the system .
We made some workaround on customer website to overcome this challenge , but i would suggest you to change this aspect of cobrowse , as to me it looks like a limitation . If the agent side of cobrowse session has ended , logically cust side of cobrowse should end too and should be marked closed in the system (as customer alone can't stay on a cobrowse session ).
Let me know of your thoughts on this .
Thanks & Regards,
Garima.
------------------------------
Regards
Garima.
------------------------------
Original Message:
Sent: 03-05-2024 08:39
From: Chad Hansen
Subject: AMA - Co-browse for Voice questions (ask here)
Hi Garima!
This does sound a bit unexpected. Would you mind opening a case with Care and include a conversation id or two where this has occurred? From the description, it's hard for me to say exactly what's going on, but it sounds like the Co-browse portion of the voice interaction is never disconnecting from the customer.
For what it's worth, the Request Navigation function is intended to be used to navigate to another page of the brand's website where Messenger is deployed. This would not include external links to an MS Teams or Zoom conference, I suspect that's where this hiccup might be occurring on the conversation.
------------------------------
Chad Hansen
Product Manager
Genesys - Employees
------------------------------
Original Message:
Sent: 03-05-2024 04:36
From: garima balodi
Subject: AMA - Co-browse for Voice questions (ask here)
Hi Matt,
I am using the cobrowse with voice via web messenger (latest one released on 14th feb ). After a cobrowse session is established ,-> agent requests navigation to a third party like MS Teams meeting link , or zoom link -> both agent and cust connect via that session (while the voice channel still remains on , for adherence purpose in wfm ) . All these calls are shown awkwardly in reporting. Such calls ,while getting ended properly and on time , but are shown as 'live' for a couple of days in performance interaction views. What could be the reason for these awkward reports ?
Regards
Garima.
------------------------------
Regards
Garima.