Step one: we’re ditching the default web messaging widget for a custom UI built on the WebSocket Guest API. The idea is to handle startConversation manually instead of relying on the pre-built SDK. I’ve got the initial handshake working on wss://webchat.genesyscloud.com/v1/guest, but the server kills the socket right after the first ping frame. Close code is 4001. The JSON payload looks clean: {"type":"chat","conversationId":"abc123"}. Running genesyscloud-messaging-sdk v1.2.0 in the browser. Logs just stop.