Indeed, trying to model a social interaction (asynchronous by nature) via Guest Chat emulation (synchronous by nature) likely explains the inconsistency: we would recommend Open Messaging for integrations purposes.
Original Message:
Sent: 02-19-2024 11:48
From: Robert Wakefield-Carl
Subject: Disconnect reasons confusion on Social
So, your social platform is using Guest Chat? I would suggest they implement the Open Messaging instead and bring their conversations in over that as their own provider. In fact, they could have different providers for the different platforms or types.
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 02-19-2024 03:06
From: Karl Beal
Subject: Disconnect reasons confusion on Social
Hi Robert
The app we use from the AppFoundry for social within Genesys classes social as chat rather than messaging.
Thanks
Karl
------------------------------
Karl Beal
Severn Trent Water
Original Message:
Sent: 02-17-2024 23:38
From: Robert Wakefield-Carl
Subject: Disconnect reasons confusion on Social
So, Messaging being asynchronous can have timing issues like this. The conversation stays open for 72 hours as an active session. Supposed the agent ends the conversation and then later on, the customer ends the conversation. That is probably what you are seeing. If either of them continues the conversation in that 72-hour period, it is not really ended. I would assume you case the agent disconnected and then later on the customer also ended by either using the trash can or not responding to the original response from the agent. @Angelo Cicchitto, is that about right?
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 01-16-2024 08:39
From: Karl Beal
Subject: Disconnect reasons confusion on Social
Hi
I have a social conversation an agent is saying it just randomly ended.
Genesys shows:
Internal Participant(s)
Disconnect Reason: Peer
External Participant(s)
Disconnect Reason: Client
Ive looked at Disconnect reasons in the interaction's detail view - Genesys Cloud Resource Center
However I still cannot work out who ended it.
Interaction timeline shows Disconnect type: Peer.
With this being social, a customer cannot hang up, unless they delete their account or block us?
#DigitalChannels
------------------------------
Karl Beal
Severn Trent Water
------------------------------