Two things come to mind - real estate and territory. With embedded clients, there is not much room for other features without popping out a window and if you have to do that, you may as well use a different product for the internal chat. Second, most companies are standardized on a UC platform with chat already like Teams, Slack, or even Zoom, so IT and management have a hard time justifying use of another chat product. That is why Genesys added a permission for Chat to turn off that feature completely when not required. Also, until there is chat capabilities between Teams and/or Slack, there is little likelihood that the contact center wants to silo themselves inside of Genesys for internal chat.
------------------------------
Robert Wakefield-Carl
Avtex Solutions, LLC
Contact Center Innovation Architect
robertwc@avtex.comhttps://www.Avtex.comhttps://RobertWC.Blogspot.com------------------------------
Original Message:
Sent: 02-13-2022 23:14
From: Vaun McCarthy
Subject: Agent Asssistance (Internal Chat) etc within Embedded Clients?
Hi guys
What are you doing to get around the limitation where the embedded clients (Salesforce, Chrome etc) don't support internal chat? This is something that one of my orgs uses quite frequently but at the moment it seems like if we want to move them to an embedded client they'd need to still have a separate browser tab logged in under a second session.
There's an idea on aHa that's been sitting there for over 2 years now to add it but there's only a dozen or so votes on it. Is this because most of your org agents don't use it at all or they're just using something like Teams outside of Genesys?
#Ask Me Anything (AMA)
#Implementation
#Omni-ChannelDesktop/UserInterface
------------------------------
Vaun McCarthy
------------------------------