Record Change Notification on Unfocussed Browser Tab in Microsoft Edge
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Is anyone aware of a product capability that will create a notification (or some form of visual cue) on an unfocussed browser tab when a change to a record occurs on the platform?
I use Provider Notifications to alert the agent in the Next Experience UI (e.g. in the CSM Workspace) when a Case record they are assigned to has the Needs attention field updated to true. This is suitable for the scenario when an agent is constantly using the ServiceNow platform and always has that tab of their browser selected.
The scenario I'm talking about is when the agent context-switches away and are doing something on another tab in their browser. If a Case record is updated while they are away from the ServiceNow tab (sometimes for many minutes), there's no obvious visual cue for them to know something has changed that may require their urgent attention.
I really want to avoid creating an email notification for this, so keen to know if others have come across something in this space.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Steven,
There is no out-of-the-box product capability for this, and it is worth understanding why, because it rules out a configuration fix:
Provider Notifications only render inside the Next Experience page itself. They do not use the browser's Web Notifications API, they do not change the ServiceNow tab's title or favicon, and they cannot raise an operating-system level alert. So when the agent is on another tab there is simply nothing in the ServiceNow page that Edge will surface to them - and Edge additionally throttles/suspends work in background tabs, so even polling-based visual cues in an unfocussed tab are unreliable by design.
What you can do instead, in order of preference:
1. Fix the "missed it while I was away" half of the problem in-platform: make this Provider Notification persistent, i.e. it stays / has to be acknowledged or dismissed rather than being a transient toast that disappears. The agent still gets no cue while they are on the other tab, but the alert is waiting in the header/notification list when they come back instead of having vanished during the minutes they were away. Combined with the workspace list/badge for assigned work, that is the supported pattern for Needs attention = true.
2. If the agent must be reached while they are genuinely outside ServiceNow, send the alert to an application that CAN raise an OS notification - a Microsoft Teams (or Slack) direct message from the same trigger, using the Teams spoke in Flow Designer. It is not email, it reaches a desktop/mobile app the agent is likely to have in front of them, and it can link straight back to the Case. Many teams end up here for urgent Needs attention events specifically because the browser tab cannot do it.
3. A true background-tab / OS notification from the ServiceNow tab itself would require a custom-built component using the browser Notification API (with per-user browser permission, Edge site notification settings allowed for your instance, and the tab still loaded) - it is not a configuration of Provider Notifications, and permission prompts plus background-tab throttling make it fragile for an agent-wide rollout.
So: no product setting will flash an unfocussed Edge tab - use a persistent Provider Notification for the return-to-tab case, and a Teams/Slack message if it has to interrupt the agent while they are elsewhere.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@kmohammed Thanks very much for that detailed response. Always best to ask first before making assumptions and going down the wrong path.
My initial consideration, if it wasn't achievable, was to leverage the Now Agent app and use a Push Notification to inform the agent that an update occurred on the record. That presumes the agent will use the app on their mobile device, but it keeps the notification "in the platform" (albeit with a slight trade-off that the agent needs to context switch to their mobile device). Not all of our agents are using the app as yet, so it may be less preferred than your second preference of using Teams - which all of our staff regularly use.
I do have a follow-up question regarding your first preference. It reads like you're saying that the Provider Notification can be modified so that the "toast" pop-up moves from being transient to permanent (i.e. will stay visible until the agent closes it). If that is true, how is that configured because I don't see an obvious property on the Provider Notification record that toggles that.
Regards,
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Steve — good catch, and thanks for checking rather than assuming. To correct my earlier wording: you are right, there is no property/toggle on the Provider Notification record that turns the toast itself from transient to permanent (stays until the agent closes it).
What persists is not the toast, but the notification entry itself: once raised, it stays in the agent's notification center (bell list) until it is dismissed or marked read, so the agent can come back to it even if the toast has already disappeared or the tab was unfocused. The toast is transient by design; I should not have described it as if the record could pin it on screen.
So in practice: use the Provider Notification for the in-platform record of the change (the bell entry the agent can act on later), and if you need something that actively interrupts/waits for acknowledgement, pair it with your other options — your Now Agent push idea is a valid route for agents on mobile, and Teams is the stronger choice for your staff since everyone already uses it. There is no out-of-the-box way to make the workspace toast itself stay until dismissed; that would need a custom notification component, which is rarely worth it when the bell entry plus Teams/push already cover the need.
Thanks again for the helpful mark and for the follow-up — happy to look at the Teams/Flow side if you go that route.