Desktop Notifications (Browser Push Notifications)

Desktop Notifications

Desktop notifications are extremely convenient if you're working in the Re:amaze dashboard on a modern web browser such as Chrome, Safari, or Firefox. When customers message you or reply to you, Re:amaze will send a notification to you via your browser. If you're using a Mac OS or Windows based computer, these notifications will be stored in the notifications center. You can also refer to this article for more about how this works.

We always recommend to enable desktop notifications as soon as possible when you start to work in your Re:amaze account.

Alt Text

Issues With Desktop Notifications

It's not uncommon for desktop notifications to not turn on upon initial setup or fail after a certain amount of time has elapsed. To self diagnose these problems, follow the instructions below:

  1. Go to the Notification Settings in your browser and remove any reamaze.com related domains from the allowed list. This should tell your browser to stop allowing notifications from reamaze.com domains.
  2. Alternatively, you can click the "lock icon" next to the URL in your address bar and go to "Site Settings". Once you're there, click the "Reset Permissions" button.
  3. Then, close the browser and open it, this time go to the Settings > Desktop Notifications page and follow the steps to allow notifications again. Doing this should force your browser to issue a new notification token to Re:amaze.

Please confirm that you have notifications enabled at the operating system level.

  1. Go to Notification Settings. On Windows, this is in the control panel and on Macs, this is in the System Settings app.
  2. Make sure Chrome has permissions to receive push notifications.

Still not working?

  1. Make sure Chrome has notification permissions on your operating system. On either Windows or Mac, you should find this under Notifications Settings to see which apps have notification permissions. Make sure Chrome is one of the apps.
  2. Make sure you've reset our permissions. Go to Notification Settings in Chrome. First take away permissions for Re:amaze's domain and then re-approve permissions by going to Settings > Desktop Notifications.

Lastly, if everything there is set, we can help diagnose the problem further if you can open your Chrome, Safari, or Firefox developer console and take a screenshot of the results after you run this script:

navigator.serviceWorker.ready.then(function(t) {
  try {
    t.pushManager.subscribe({
      userVisibleOnly: !0,
      applicationServerKey: new Uint8Array([4, 212, 100, 103, 5, 151, 151, 64, 77, 142, 58, 0, 58, 232, 15, 36, 234, 224, 95, 73, 239, 30, 183, 163, 161, 69, 32, 108, 101, 205, 238, 55, 29, 26, 38, 140, 208, 167, 234, 11, 88, 161, 255, 115, 60, 244, 241, 225, 188, 248, 133, 151, 26, 225, 39, 180, 184, 238, 171, 221, 145, 238, 135, 255, 219])
    }).then(function(t) {
      try {
        console.log(JSON.stringify(t.toJSON()));
      } catch(e) {
        console.log("Caught exception getting subscription token")
        console.log(e);
      }
    }).catch(function(e) {
      console.log("Caught exception getting subscription token in promise")
      console.log(e);
    })
  } catch(e) {
    console.log("Caught exception subscribing")
    console.log(e);
  }
})