Messenger Notifications Not Arriving: Checking Windows, macOS, Linux and Centrio

1. Work out what's actually missing

A notification isn't a single event. The message itself, the unread counter, the sound, and the system banner can all behave independently. A red badge next to a service confirms an unread message exists, but it doesn't prove Windows was ever asked to show a pop-up. The reverse is also possible: the banner has already disappeared while the message is still unread.

Pick one problem service and ask a colleague to send a short test message with recognizable text. Use an ordinary personal chat where notifications definitely aren't muted. Leave the app open first, then switch to another window. Don't test ten chats at once — different rules for groups and channels will make the results impossible to interpret.

What you're seeing	Where to start
No message even inside the chat	Network, account sign-in, the service itself
Message is there, no banner	Chat rules, app permissions, and OS permissions
Banner appears, no sound	App sound, system volume, output device
Notifications repeat	A second client, browser tab, or duplicate service instance

2. Separate a delivery problem from an alerting problem

Open the problem chat and confirm you're signed into the right account. When a work and a personal profile sit side by side, it's easy to be waiting on a message that's actually in the other session. Compare the avatar, name, and phone number or email address. If a fresh sign-in is required, notification permissions won't restore your authorization — finish signing in the normal way first.

If new messages only show up after a manual refresh, check that service's connection status directly. Open its official web client in a browser on the same computer. Working in the browser but not in Centrio is a useful distinction for your next check. Not working anywhere means local banner settings can wait for now. This comparison won't give you a final cause, but it narrows the search.

Don't start by removing services or wiping all app data. That forces you to sign back into every account, and the original symptom may still be there afterward. Write down what you observed before restarting anything — during diagnosis that's more useful than several simultaneous changes.

3. Check the specific chat and web service settings

Inside the messenger, check whether the chat, group or channel itself is muted. A service may have separate rules for direct messages, mentions and calls. A test message with no mention in a group doesn't test a "notify only on mentions" rule. Pick the event that should actually trigger an alert under your current settings first.

Then open the web client's general notification settings. Check desktop alerts and sound separately. If the service prompts you to allow notifications, complete that prompt inside the app you're actually working in. Permission granted to a site in Chrome doesn't automatically carry over to a separate session in a different app.

Repeat the test with the chat not in focus. Some clients deliberately change alert behavior for an open conversation. So a missing banner over an active chat, on its own, doesn't confirm anything is broken. Compare identical conditions and note where your focus actually was at that moment.

4. In Centrio, tell apart quiet mode, sound and unread counts

In Centrio, check the overall quiet mode and the notification settings for the specific service. Per-service controls are in its context menu; general alert settings are in the notifications panel. Turning off sound and turning off notifications entirely solve different problems — for calm work, the first is often enough.

Badges tell you where new messages showed up: check both the individual service tab and the overall indicator. With notifications turned off, a service can drop out of the overall count even though its messages are still there on its own page. Don't rely on the overall number as the only way to check one specific conversation.

Custom sounds are handy when you need to recognize a work channel by ear. That said, custom sounds are currently a Pro feature; basic notifications and quiet mode are in Free. Don't buy a subscription to fix a system-level ban on banners — check OS permissions first. Free allows up to three connected services.

5. Windows: app permissions and Do Not Disturb

On Windows 11, open Settings → System → Notifications. Check the general toggle, then the entry for the specific app. For a browser-based service that might be the browser itself; for Centrio, look for Centrio. Inside a sender's own settings, banners, notification center entries and sound are turned on separately.

Check Do Not Disturb and its automatic triggers. It can turn on by schedule, during a game, while mirroring a display, or during full-screen work. If an entry shows up in the notification center but never popped up on screen, that's an especially useful thing to check. For a regular working setup, it's easier to allow specific apps through than to keep toggling quiet mode off entirely.

After adjusting permissions, resend one test message. If the banner shows up but there's still no sound, check volume and the current audio output — a headset may still be selected after a call. Don't change notification settings, the audio device and the account all at once — you won't be able to tell which change actually helped.

6. macOS: app notifications and Focus

On a Mac, open System Settings → Notifications and select the app that should show a banner. Allow notifications and check its display style. Separately review whether it shows on the lock screen and whether text previews are shown — a hidden message preview is not the same as a missing notification.

Then check the "Focus" section. An active Focus profile can restrict which apps notify you, and a schedule can turn one on without any manual action. If Focus settings are shared across your Apple devices, factor that link in too. To test briefly, turn off the current Focus profile, send a test message, and restore your usual rules afterward.

It's worth checking normal work and screen sharing separately. No pop-up text during a presentation may well be the behavior you want. If you need urgent alerts during meetings, decide ahead of time which apps are allowed to notify you, and whether message content should be visible to an audience.

7. Linux: it depends on your desktop environment

On Linux there's no single universal notification settings screen — behavior depends on your desktop environment. In GNOME, open Settings → Notifications, check Do Not Disturb mode and the permissions for the app in question. The notification list opens by clicking the clock or with Super+V. With quiet mode on, entries can stay in that list without ever popping up as a banner.

If you're on KDE Plasma or another environment, look for the equivalent section in its own system settings. Don't apply GNOME-specific commands just because a distro is called Ubuntu — the installed shell can be something else entirely. When reaching out to support, state the distro and the desktop environment separately.

A useful control check is a notification from a different installed app. If nothing shows up at all, investigate desktop settings first. If other programs notify fine and only one messenger stays silent, go back to chat rules, session state and that specific client. That's faster than changing system services without a confirmed cause.

8. In the browser, check the permission for that exact site

In Chrome, open site settings via the icon to the left of the address bar, or go to Privacy and security → Site settings → Notifications. Check whether the problem service's address is in the allowed or blocked list. Permission for one domain doesn't automatically extend to every other one.

Google also warns that notifications don't arrive in Incognito mode. That makes a private window an awkward control test specifically for desktop alerts. A separate regular profile with permission explicitly granted works better for comparison. After changing a permission, reload the page and repeat the test.

If banners are duplicating, check whether the same account is signed in at once in the browser, a separate client, and Centrio. Pick one primary place for alerts and turn them off in the rest. You can keep the sign-in in a backup client active — you don't need to sign out of the account to stop duplicate alerts.

9. Finish the check and note down what helped

Test in two states: the app open on a different service, and the app minimized. A fully closed program, a minimized window, and a sleeping computer are all different conditions. Don't treat a successful test with the chat open as proof that background alerts work. Likewise, a test that works while the computer was asleep doesn't explain behavior during active use.

If the problem is still there, prepare a short description: service name, app version, OS, Linux desktop environment if relevant, the exact symptom, and how it compared to the browser. Add the time of the test and whether an unread counter appeared. You typically don't need to include the content of personal messages in that report.

Once things are fixed, settle on a stable scheme: urgent work messages with sound, less important ones visual-only, informational channels checked on your own schedule. The goal is predictability — an important event should produce the alert you expect, and a constant stream of background notifications shouldn't be allowed to bury it.

Frequently asked questions

Why is the message there but there's no notification?

Delivery and alerting go through separate checks. If the message is visible, work through chat rules, client settings, site permissions and your OS's quiet mode, in that order.

Why does the sound play but no banner shows up?

A web service can play sound independently of the system banner. Check the banner permission for your browser or for Centrio, and check whether Do Not Disturb is active.

Do I need to clear the cache to fix notifications?

That's usually not the first step. Start with one test message and permission checks. Clearing data can end your session and force a fresh sign-in without actually fixing a notification block.

Are notifications free in Centrio?

Basic notifications and quiet mode are included in Free. Custom sounds are a Pro feature. Check the pricing page for the current feature breakdown.