Hi Alder, I will check later if this is found from documentation, but now it's just easier to write from my (RAM 😁) memory. Let me split this one to two chapter for easier reading, please consider Communication Panel for pre-requisite for both: 1. Social Channels via Conversation API - For back-end you need Chat Server and SMS Server. Here SMS Server is the gateway that receives and sends the messages, while Chat Server is parsing, routing and adapting to Contact Pro protocol. - SMS Server should be set to HTTP mode in SC -> Modules and restarted. - After that follow Configuring Sinch Conversation API - Additionally you should allow http traffic from and to SMS Server component 2. Contact Pro Webchat and also Chatlayer or any other chatbot integration - For back-end you need Chat Server and ECF in visitor mode. The ECF in visitor modes differentiates from agent mode so that access to internal resources such as RI or authentication is blocked. In other words more safer to be published towards internet. - Once you have ECF Visitor set up and IA variables defined, then browse to http(s)://visitor url/latest/VisitorConfigurator/index.html and start building your chat app. It should fetch automatically queues in the system based on your user rights. - Of course you need to open connection from internet to ECF Visitor IP. We can take the firewall opening in separate, once you have set up the needed components and you are able to play with it in internal network. You may also consider if you want to enable Contact Pro webchat at all, because in Conversation API stack there is Sinch Chat available which has video and call capability over the chat. Currently we recommend the Sinch Chat over Contact Pro Webchat. If you wish to have a discussion about differences, please ping me in email. With that you should get started and feel free to reach us if any questions. BR, Jukka
... View more
