Notifications — channels, and why push is per-device
In-app, email, push and Telegram are independent channels. Push is the one that surprises people: it's granted per device, so signing in on a new phone means enabling it again there.
Who this is for
Everyone. Admins should mention push during onboarding — it's the channel people assume is broken.
The channels are independent
Turning something on in one place doesn't turn it on everywhere. That's a feature — you probably want a new-lead alert on your phone but not an email for every one — but it does mean 'I'm not getting notified' needs the follow-up question 'where were you expecting it?'
Push is per device
Push alerts appear on your phone's lock screen and open straight to the record they're about. But permission is granted by the device, not the account: each phone or tablet you sign in on has to be enabled separately, and if you declined the OS prompt you have to re-enable it in your phone's own Settings before the app can ask again.
Same shape as the browser microphone permission for calling — device-level, and nobody else can fix it for you.
Tune it down rather than off
The failure mode with notifications isn't too few, it's so many that people stop reading them. If you're ignoring a category, switch that category off rather than muting everything — otherwise the one alert that mattered arrives in a stream you've already learned to swipe away.
How to check it worked
- Trigger the event you care about and confirm it arrives on the channel you expect.
- For push, test on each device you actually use.
Related
Where this lives in the app
This is documentation for Virtual Closer. Book a walkthrough or sign in.