Notifications

Ce contenu n’est pas encore disponible dans votre langue.

Settings → Notifications — turn message notifications on or off for this device.

Notification preferences are per device. Enabling them on your laptop doesn’t enable them on your phone.

In-app notifications

Setting	What it does
New Message Notifications	Browser or PWA push notifications for new messages on this device
Notification Sound	Plays a sound when new messages arrive — works independently of toasts

The panel states your current combination plainly, e.g. “Toast notifications are enabled, but sound is muted” or “All notifications are currently disabled.”

Push notifications

Enable push notifications for your connected accounts. Push works even when the app is closed.

Status per device: Enabled, {registered} of {total} enabled, or Disabled.
Enable all turns push on for every connected account.
Accounts lists each connected Telegram account with its own Enabled / Disabled state, so you can be notified about the support account but not your personal one.
Send test delivers a test notification so you can verify end to end.

If push isn’t available

Message	Meaning
Push notifications not supported	Your browser doesn’t support them
Notifications blocked	You (or your OS) denied permission — enable it in browser settings
No accounts connected	Connect a Telegram account first

Troubleshooting push

The Troubleshooting section shows live diagnostics:

Field	What it tells you
GCM Sender ID	Present in the manifest, or missing
FCM reachable	Whether Firebase Cloud Messaging can be reached
Permission	Granted / denied / default
Service worker	Registered or not
Subscription	Active, None, or Failed (timeout)
Endpoint	The push endpoint in use

When it detects a specific problem it names it and suggests a fix — for example a missing GCM sender ID, or a subscription that timed out because FCM is blocked.

Force reset

Force reset clears the local push registration and starts again. “Use this if notifications are stuck or missing.”

Manual steps

If a reset doesn’t help:

Open chrome://gcm-internals and check whether your browser has a registration.
Try signing in again in an incognito window.
Clear site data for Entergram and reload.
Try Firefox to rule out a Chrome-specific issue.
Open chrome://settings/content/notifications to reset notification permissions.

Corporate networks and VPNs frequently block FCM — that’s the single most common cause of a subscription timeout.

Notifications troubleshooting
Reminders — reminder notifications come from the Telegram bot, not from browser push