Overview
Notifications arrive through more than one channel, and each one is controlled independently:
- Browser push: an operating-system alert when the tab is open or in the background. It depends on an active push subscription.
- Email: a digest/alert sent to your account email.
- In-app: the notifications bell inside the platform (a list with read/unread, mark as read, snooze and delete).
- Sound/audio: an audible cue in the dashboard when something new happens.
What triggers each notification depends on the event type (conversation assignment, mention, new conversation, new message in an assigned/participating conversation, SLA, and events from other modules such as tasks, CRM, payments and calendar). For each type, you choose separately whether to receive it by email and/or push. If a channel is unchecked for a given type, the notification will not arrive there — and that is usually the reason behind "I'm not receiving notifications".
Prerequisites
- Being logged in to your account.
- A browser with notification permission granted for the platform's address.
- The correct, reachable account email (check the spam/junk folder).
Step by step
- Review your per-event-type preferences. In your profile/account, open Notification settings and check, for each event type, whether Email and/or Push are enabled. Save your changes.
- Allow browser notifications. Grant notification permission to the site and enable push — this registers a push subscription tied to your user. Without an active subscription, push is not delivered.
- Check email. Confirm the account address and look for recent messages; check the spam folder and add the sender to your trusted contacts.
- Check volume and sound. Make sure the system/browser sound is not muted and the dashboard's audible cue is enabled.
Settings & options
- Per-channel, per-type preferences: the email and push selections are stored as separate lists (one for email, one for push). Checking one does not check the other.
- Push subscription: each browser/device creates its own subscription. Switching browser, profile or device requires allowing and registering again.
- In-app (bell): notifications also appear in the internal list even when push or email are off; there you can mark as read, snooze, or delete.
Use cases
- Get push for mentions and new messages, but only email for missed SLA.
- Keep a tab open to ensure push while you work.
- Track everything through the in-app bell and use email only as a backup.
Tips, limits & best practices
- Browser push is most reliable with one platform tab open.
- After switching device or browser, review your preferences and register push again.
- Emails can land in spam: marking them "not spam" improves future delivery.
Troubleshooting
- Permission denied in the browser: the browser is blocking notifications for the site. Open the site settings, switch to Allow and reload the page.
- Expired push subscription: push stops arriving even with permission granted. Re-enable it by turning browser notifications off and on to register a fresh subscription.
- Email not arriving: confirm the correct account address and check spam/junk; allow the sender.
- No sound: check the system/browser mute and whether the dashboard's audible cue is enabled.
- Only one event is missing: the channel (email or push) is likely unchecked for that type in your preferences.