Handling department status changes in Web Widget (Classic) can be managed using thechat:departmentStatus
callback. This allows you to apply specific settings based on the department's availability.
For example, if a department named 'CRM' is online, you can enable chat settings for that department. Conversely, if the department is not online, you can suppress the chat or apply alternative settings like a contact form. This ensures that the widget's behavior aligns with the department's current status, providing a seamless experience for users.
You can modify the Web Widget (Classic) behavior using JavaScript APIs by applying specific workflows at different times. Some workflows should be executed when a department's status changes, while others should be run when the widget first…
The timing of applying widget settings in Web Widget (Classic) API workflows is crucial. Some settings should be applied when a department's status changes, while others should be applied when the widget first connects or reconnects. For instance,…
Thechat:connected
callback in Web Widget (Classic) is best used for commands you only wish to execute once. This is ideal for initial setup tasks that should not be repeated every time the widget reconnects. If you have commands that need to be…
Hiding the Web Widget (Classic) on page load is not strictly necessary, but it can be part of your workflow if desired. The initial steps of hiding the widget and then showing it when an unread message appears can be omitted without affecting the…