• Widget will remain opened/closed across pages domain/subdomains. Widget will load chat instantly if chat is started on another tab of the same page.
• If NodeJS is used and chat is started on subdomain it will continue on all subdomain of the main domain.
• On page reload widget will avoid flickering while loading main widget components.
• Inline form will have a check to avoid it being submitted after chat was closed.
• Widget sounds settings will remain the same across the domain/subdomain navigation
• It's possible to mask sensitive information before it sending to Rest API endpoint. https://doc.livehelperchat.com/docs/bot/rest-api#magic-prefixes-for-replaceable-variables
• Bot log will log much more events and is usefull for bot debugging. It's activated in department edit. Log will appear in audit log.
• Markdown standard link support for better ChatGPT support.
• Rest API debug enhancement options. https://doc.livehelperchat.com/docs/bot/rest-api#audit-log
• If initial intro message was long, we did not scrolled to the bottom as we should.
• If `'lhaudit','see_audit_system'` permission was not set, operator will not see Rest API messages logged in the chat.
• Now it's possible to block third party chat from incoming webhooks.
• Sub URL has magic prefix `urlencode_` to encode elements in the query. https://doc.livehelperchat.com/docs/bot/rest-api#sub-url
• Option to disable mail ticket closed for some of the mailbox even if customer e-mail matches few of the tickets.
• Option to choose to show bot profile in widget theme.
• Maintenance mode improvements.
• Stream as HTML support for Rest API calls.
• Simple search for personal canned messages.
• In triple quotes sometimes code was parsed as a code. We should not parse anything in triple quotes.
• Improvements in explanations for e-mail messages.
• In department list you can search by department alias.
• Now it's possible to define multiple work periods in the single day.
• Updated to React 18 widget.
• Brand new text editor for the operators. Can be activated in the dashboard settings.

For update just follow standard update procedure. No database update needed this time.