1. Incoming webhooks now can be represented in the chat list with an icon.

execute doc/update_db/update_287.sql for update

• Proactive invitation now have user initiated conversions https://doc.livehelperchat.com/docs/proactive#conversion

execute doc/update_db/update_286.sql for update

• Proactive invitations can have child invitation which works as A/B testing workflow.
  • Once you define a parent invitation. Present invitation is considered as child invitation.
  • Only main display attributes are taken as variation.
  • Parent invitation statistic window will show child invitation performance.
• Bot pause trigger. https://github.com/LiveHelperChat/livehelperchat/pull/1797
• Proactive invitation have two new options
  • Hide content on click - clicking it will close invitation without triggering widget open. E.g you have some sale running and want to share some code with users.
  • Custom on click event - in combination with above option can work as independent and just execute javascript on click.
• Users/Groups/Roles list/edit windows UX improvements. Sorts by module etc.
• Modifying department group will update it stats also now.
• Export CSV for survey option.

execute doc/update_db/update_285.sql for update

• Start chat form settings can be assigned to more than one department.
• Custom start chat settings can switch department from dropdown option.
• Left dashboard menu will show alert icons also. https://github.com/LiveHelperChat/livehelperchat/pull/1796
• Loading previous messages will pay attention to departments operator has access to. https://forum.livehelperchat.com/viewtopic.php?id=4139

execute doc/update_db/update_284.sql for update

Statistic saved reports can be send daily/weekly/monthly

execute doc/update_db/update_283.sql for update

1. Reports various fixes.
2. Now you can save report for future reference.

execute doc/update_db/update_282.sql for update

1. Optional reactions to bot messages. https://doc.livehelperchat.com/docs/bot/bot-text#reaction-options
2. Replaceable variables activity period.

execute doc/update_db/update_281.sql for update

1. Bot messages can be automatically translated using Translation services.
2. Passed additional chat variables will prefill nick, email, phone.
3. Visitor now can switch his language in the widget.
4. Alert message will be shown if department groups permission is misconfiguration. Operator can edit them, but can't read.
5. Option to clone replaceable variable.
6. Now as admin I can edit more fields of the operator.
7. Files upload UX fixes. Messages not always was fetched after files upload.

execute doc/update_db/update_280.sql for update

1. Additional chat columns can be sorted [Pending chats, Active chats] widgets supports

execute doc/update_db/update_279.sql for update

Now there is an option to assign operator to department/department group and at the same time exclude him from auto assignment workflow.

E.g You have operators who works only with VIP department, but when they don't have much to do they want to accept chats manually from lower level departments. With that option you can do that.

• VIP Department chats will be auto assignment.
• But lower level chats they would need to take manually.

execute doc/update_db/update_278.sql for update

1. You can have custom keyboard shortcuts for bot commands.
2. Commands now have --silent and --update_status options. Read about them on documentation.
3. Using above new features you can have a custom chat close shortcut add subject etc... Unlimited options.

execute doc/update_db/update_277.sql for update

1. We will be able to read variable passed like this. In additional chat variables Old way passed variable name just enter username. This will improve compatibility with older embed codes.

LHCChatOptions =
  {
      "attr_prefill": [
          {
              "name": "username",
              "value": "remdex"
          }
      ]
  }

2. {args. will be supported in canned messages and canned messages replace variables. E.g {args.chat.chat_variables_array.player.firstName}
3. Various small bugfixes.

execute doc/update_db/update_276.sql for update

1. Option to save bot response as template or quickly copy from another trigger.
2. Option to save trigger events as template.
3. If widget theme was used and theme has an image it should override bot logo.

execute doc/update_db/update_275.sql for update

1. Visitors can download now chat as txt file. Can be turned off in the chat configuration.
2. Bot quick reply buttons now have option to set custom css class and icon content. Usefull while developing custom theme and using custom font.
3. Survey widget state will have an operator profile shown.
4. Various small changes for the widget modal windows. Paddings, button styles.
5. Mobile app was not transferring chat to another operator.
6. More CSS classes for widget elements to override them with custom CSS.

execute doc/update_db/update_274.sql for update

1. Option to skip event listener.
2. Custom event for Rest API call for external logging.

execute doc/update_db/update_273.sql for update

1. Option to cache Rest API request. Usefull if Rest API behaves just as intent, sentiment analysis because responses are always the same.

1. Message aggregation for sentiment analysis per message implementation.
2. Small security fix
3. Possibility in statistic group by operator

1. Search by phone.
2. Security fixes. Update highly recommended.
3. Improvements to dashboard request frequency.
4. Edge case widget hide/show scenario fixes. Was not possible to close proactive invitation if status widget was acting as close button.
5. Operator will be in text grey (online operators widget) if he can't write to any department assigned.
6. Visitor hold option. You can pause auto responder for the visitor not replying if you know that visitor will take time looking for an info.
7. Delete action should wait until request is done.
8. Mobile app supports live online/offline status monitoring.
9. Dashboard left column will be always visible in any other page of LHC. Possible to hide/show it.
10. Admin chat interface will render presented buttons for the visitors.
11. Audit log list will have a quick view option as modal window.
12. Audit log will store all messages as JSON if not a string passed.
13. Online operator counter in the online operators widget. Will show exact number of operator whois online and has write permission.
14. More complex secrethash value generation during install. I would suggest for existing installation just write it quite long complex string with various special characters.

execute doc/update_db/update_269.sql for update

1. Proactive chat invitation now supports multiple departments assignment
2. Proactive invitations now can filter directly online_attr_system key and values

execute doc/update_db/update_268.sql for update

1. Proactive chat invitation dynamic conditions.
2. Messages auto scroll to reply position fixes.
3. force_logout attributes support for Rest API.
4. Highlight currently opened chat.
5. Permission to allow/deny operator visitor IP

execute doc/update_db/update_267.sql for update

1. Block by online user. Basically it means a cookie based block. Online visitor tracking has to be enabled.
2. Widget will automatically adjust width, height on desktop devices.
3. Proactive invitation now can be expireable.
4. Online visitors widget will show read only departments groups.
5. If chat has remarks from previous chats tab will be highlighted.
6. Referer was passed incorrectly in so circumstances.
7. Security fixes
8. Added icons from the bot now is transaction wrapped.
9. In some cases Live Helper Chat did not returned correct data for mobile app.
10. Canned messages statistic tab will have more export capabilities.
11. If operator takes over a chat, we should terminate any previous information collection workflow.
12. Some refactoring to remove php-session dependency for anonymous visitors.
13. Proactive chat filter in chat list.
14. Commands should not be executed in whisper mode.
15. Subject add/remove events.

execute doc/update_db/update_266.sql for update

1. Missing indexes fixes in some tables.
2. Whisper mode for the operator. We will go automatically to whisper mode if operator is not a chat owner.
3. Status widget icon fix in chrome https://github.com/LiveHelperChat/livehelperchat/issues/1733
4. JS API improvements for CloudTalk extension
5. Operator concurrent chats support while viewing specific chat. You can see how many other chats operator were having.
6. PHP-Resque in some situations were missing chat object.
7. And many other small changes

execute doc/update_db/update_265.sql for update

1. In progress trigger option. This is usefull in case previous process has not finished yet. Mostly use case with custom extensions.
2. Users sometimes were logged out just after login if they were using auto logout after some interval.
3. I have started a progress to remove old legacy widget code from the app.
4. On password remind function show identical message in all cases to avoid scanning for existing customers.
5. Further PHP 8.1 fixes.
6. In statistic section now you can differentiate proactive chats was it manual invitation or automatic.
7. In case PHP-Resque was used and incoming webhook events were not send to Rest API
8. Get rid of document.write for a new widget to avoid warning.
9. jfif support as image format.

execute doc/update_db/update_264.sql for update

1. Survey API. See a swagger survey section.
2. Fix tricky case if manager is monitoring a chat and chat being transferred to him, chat was not auto accepted. It will be now.
3. Mobile app now supports android notifications categories.
4. Further 8.1 PHP support improvements.
5. System tab will be remembered now on refresh.
6. If proactive invitation is used with bot append option we should not show next time invitation once a visitor closes it.
7. SVG Cleanup on upload for security reasons.
8. Operators statistic directly in online operators widget.
9. Department statistic link directly in pending/active chats widget.
10. CSRF token for logout link.
11. We now have zoom image option directly in the chat widget.
12. Pre chat conditions.

execute doc/update_db/update_263.sql for update

Widget theme table columns type changes. On some MySQL servers, it was returning that row size to big.

execute doc/update_db/update_262.sql for update

1. Canned messages can be disabled now.
2. Further 8.1 PHP compatibility fixes

execute doc/update_db/update_261.sql for update

1. Theme alias and Department alias.
2. PHP 8.1 compatibility fixes

execute doc/update_db/update_260.sql for update

1. New trigger response type. Log action usefull in case you want to store historical chat actions.
2. Canned messages can have activity period. E.g some messages can be active during christmas period or just morning hours.
3. Chat export has more prefilled variables.
4. While sending manual message to online visitor it's possible to ignore bot.
5. Online hours operators statistic now has seconds filter.
6. Improved older PHP versions support.
7. PHP-Resque replaceable variables where lost during trigger process events.
8. Hide block by nick if visitor nick is "Visitor"
9. Large inactivity timeout values and custom permission to use them.
10. Region/State detection improvement for chats.

And many other changes all around

execute doc/update_db/update_259.sql for update

1. Rest API access can be restricted only to Rest API keys.
2. Rest API keys themself can have IP restrictions
3. Bot Rest API call default trigger can execute selected trigger only one action.
4. Output parsing in Rest API calls, now can have two conditions.

1. There is new event you can fire to trigger google analytics events directly from custom HTML of your widget.
2. Now you can explicitly control what one operator can change in other operator departments. https://doc.livehelperchat.com/docs/users/account-edit
3. In password change requirements you can force users to logout after certain period of last login.
4. You can automatically disable operator if from their last login passed X number of days.
5. In password requirements you can set bunch of other requirements for the password.

execute doc/update_db/update_257.sql for update