New features and enhancements#

Stop a button being tapped twice#

#KR-10818, #enhancement, #webchat, #editor, #contentnode

Website buttons that open a popup window — a Singpass authorisation flow, for example — now have a "Disable after click" option. With it switched on, the button greys out as soon as its window opens, so a visitor cannot start the same external flow a second time while the first one is still in progress. Only that button is affected; the others in the message keep working as normal. The option is off by default, so nothing changes until you turn it on for a specific button.

Send WhatsApp stickers from live chat#

#KR-10679, #feature, #whatsapp, #livechat, #dashboard

Agents can now send stickers in WhatsApp conversations. A new sticker library in the dashboard lets you upload, rename, search, and enable or disable the stickers your team can use, and agents pick from that library directly in the live chat composer. Stickers sent by customers and by your agents both render as proper images in the conversation, in monitor views, and in chat history. This builds on sticker viewing introduced in 34.12.2.

WhatsApp external API now available under the Developer module#

#KR-7054, #enhancement, #whatsapp, #api

The WhatsApp external API — bulk sends, send monitoring, message templates, and media upload — is now also exposed under the Developer module. Calls made through the new endpoints gain everything the Developer module provides: inbound and outbound traffic visible in the dashboard monitor, rate limiting, duplicate-request protection, and a choice of authentication methods (a developer API key or the existing WhatsApp authentication). The original endpoints keep working exactly as before, so existing integrations need no changes.

Keep returning-visitor sessions separate per app source in webchat#

#KR-10901, #enhancement, #webchat

Deployments that serve several bots from a single domain — for example one page per institution — can now keep each bot's returning-visitor session separate. A new webchat setting, "Separate resuming session by App Source", means a visitor who opens a second bot on the same domain no longer overwrites the first bot's session, which previously allowed one institution's context to appear in another institution's conversation. The setting is off by default, so existing behaviour is unchanged until you enable it.

A more prominent webchat message box #

#KR-10837, #enhancement, #webchat

The webchat message box now receives the cursor automatically whenever typing is allowed — when the widget opens, when a menu that was blocking typing is dismissed, and after each bot reply — so visitors can start typing straight away. This applies on desktop only, to avoid popping up the mobile keyboard. The "Type a message…" placeholder is also darker and easier to read by default, and its colour is now configurable. Both behaviours can be adjusted in the webchat settings.

Central control over allowed attachment types and sizes#

#KR-10614, #enhancement, #security, #webchat, #livechat, #dashboard

The file types and maximum size allowed for general attachments — visitor uploads in webchat, agent uploads in live chat, and dashboard File Storage — are now governed from one place in the Core module settings instead of being fixed separately in each feature. You can restrict your deployment to only the formats your users actually need, reducing the risk of malicious file uploads, and all three upload paths stay consistent. Purpose-specific uploads such as CSV imports, avatars, and certificates keep their own built-in restrictions.Stronger protection for file uploads

#KR-10590, #enhancement, #security, #webchat

Following the move to secure, temporary file links in 34.12.2, the older upload route that handed out direct write access to file storage is now switched off whenever the secure file proxy is enabled. Every upload is therefore virus-scanned and never exposes the underlying storage location. Deployments that do not use the proxy are unaffected.

Bug fix#

[#KR-10789] Fixed being unable to filter abandoned and monitor chats by content step
[#KR-9963] Fixed WhatsApp bots gradually failing to reply as a conversation's history grew — GenAI responses now use the last 20 messages on WhatsApp
[#KR-11003] Fixed the approval page listing changes nobody had made — including, in some cases, an accidental rename of a content step that could break the conversation flow once approved
[#KR-11023] Fixed "Approve All" not publishing trigger and API changes and leaving them in the approval queue, and fixed bot import, export and delete not carrying trigger and API changes through to the live bot
[#KR-10708] Fixed live chats not auto-resolving when only one side of the conversation had replied and "skip having both interaction" was enabled
[#KR-11039] Fixed WhatsApp message status updates (sent, delivered and read) being reported twice to connected systems — each status is now reported once. Recipients were never affected and always received a single message.
[#KR-10982] Fixed agents being switched to Offline while they were still working, and the supervisor's agent overview showing zero agents when it failed to load
[#KR-10945] Fixed members who took their time answering the post-chat survey losing the feedback they typed and being handed back to a live agent instead of seeing the thank-you message