You do not have to keep an eye on the Yaplet tab all day. Your browser can show you a desktop notification — the small popup your computer displays outside the browser — the moment a customer writes. It is off until you turn it on, and it takes two clicks. In the same place you can also check the sound and stop your browser from putting the Yaplet tab to sleep.
1. Turn them on
Notifications are switched on in Settings. If your browser has not been checked yet, a reminder in the Inbox takes you there.
In Settings
Open the account menu at the bottom of the left-hand menu and choose Settings. Find the check titled Chat alerts in this browser. It has four rows: Sound, Browser notifications, Phone app and Keep this tab awake. Switch on Browser notifications — your browser asks whether Yaplet may show notifications. Choose Allow, and you are done.
From the Inbox reminder
While you are Online, the first time you open Yaplet in a browser, a card appears above your conversation list: Can this browser alert you?
- Check now — opens Settings right at Chat alerts in this browser, where you switch on Browser notifications and look at the other three rows.
- Got it — closes the card without opening anything.
Either button hides the card in this browser. It comes back only after the browser has put Yaplet to sleep (see "Keep Yaplet awake" below), and it is never shown while you are Offline.
2. Check that they really arrive
Once the Browser notifications switch is on, a Send test button appears next to it. Click it and a real notification should appear within a few seconds, outside the browser, in the corner of your screen where your computer normally puts them.
If nothing shows up, your computer itself may be holding notifications back — check its own notification settings for your browser, and make sure you are not in a focus or do-not-disturb mode.
The sound you hear inside the Yaplet tab has its own test: click Play test sound in the Sound row. If the row warns Blocked, click anywhere in Yaplet — your browser plays no sound until you do, and one click fixes it. If it warns Muted, your notification volume is 0; raise it in your profile at the top of Settings.
Keep Yaplet awake
To save memory, browsers put tabs you are not looking at to sleep, and a sleeping Yaplet tab cannot play the sound or show new chats. With Browser notifications on, the popup still reaches you — but the sound and the new chats in your list do not. The Keep this tab awake row in Chat alerts in this browser shows what to do for your browser:
- Easiest, in any browser: keep Yaplet in its own browser window.
- Chrome: Settings → Performance → "Always keep these sites active" → Add → the Yaplet address.
- Edge: Settings → System and performance → "Never put these sites to sleep" → Add → the Yaplet address.
- Brave, Opera and other Chromium browsers: add the Yaplet address to the sites that the browser's sleep or memory-saver option never touches.
- Firefox: only puts tabs to sleep when your computer is low on memory — close the tabs you do not need.
- Safari: has no setting for this — keep Yaplet in its own window and do not minimize it.
Do not let your computer go to sleep during your shift either. In Chrome and Edge, a button in that row copies the browser's settings address, so you can paste it into the address bar. If the browser put Yaplet to sleep during your shift in the last week, the row tells you for how many minutes.
Yaplet also tells you when it happens. If the browser kept Yaplet asleep for 3 minutes or more while you were Online, the card above your conversation list says Yaplet was asleep for N min (N is the number of minutes), with Show me how and Got it. Show me how opens Settings at Chat alerts in this browser, and either button hides the card in this browser until the next sleep. Only Chrome, Edge, Opera and Brave let Yaplet notice a sleep; Firefox and Safari do not, and a computer going to sleep is never noticed.
What a notification looks like
The title is the customer's name and the text is their message. Click it and the Yaplet window you already have open comes to the front with that conversation open — you do not end up with a second dashboard window.
You get one notification per conversation, not one per message. If the customer keeps writing, that popup quietly updates to their latest line — new text, no sound — until someone from your team opens or answers the conversation; after that, their next message alerts you again. A new request for a person always alerts you, and lines written by the AI bot, workflows or the system never notify anyone.
Workspace owners also hear about conversations nobody else can take. When a customer writes or asks for a person while nobody on the team is on duty (Online and with access to that brand), the owners get a notification whose text starts with Nobody on duty. When nobody from the team answered a request for a person within 5 minutes, it starts with No answer in 5 min. The owners get both by email too, with the conversation.
Why you sometimes get nothing
Most "my notifications are broken" reports turn out to be one of these, in this order:
- You had Yaplet on screen. No popup is shown while a Yaplet window is visible — the dashboard already announces the message with its own alert and sound. This is deliberate.
- Your status is Offline. Offline means you receive nothing at all, on any device, whatever the browser allows — unless you are a workspace owner and nobody is on duty (see above). See availability and business hours.
- The conversation is assigned to someone else. An assigned conversation only notifies the person it is assigned to, as long as they are on duty. If they are not, a live chat notifies everybody on duty for that brand, just like an unassigned one; an email conversation stays with its person and notifies nobody else. Unassigned ones notify everybody who is online and has access to them.
- You do not have access to that brand. You are only notified about conversations you could open anyway — see who sees which conversations.
- The browser put the Yaplet tab to sleep. A sleeping tab cannot play the sound or show new chats, although the popup from Browser notifications still comes. See "Keep Yaplet awake" above.
- Chat sounds are blocked until you click. After you reload the page, or when your browser reopened the tab by itself, browsers play no sound until you click on the page. If a chat sound is refused while you are Online, a notice says Chat sounds are blocked. One click or key press anywhere in Yaplet fixes it and closes the notice.
- The live connection dropped. New chats, messages and sounds reach the dashboard over a live connection. Yaplet reconnects it by itself, also in a background tab, and at once when you come back to the tab. If it stays down for a while, a notice says Live updates paused: new chats, messages and sounds cannot reach this tab right now. Yaplet keeps trying, and the notice closes by itself once the connection is back, followed by Live updates are back. The notice also has a Reload page button if you would rather not wait. If a new chat started waiting in the meantime, the new-chat sound plays once when the connection returns.
One more thing that is easy to expect and does not happen: only customer messages become desktop notifications. The bell in the sidebar — billing notices, announcements, messages from your admins — stays inside the dashboard.
If your browser is blocking them
If the line under the switch reads Blocked by your browser, notifications were refused for Yaplet at some point, and we cannot ask you again — browsers only allow one ask per site.
- Click the icon at the left end of the address bar — a lock, a slider, or an "i", depending on your browser.
- Find Notifications and set it to Allow.
- Reload the page and switch Browser notifications back on in Chat alerts in this browser (account menu → Settings).
If it reads Not available in this browser, that browser cannot show desktop notifications at all. The usual case is Safari on an iPhone or iPad — use the Yaplet mobile app there instead.
Each browser is its own switch
Notifications belong to the browser in front of you, not to your account. Turning them on at the office does nothing for your laptop at home, and your colleague signing in on their own machine starts from off. If you use more than one computer, switch them on at each one.
The same applies to the web address you sign in at: if you sometimes open Yaplet on a different address, turn notifications on there too.
On a shared computer
Sign out from the account menu at the end of your shift. Signing out also disconnects that browser, so the next person to use it does not get popups about your conversations. Closing the browser window is not the same thing — the connection stays until you sign out or switch the setting off.
For team leads: who has notifications on
If you are allowed to manage the team, open the account menu and choose Manage team. On wider screens, each member shows Notifications on or No notifications; hover over it to see in how many browsers. Only browsers where notifications really work are counted — the phone app is not.
A member who shows No notifications only hears about new chats while a Yaplet tab is open and awake. Ask them to switch on Browser notifications in Settings → Chat alerts in this browser.
Away from your desk
Desktop notifications only reach the computer you are sitting at. For alerts on the move, install the phone app and allow notifications there — see use the mobile app for agents.