Web Push Notifications
The WebSocket version delivers browser-native push notifications for new messages and incoming calls — reaching users even when they've closed your tab or moved to another website. Push works across Chrome, Firefox, Edge, and other modern browsers that support the Web Push API, on both desktop and mobile.
Web push is a WebSocket-version feature. The free version does not include push delivery — users only receive notifications while they have the site open and the tab is active.
What it adds#
- Native browser push for new messages and incoming calls
- Reaches users while they are on other sites, on other tabs, or have the browser minimized
- One-time opt-in through the browser's permission prompt — no Better Messages account or third-party app required
- Clicking the notification opens the relevant conversation in a new tab
- Works on desktop (Chrome, Firefox, Edge, Brave, Opera) and Android browsers
- Independent from the mobile-app push channel — both can be active at once
How it works#
When a user is signed in and grants browser push permission, the browser registers a push subscription with the device's push service (Apple Push Notification service for Safari/macOS, Firebase Cloud Messaging for Chrome/Android, Mozilla's autopush for Firefox). Better Messages stores the subscription against the user's account.
When a new message or incoming call arrives via the WebSocket relay, the plugin checks whether the recipient is currently active on the site:
| Recipient state | What happens |
|---|---|
| Tab open, page focused | In-app notification + sound only (no push) |
| Tab open, page unfocused | Web push fires |
| Browser closed entirely | Web push fires (delivered when browser opens) |
| Site never opened in this browser | No push subscription, falls back to email notification |
Click handling is built in — tapping the push notification opens the conversation directly. Notifications include the sender's name and a message preview that respects the recipient's privacy settings.
When users benefit most#
| Scenario | Why web push matters |
|---|---|
| Community managers replying to support DMs | Stay reachable without keeping the site tab open all day |
| Marketplace vendors waiting on buyer questions | Pre-purchase questions don't get missed |
| LMS instructor office hours | Students can ping the instructor; instructor is notified immediately |
| Dating / fan communities | Real-time reach to users who only check the site occasionally |
How to enable#
Web push is automatically available with the WebSocket version — there's no admin setting to flip. Users are prompted by their browser to allow notifications the first time they enter a conversation. They can manage the permission anytime through the browser's site settings, or via their account preferences inside Better Messages.
For the cleanest user experience, the plugin only triggers the browser permission prompt at a meaningful moment (when the user has just opened a thread), not on first visit. This dramatically improves opt-in rates compared to prompting on landing.
Frequently asked questions#
Does web push work on iPhone Safari?#
Web push for iOS Safari requires the user to install the site as a Home Screen PWA first (iOS 16.4+). For most iOS users, mobile-app push via OneSignal or the native iOS app is more reliable. Desktop Safari (macOS) supports web push directly.
What happens if a user denies the browser permission prompt?#
They will not receive web push notifications. They still receive in-site notifications (badge, sound) when active, and email notifications when away — both fall back gracefully. They can re-enable push from browser site settings later.
Does web push share data with third parties?#
The push service (Apple, Google, Mozilla) handles the delivery infrastructure but cannot read message content — the payload sent through the push service is encrypted in-transit and Better Messages controls the content. No third-party analytics or tracking is added.
How does web push interact with the mobile app's push?#
Independently. A user with both the mobile app installed AND web push enabled will receive notifications in both channels for the same event. Most users disable one or the other manually in practice. There's no built-in coordination.
Are notification previews configurable?#
Yes — the Privacy Settings under WP Admin → Better Messages → Settings → Notifications let you choose whether the message body appears in the notification or only the sender's name. Sites with sensitive content typically choose "sender only".
See also#
- Mobile app push notifications — native iOS/Android push
- OneSignal integration — multi-channel push provider
- Progressify PWA integration — PWA push for iOS Safari
- Email notifications — fallback when neither push channel is available