This article will help you setup and troubleshoot both audible and visual notifications.
Browsers, with Google's Chrome being at the forefront, have become significantly more limited in what sites can automatically play audio. Autoplay is defined as any audible tone coming from the browser that is not directly initiated by a user action on that website. While noble, their intent was to block the auto-playing of unwanted advertisements. Unfortunately, they did not take in to consideration the browser as a communication metaphor.
As evidence, one of the rules now dictating playing audio indicates that unless the user "interacts" with a web page since its last refresh (which includes any of shutting down the computer, restarting the browser or manually refreshing the page), the browser window will not play a sound from that page until a user action is performed on that page. While we lobby browsers to make provisions for addressing, here's what you should need to do to get your browsers to "ring":
This means that after the Ramble portal loads, you need to click inside the portal in some manner for you to indicate to your browser, "I'm ok to play audio." Once you click inside audio should play, regardless of the future browser state (focused, not-focused or even hidden).
Allowing Visual Notifications
Visual notifications are critical to being able to answer chat requests in a timely fashion. In combination with audio notifications, visual notifications provide the perfect metaphor for allowing you to disturb your regular work only when a visitor chat request is made. To make sure that you're able to receive visual chat notifications, please follow the steps that correspond to your browser.
Within Chrome, open a new tab and paste this link: chrome://settings/content/notifications?search=notifications. Alternatively, press the Menu icon in Chrome (the three vertical dots) and select Settings. Scroll down to the bottom of your Settings page and open the Advanced section. Scroll down and select the Content Settings tab in the Privacy and Security section.
Select 'Notifications' to see which sites are allowed (bottom) or denied (top). Disabling the feature will stop sites from popping up alerts. Unfortunately, that means notifications you do want will not be shown unless you decide to toggle the notification settings for each site you find yourself visiting. To turn the feature off entirely, toggle the "Ask before sending" setting to "off."
To confirm Ramble has authority to send browser notifications, navigate to your security settings. Hit the menu icon and select Options, then select Privacy & Security. Scroll down to the Permissions section and select Notifications Settings icon. Find Ramble and, if not already, enable it to allow notifications.
Hit the menu icon in the top right and select Settings. Scroll down to Advanced Settings, then select Website permissions. There you can toggle on notification permissions for individual websites, including Ramble.
Safari does not yet support the push API for browser notifications.
Troubleshooting Visual Notifications
If you have allowed notifications and are still not seeing visual them, please attempt a hard refresh (Hard Refresh Instructions) of the Ramble portal and click within the page.
Ramble Visual Notification Examples (3 Scenarios)
Scenario A) The user's Chrome browser is focused and is displaying the Ramble Portal in the active tabRamble will show a notification like the screen below in the bottom left while Chrome will not show a browser notification (see B) and C) to understand more).
Scenario B) Chrome browser is focused but a tab other than the Ramble portal is currently displayingChrome will show the notification in the upper right.