New features and enhancements#

Prevented unintended actions when pressing Enter in webchat#

#KR-10528, #enhancement, #livechat

Improved the webchat input behavior by ensuring that pressing the Enter key to send a message does not trigger unintended actions on the host website (such as opening new tabs like). With this enhancement, keyboard input within the chatbot is now isolated from the parent webpage, preventing conflicts with underlying site functions. This results in a smoother and more predictable user experience, especially for webchat embedded on client websites.

Added customizable next/previous button symbols for card carousel#

#KR-10531, #enhancement, #editor, #contentnode, #carousel

Introduced a new optional setting that allows clients to customize the next/previous navigation buttons in card carousels. Instead of using the default arrow icons, clients can now replace them with custom text or symbols (e.g., “Next” / “Prev”).

This enhancement provides greater flexibility in UI design, allowing businesses to better align the carousel navigation with their branding, language preferences, or accessibility needs, resulting in a more tailored user experience. Can access this one in Setting/Webchat

Enabled live chat notification sound without window focus#

#KR-10489, #enhancement, #livechat, #sound, #notification

Introduced a new setting to allow live chat notification sounds to trigger even when the dashboard window is not in focus. Previously, the notification sound depended on browser focus, which caused issues in environments like embedded dashboards (e.g., Webex) where focus detection is unreliable.

With this enhancement, clients can enable notifications to ring regardless of window focus, ensuring agents are alerted to incoming messages in all scenarios. This improves responsiveness and prevents missed chats, especially in multi-window or embedded use cases. Can access the setting in Setting/Webchat

Increased and made file upload size configurable in File module#

#KR-10570, #enhancement, #file, #sizelimit

Enhanced the File module to support larger file uploads and provide more flexibility in configuration. Previously, uploads were limited by a fixed 25MB restriction, which caused some files to be rejected. With this update, the upload limit is now configurable via the dashboard, allowing clients to adjust based on their needs. A server-side setting defines the maximum allowed limit (default 35MB, with support up to 50MB), ensuring both flexibility and control.

This improvement enables smoother handling of larger files, reduces upload failures, and enhances overall usability for file management.

Fixed multiple CVEs and compatibility issues in server and build process#

#KR-10567, #enhancement, #security

Resolved several security vulnerabilities (CVEs) and improved system compatibility by upgrading and patching key dependencies. This includes updates to critical libraries such as uuid, lodash, form-data, ws, and tmp to address known security risks.

Additional fixes were implemented to ensure compatibility with newer library versions, preventing build failures and runtime issues. Improvements were also made to the deployment process to ensure these fixes are consistently applied across environments.

Extended content node delay to support longer wait times#

#KR-10540, #enhancement, #contentnode

Enhanced the Content Node functionality to support longer delay durations between messages, beyond the previous 60-second limitation. This allows clients to design more flexible engagement strategies, such as retargeting users after a meaningful time gap.

With this improvement, businesses can now introduce delays of extended durations (e.g., 30 minutes) within chatbot flows, enabling follow-up messages to re-engage users who may have previously declined an offer. This removes the need for workaround loops, which previously caused errors due to system limitations.

This enhancement supports more advanced use cases like re-engagement campaigns, timed nudges, and personalized follow-ups, helping improve conversion rates and overall customer engagement.

Added support for WhatsApp Usernames (BSUID) for message handling and tracking#

#KR-8359, #new-feature, #whatsapp

Introduced support for WhatsApp Usernames (Business-Scoped User IDs - BSUID) to align with Meta’s upcoming global rollout. As WhatsApp evolves beyond phone-number-based identification, users may interact with businesses using usernames instead. This change is critical, as businesses that do not support BSUID risk missing messages from users who adopt this feature.

With this enhancement, the platform is now capable of capturing, storing, and mapping BSUIDs from incoming message webhooks. This ensures that user identities remain consistent across interactions, even when phone numbers are no longer the primary identifier. The system is also prepared to support both test BSUIDs (from February 2026) and actual BSUIDs (from March 2026 onward) as part of Meta’s rollout timeline.

This update directly supports key business scenarios such as:

• Session messaging (reactive conversations) where accurate user identification is critical
• Click-to-WhatsApp Ads, ensuring leads and conversations are not lost due to identifier mismatch

By enabling early adoption of BSUID mapping, clients can maintain uninterrupted communication, improve user tracking across channels, and ensure compliance with WhatsApp’s evolving platform requirements. This positions the platform to seamlessly support future messaging standards while minimizing operational risk during the transition.

Bug fix#

• [#KR-10521] Fixed inconsistency in content styling between Widget and Monitor views
• [#KR-10574] Fixed Marker-Checker rejection reverting to original instead of last approved version
• [#KR-10569] Fixed missing typing indicator for Facebook Messenger chats