Yes, many.
1. I doubt Einstein chat bot can create API call into guest messaging API.
2. Authenticated Messaging is probably impossible or highly unlikely.
3. Context from bot (transcript) requires a JSON array, so most likely not probable.
4. Einstein could not use GCx Knowledge Workbench or enterprise KMS like Shelf.io
5. Passing skills and routing and user information would be through a single attribute.
If it were me, I would go with a Boy Connector to Einstein. Check out the Blueprint for Watson and do as the Chinese R&D do - replicate and duplicate.
------------------------------
Robert Wakefield-Carl
Avtex Solutions, LLC
Contact Center Innovation Architect
https://www.Avtex.comhttps://RobertWC.Blogspot.com------------------------------
Original Message:
Sent: 08-27-2022 17:52
From: Vaun Mccarthy
Subject: Anybody using external routing package for messaging with the Genesys SF integration also using Bot Flows?
Just wondering if there are any gotchas with having a Bot Flow run iniitally before the handoff to the queue=>agent=>SF Omnichannel? Have people stuck with having the bot in this scenario be an Einstein driven one?
#ConversationalAI(Bots,AgentAssist,etc.)
#Integrations
#Omni-ChannelDesktop/UserInterface
------------------------------
Vaun Mccarthy
------------------------------