Desktop Notifications

Make sure a new visitor message reaches you even when the dashboard is behind another window — how to switch on browser notifications, check the chat sound, keep your tab from falling asleep, and when nothing appears on purpose.

What they are

A desktop notification is the small popup your operating system shows outside the browser — the same kind of alert you get from a mail or chat app. Yaplet can send you one when a visitor writes and you are working in another window, so you don't have to keep a dashboard tab in view all day.

They are switched off until you turn them on, and they are set per browser: turning them on in Chrome on your office computer does nothing for the browser on your laptop at home.

Hearing about a new chat takes three things in the browser you work in: the chat sound, the browser notification, and a Yaplet tab that the browser has not put to sleep. The Chat alerts in this browser check in Settings looks at all three, and this page explains each one.

Desktop notifications only cover visitor messages waiting for a reply. The bell in the sidebar — subscription updates, platform announcements, messages from your admins — stays inside the dashboard and never becomes a desktop popup.

Turning them on

Browser notifications are switched on in one place: the Chat alerts in this browser check in Settings. The reminder card in the Inbox (described below) and the Turn on chat alerts step of the Getting started card only lead you there.

Open the check

Open the account menu at the bottom of the left-hand menu and choose Settings; the Your account window opens. The check is the card labeled Notifications and titled Chat alerts in this browser. It has four rows: Sound, Browser notifications, Phone app and Keep this tab awake.

Switch on Browser notifications

In the Browser notifications row, turn the switch on. Your browser asks for permission; allow it and you're done. The hint under the switch tells you where you stand. Once it is on, it reads On. A pop-up shows for new chats even when this tab is asleep or closed. You get them only while you're Online; owners also when nobody on the team is. While it is off, it reads Off in this browser. Turn on to get a pop-up for new chats even when this tab is asleep or closed, only while you're Online.

Send a test

Once the switch is on, a Send test button appears next to it. It sends a real notification to this browser so you can confirm it arrives before you rely on it. A message says Test notification sent and adds "It appears outside the browser. Nothing there? Check your system notification settings." If the test cannot be sent, a message says Could not send the test notification. Try again.

Turn it on from the switch, not from your browser's own settings screen. Browsers treat a request that follows a deliberate click far more kindly, and some refuse one that doesn't.

Everything in the check except the Phone app row is per browser: another browser, or another computer, starts fresh and needs its own check. The Phone app row belongs to your account, so it shows the same in every browser.

The reminder in the Inbox

While your status is Online, a card can appear above the conversation list in the Inbox. It switches nothing on by itself — it opens the check in Settings. There are two versions:

  • Can this browser alert you? — shown once in every browser. It says: "Check the sound, notifications and keeping this tab awake, so you never miss a new chat. It takes a minute." Its buttons are Check now and Got it.
  • Yaplet was asleep for N min — shown again after your browser put Yaplet to sleep for 3 minutes or more while you were Online. It says: "Your browser put this tab to sleep while you were Online, so nothing could ring. You can stop it from doing that." Its buttons are Show me how and Got it.

Check now and Show me how open Settings scrolled straight to the Chat alerts check. Whichever button you press, the card disappears in this browser until the next time the browser puts the tab to sleep. While you are Offline the card does not show at all.

Yaplet can only notice a sleeping tab in Chrome, Edge, Opera and Brave, which tell the page about it afterwards. Firefox and Safari don't say so, and a computer going to sleep is never reported — so the second version of the card never appears in those cases.

What arrives

A notification carries the visitor's name as its title and the message itself as the text, shortened if it is very long. Clicking it brings the dashboard window you already have to the front and opens that conversation — or opens a new one if the dashboard isn't running.

You get one alert per conversation, not one per message. The visitor's first message in a conversation waiting for a reply pops up with a sound. If they keep writing before anyone from your team has opened or answered the conversation, that same popup quietly updates to the newest line — no new sound, and no stack of popups. Once someone from the team opens or answers the conversation, the visitor's next message alerts with a sound again. A new request for a person always alerts with a sound.

Only what the visitor writes, and a new request for a person, alert anyone. Lines written by the bot, a workflow or the system never do.

Who gets a notification for a given conversation follows exactly the same rules as the phone app — your Online/Offline status, who the conversation is assigned to, whether anyone is on duty, and which brands you have access to. Those rules are written out in full on the mobile Notifications page, and brand access itself is set on the Organizations page.

Offline means silence. If your status is Offline you receive no notifications at all, on any device, no matter what you allowed in the browser. This is the first thing to check when someone says notifications stopped. The one exception is the organization's owners: when nobody is on duty, they are notified even while Offline.

When nothing appears — on purpose

No popup is shown while any Yaplet window is visible on your screen. You are already looking at the dashboard; it announces the message there with its own sound instead. So "I had the tab open and got no popup" is the system working, not a fault.

The dashboard's own sounds work like this. In a conversation assigned to you, each message the visitor writes plays the message sound. In an unassigned conversation, the new-chat sound plays for the visitor's first message (until someone from the team opens or answers it) and for every new request for a person — the Agent requested line. Lines written by the bot, a workflow or the system make no sound.

The Send test button is the one exception — it always shows, because otherwise the button could never prove anything.

The notification volume slider in Settings controls the in-app sound the dashboard plays, not the desktop popup. The popup uses whatever sound your operating system assigns to notifications.

Keeping the dashboard tab awake

To save memory, browsers put background tabs to sleep, and a sleeping tab can't ring or show new chats. The browser notification is your safety net — its pop-up still shows when the tab is asleep or closed — but the chat sound and new chats appearing in the dashboard need a tab that is awake.

The Keep this tab awake row in the check shows how to stop your browser doing that to Yaplet. The easiest way is to keep Yaplet in its own browser window. If you prefer to keep it in a tab, the row shows the step for the browser you are using:

BrowserWhat to do
ChromeSettings → Performance → "Always keep these sites active" → Add → the Yaplet address.
EdgeSettings → System and performance → "Never put these sites to sleep" → Add → the Yaplet address.
Brave, Opera and other Chromium browsersFind the option that puts tabs to sleep or saves memory, and add the Yaplet address to the sites it never touches.
FirefoxIt only puts tabs to sleep when your computer runs low on memory — close the tabs you don't need.
SafariIt has no setting for this — keep Yaplet in its own window and don't minimize it.

The row also reminds you not to let your computer go to sleep during your shift.

In Chrome and Edge, a button in the row copies the address of the browser's own settings page (chrome://settings/performance or edge://settings/system). Paste it into the address bar to get there — a web page is not allowed to open that page for you.

If your browser put Yaplet to sleep during one of your shifts in the last 7 days, a line at the top of the row says Your browser put Yaplet to sleep for N min during your shift. A sleeping tab can't ring. (N is the number of minutes.) It is the same thing the Inbox reminder tells you about.

When chat sounds are blocked

Browsers play no sound on a page nobody has clicked yet — for example after a reload, or in a tab the browser reopened by itself. When a chat sound is refused while you are Online, a notice appears: Chat sounds are blocked — "Your browser plays no sound until you click somewhere in Yaplet. One click anywhere on this page fixes it."

The first click or key press anywhere in Yaplet unlocks the sound and closes the notice. The Sound row in the check shows the same state as Blocked, and its Play test sound button (which reads Play again after a play) fixes it too. If the row says Muted instead, the notification volume on your Profile card is set to 0.

When live updates pause

New chats, messages, sounds and the waiting-chats counter all reach the dashboard over one live connection. Yaplet reconnects it by itself: also while the tab is in the background (there roughly once a minute at worst, because browsers slow down background tabs), and at once when you come back to the tab or your network comes back.

If the connection stays down for a while, a notice appears: Live updates paused — "New chats, messages and sounds can't reach this tab right now. Yaplet keeps trying by itself, and this closes as soon as the connection is back." It has a Reload page button if you would rather not wait, and no close button. It closes by itself when the connection is back, followed by a short Live updates are back.

If a new chat started waiting while the connection was down, the new-chat sound plays once as soon as it reconnects.

The permission belongs to the browser and the address

Two things decide whether a notification can reach you: the browser you are sitting at, and the web address you signed in on. Yaplet's dashboard runs on more than one address, and each one is treated separately by the browser — so if you sometimes work from a different Yaplet address, switch notifications on there too. Each browser sends you to the address it was switched on at, which is what keeps a click landing in the tab you already have open.

If your browser is blocking them

If the hint under the Browser notifications switch reads Blocked by your browser, the permission was refused at some point and Yaplet cannot ask again — browsers only allow one ask per address.

  1. Click the icon at the left of the address bar (a lock, a slider, or an "i", depending on the browser)
  2. Find Notifications and set it to Allow
  3. Reload the dashboard, open Settings and turn the Browser notifications switch back on

If it reads Not available in this browser, that browser cannot do desktop notifications at all. The usual case is Safari on an iPhone or iPad in a normal tab — use the Yaplet mobile app there instead.

Shared computers

Signing out through the account menu also unlinks that browser, so the next person to sign in on it does not receive your conversations. Turning the switch off does the same thing without signing out.

Closing the browser is not signing out. On a computer several people use, sign out properly at the end of your shift — otherwise the machine keeps receiving notifications for your conversations.

Seeing who on your team has notifications on

On the Organizations page (account menu → Manage team, which needs the Organization permission), each member's card shows a badge on wider screens: Notifications on (a green bell) or No notifications (gray). Hover over it for the explanation: either the member gets a browser notification for new chats in N browser(s), even while the Yaplet tab is closed or asleep (only while Online), or they hear about new chats only while a Yaplet tab is open and awake, and can turn notifications on in Account settings → Chat alerts in this browser (account menu → Settings).

The badge counts only working browsers — a browser whose notifications keep failing is not counted — and it does not count the phone app, only browsers. Use it to see who on the team would miss a chat while their Yaplet tab is closed or asleep.

Limits worth knowing

LimitWhat it means
180 days of inactivityA browser that hasn't opened the dashboard for half a year is dropped from the list. Opening the dashboard there again puts it back with no prompt, because the permission is still in place.

User Settings

The Chat alerts in this browser check — sound, the browser notifications switch with Send test, the phone app row, and keeping the tab awake — lives in the settings modal. The notification volume slider stays on the Profile card.

Mobile Notifications

The same rules on your phone — who gets notified for which conversation, and what to check when notifications stop.

Organizations

Brand access decides which conversations can notify you at all.

© 2026 Yaplet. All rights reserved.