Receive desktop notifications for connect chatDescriptionTo be able to receive desktop notifications for Connect Chat, the below settings needs to be enabled. The settings would also work for chats initiated by an end user using the Connect Chat Queue url. ServiceNow has officially announced the deprecation timeline for Connect Support. These plugins will no longer activate or support, as of two upcoming Now Platform® releases. Beginning with the Now Platform San Diego release in March 2022, we will no longer deploy or activate the plugin listed below. The plug-in will remain active in your instance, including when you upgrade to a new Now Platform release Beginning with the Now Platform Utah release planned in March 2023, we will end support for the plugin listed below. While they will remain active in your instance, including when you upgrade to a new Now Platform release, we will not be able to service them. Affected Plugins - Connect Support Plugin: com.glide.connect.support Release or EnvironmentAll currently supported releases. Orlando, Paris & QuebecResolution1) The "Send me desktop notifications" option is selected to true "For all activity" from under the Notification Preferences menu in the Connect chat. 2) From the Setting options in the top right corner on the instance home screen, under "Notifications" section, the "Connect desktop notifications" option is enabled. In Madrid, you need to click on Notification > Under Notification by Category search for Connect > Enable all the the options under ALLOW CONNECT NOTIFICATIONS. Follow the steps below to enable notifications on Madrid & New York instances, 1. Set the allow notifications to true. 2. Scroll the NOTIFICATIONS BY CATEGORY section and go to Connect 3. Select all the options under ALLOW CONNECT NOTIFICATIONS Once both the above settings are done, you would be able to receive the alert for any new Connect chat message even when the chat is running in the background or even if the ServiceNow window is altogether minimized, as shown in the below screenshot: You would be able to see the name of the user who sent the message, the message content and your instance URL. Additionally, you can check the site setting on Chrome and validate that the below permissions are allowed.- Notifications- Pop-ups and redirects- Sound If these are not enabled for the instance, then follow the below steps:* Set the permissions to allow* Clear browser cache completely* Close all browser windows* Relaunch the browser and login to the instance.Additional InformationMake sure to check with the browser notifications settings (Chrome) It should allow notifications from your ServiceNow instance. On your computer, open Chrome.At the top right, click More Settings.At the bottom, click Advanced.Under "Privacy and security," click Content settings.Click Notifications.Choose to block or allow notifications: When on normal portal page, end user will not get any notification for a chat.When on portal, user will get sound notification for a 1 - 1 chat, but they cannot join the chat. 3. To join the chat the user will have to go back to native UI. If the above steps still don't show the Connect Desktop Notification: Clear the complete browser cache, and close all browser tabs.Allow pop-ups and notifications in the browser for your instance. For Chrome: For Firefox: Additional KB on Connect Chat: KB0760394 - Connect Support needs a manual refresh for incrementing chat count on AMB recoveryKB0760090 - Manual browser refresh is required when users's session times out and user re-logs into the system, to receive new AMB updates. This cause connect chat queues not getting updated for agent.KB0695952 - Queue number or chat messages are randomly or intermittently not updating in Connect but show after a refreshKB0677335 - Connect Chat Performance Issues: Overview and Best PracticesKB0634397 - FAQ for Connect Chat and Connect SupportKB0622691 - AMB (Asynchronous Message Bus) - an Architectural Overview