Google Chat notifications not working on a Mac: how to see them

There are two versions of this problem and they need different fixes. In the first, no Chat notification has ever appeared on the Mac, which means a permission somewhere in the chain is off. In the second, notifications appear on some days and not others, which is almost never a permission. It is Google's routing rule deciding that the phone is the better place to send them.

Most troubleshooting lists cover the first case and stop. The routing rule is the one that wastes a week, because every setting looks correct while the messages quietly arrive somewhere else.

Chat picks one device, and the rule is published

Google states the basic behaviour plainly: notifications appear on the devices used most recently, and if there is no recent activity in Chat, they appear on all devices signed in to the account. So the default is not "everywhere at once". It is "wherever the person appears to be".

The mechanism behind that is a browser permission called idle detection, and it has a number attached. Google documents that idle detection delivers notifications to the active device and pauses mobile alerts while there is activity on the desktop, and that a person counts as idle after being inactive for more than 30 seconds, even with the browser still open. Thirty seconds is short enough that reading a document in another window, or answering a question across a desk, is enough to hand the next notification to the phone.

There is a second routing rule on top of that. Google's troubleshooting page says that when the Chat or Gmail mobile app is open, notifications show up there and do not show up in the browser, in the Chat desktop app, or in Chat inside Gmail. A phone left with Chat on screen on a desk is therefore not a passive bystander. It is the device that has been chosen.

The permission itself is granted in the same prompt as notifications, and the dialog is recognisable because it asks about pausing mobile notifications when active on this device. If the prompt never appeared, it can be set by hand at chrome://settings/content/idleDetection, where the option that sites can ask to know when the device is in use is turned on and chat.google.com or mail.google.com is added to the allowed list.

Find out where notifications are currently going

Before changing anything, it is worth learning which place is receiving them, because Chat can be open in three places on one Mac and only one of them is the delivery target.

Google documents a test for exactly this. In Chat, open Settings and then Notifications, and look under Desktop notifications for Show an example. If that option is there, web notifications are being delivered in that place. If it is missing, they are going to another browser tab or to the Chat app itself. The same test exists in Gmail, under Settings, then See all settings, then the Chat and Meet tab, then Manage chat settings.

That single check separates two situations that look identical from the outside. A Mac with chat.google.com open in a tab, Gmail open in another tab, and the Chat app installed has three candidates, and the answer is not always the one in front of you. If the example notification does not appear at all, Google names two causes to check first: availability status muting notifications, and notifications not being turned on for that device and browser.

The three gates a notification has to pass

Each gate is a separate switch, and all three have to be open. Checking them out of order is what makes this take an afternoon.

The Chat setting comes first. In Chat, under Settings and then Notifications, the box is called Allow chat notifications. Google documents a detail that explains a lot of confusion here: if that box is already ticked but the browser is blocking notifications, a Turn on button appears next to it, and clicking it triggers the permission dialogs. A ticked box is therefore not proof that anything is permitted.

The browser permission comes second, and it needs two entries rather than one. Google's instructions name both https://chat.google.com:443 and https://mail.google.com:443, and both should sit under the list allowed to send notifications in Chrome's site settings under Privacy and security. Adding only the first is a common outcome, and it leaves Chat inside Gmail silent while Chat in its own tab works.

The operating system comes third. On a Mac, notifications are in System Settings under Notifications, where each app and website has its own entry with Allow notifications, an alert style, a badge option and a sound option. Google's page says only that each operating system differs and to check its help, which is accurate and not much use, so the specific thing to look at is whether the entry for the browser that runs Chat has notifications allowed at all.

When notifications appear but stay silent

A visible banner with no sound is a different fault, and it has three possible causes that live in three places.

Chat has its own sound setting, under Settings and then Notifications, where a notification sound is chosen from a list. In Gmail the same control sits under Manage chat settings.

Chrome blocks auto playing audio by default, which is the cause most people never find. Google's fix is specific: in site settings under Customized behaviors, open https://chat.google.com:443, find Sound under Permissions, and set it to Allow, then repeat for https://mail.google.com:443.

macOS has the third switch. In System Settings under Notifications, the entry for the app that delivers Chat has an option called Play sound for notification, and it is independent of everything above. The same panel holds Badge application icon, which is what puts a count on a Dock icon, and an Alert Style choice between Temporary, where banners disappear on their own, and Persistent, where they stay until dismissed. For a chat tool, Persistent is usually the right answer and it is not the default.

The Mac settings that silence Chat without saying so

Four settings on a Mac stop notifications for reasons that have nothing to do with Chat, and Apple documents all of them in the same place.

Notifications can be paused when the display is sleeping, when the screen is locked, and when mirroring or sharing the display. The third one matters more than it sounds, because screen sharing is exactly what happens during a meeting, which is exactly when a missed message is most noticeable. Anyone who reports that Chat notifications fail during calls and work fine afterwards should check that switch before anything else.

A Focus is the fourth. Apple documents that time sensitive alerts need to be allowed both for the app and for the Focus itself before they appear while a Focus is on, so allowing them in one place and not the other produces a setting that looks correct and does nothing.

Chat has its own equivalent, which is availability status. Google states that setting status to Do not disturb, or muting a conversation, stops notifications. Two exceptions are documented, and both come from Chat apps rather than people: an @notify message is designed for critical or time sensitive information and ignores Do not disturb, muted conversations and notification settings, while an @silent message is designed for low priority updates and behaves like a system message.

Check what Chat is set to notify about at all

Some of these reports are not failures. They are the default settings working as documented, on a busy space where a person expected every message to arrive.

By default, Google sends a notification when someone mentions you and when someone reacts or responds to your message. Not for every message in every space. Per space, the choices are All for every new message and reply, Main conversations for new main conversations along with mentions and replies to followed threads, For you for mentions and replies to followed threads, and None, which leaves only an indicator for mentions. Direct messages carry a shorter version of the same list.

Two more behaviours are worth knowing. Notification settings for a space or a direct message are shared between the web and the mobile app, so changing one changes both. And if email notifications are on, Google sends an email reminder for Chat messages that have gone unread for more than 12 hours, which is a useful safety net and a poor substitute for a working notification.

Why a tab is the weakest place to keep Chat

Every fix above assumes Chat lives somewhere. If that somewhere is a browser tab, three of the problems in this article are structural rather than accidental.

A tab has no entry of its own in the Dock, so the Badge application icon setting that would show a count belongs to the browser rather than to Chat. A tab reports unread state in its page title, and page titles truncate as the strip fills. And a tab is subject to the 30 second idle rule while sitting inside a window that is being used for something else, which is the most reliable way to send a message to a phone that is face down in a bag.

Google's own answer is the standalone app, and it is documented rather than a workaround. Signing in at chat.google.com in Chrome and choosing Install Google Chat from the More menu, or the Install button in the address bar, produces a progressive web app that opens from the Applications folder on macOS. It needs Chrome 73 or later, it can be set to open at startup from chrome://apps, and Google notes there is no Chat extension for Chrome, so this is the route. One documented condition comes with it: Chrome does not have to be the default browser, but it does have to be open for the Chat app to work.

Route	What it needs running	Own Dock icon and badge	Separate sign in per app
A browser tab	The browser window	No	No
Chrome, Install Google Chat	Chrome open in the background	Yes	No
Safari, Add to Dock	Safari's web app support	Yes	Yes
A dedicated site to app tool	The app itself, with a Chromium browser installed	Yes	Yes

Safari's route is the Share button in the toolbar, then Add to Dock, and Apple states that notifications arrive from a web app just as they would from any app. The fourth route builds the app on top of a Chromium browser that is already installed, with each app running as its own browser instance rather than as a window of a running one, which is also what gives each app its own cookie store when a second work account is involved. The differences between these routes are set out on Features, and the step by step version is in the Guide.

What to change first

Open Chat, go to Settings and then Notifications, and click Show an example. If nothing appears, work through the three gates in order: the Allow chat notifications box, both chat.google.com and mail.google.com in the browser's notification permissions, and the operating system entry. If the example works but real messages still land on the phone, the cause is the 30 second idle rule, and the fix is to give Chat a window of its own with the route built into Chrome or with Kagemusha.