Mobile and web push notifications

What it is

This area is about getting an Omniscio alert to reach you when you are not sitting at the computer running it. There are two delivery paths, and they behave differently.

Phone push goes through a hosted push provider that delivers to an app installed on your phone, so a notification can arrive on a locked screen with the app closed. Web push delivers to a browser instead — an open tab, or a phone browser with the web app installed to the home screen — and it is switched on per device, because whether a particular browser has agreed to receive push is a fact about that device, not a setting that can be shared across all of them.

Layered over both is a privacy mode. In its default state, the notification the push provider sees and stores carries no message content: no sender, no subject, no message body, no session name. The notification still opens the right conversation when you tap it, because the routing information is kept — but your actual words never leave the device in the payload the provider retains.

Where to find it

• The push controls live in Settings, under Notifications, alongside the ordinary chimes and OS toasts. There you will find the privacy switch, a phone-sound switch, and the web-push control for the device you are on.
• A phone or home-screen web app asks for push permission the first time, in the browser's own prompt.
• The mobile pages (reached from the sidebar or a phone) are where you actually read and act on what the push was about.

How it behaves

• Notifications & silence — the parent page for everything that decides when Omniscio is allowed to interrupt you, including mobile push, the content-free privacy default, and the phone sound switch.
• Mobile Access — the phone experience the push points into: what you see when you open Omniscio from a phone, and how you get in.
• Mobile Access — internals — how the push stream to a phone is filtered down to what the mobile view can actually render, and where the push subscription lives.
• Mobile device tracking — which phone is connecting with your pairing token, and how to approve or block one.
• Notification history — the look-back list of toasts and dismissed alerts, so a notification you missed is never lost.
• Inbox alerts — what a push is ultimately telling you about: the cards an agent or a scheduled job raises into your inbox.

A push is only sent for the kinds of events you would want to hear about — a session that needs you, an error, or a session that ended. It is delivered once, deduplicated against repeats, and rate-limited so a burst of activity does not flood your phone.

Two health checks keep push from failing quietly. When a delivery reports that a registered device token is no longer valid, that token is pruned so future sends stop trying it. And a watchdog raises an inbox card if a paired phone stops working reliably, so you find out from Omniscio rather than by noticing you stopped being notified.

Related

• Notifications & silence — when Omniscio may interrupt you, and every rule that quiets it.
• Mobile Access — running and triaging your sessions from a phone.
• Mobile device tracking — which phone is connecting, and whether it should.
• Notification history — past toasts and dismissed alerts.
• Inbox alerts — the cards an agent raises to ask for your attention.
• Mobile Access — internals — the push filter and subscription behind the phone view.