Today, when the Botpress Cloud webchat loses its websocket connection, the chat window displays a hard “Disconnected” error message, requiring the user to refresh the page. For customer-facing use cases, this creates the impression that the chatbot is broken, even during short or recoverable network hiccups. Proposed improvement: Keep the chat visible and preserve conversation history during temporary disconnects. Show a small non-intrusive status inside the chat (e.g., “Connection lost – attempting to reconnect…”). Implement automatic reconnection attempts (e.g., exponential backoff). Only prompt the user to refresh if reconnection fails after a defined threshold. Benefit: This would prevent customers from seeing disruptive error messages and make the webchat feel more reliable and professional in production environments.