+

Getting Started (3)

+

Ai Configuration (5)

+

Woocommerce Integration (6)

+

Chatbot Implementation (3)

+

Customization (2)

+

Conversation Management (2)

+

Chatbot Menu Settings (5)

+

Performance And Optimization (1)

+

Security And Privacy (5)

Push Notifications and Device Management

Reading Time: 3 minutes

Overview

Push Notifications let the Mobile App notify Administrators and WPiko Agents when a visitor sends a new message. This allows the team to react quickly without keeping the Mobile App open all the time.

WPiko Chatbot Pro also includes device registration tracking so site owners can see which devices are subscribed and remove old devices when needed.

How Push Notifications Work

Push Toggle in Settings

Push Notifications must be enabled in the Mobile App (PWA) settings inside WordPress.

When enabled:

  • WPiko generates VAPID keys automatically if needed
  • Eligible devices can subscribe to push notifications from the app
  • The app can send notifications for new incoming visitor messages

Device Subscription Flow

When a user enables push from the Mobile App:

  • The browser asks for notification permission.
  • The app registers a push subscription.
  • The subscription is linked to the signed-in WordPress user.
  • The device appears in the registered devices list in WordPress.

Supported Conditions

Push notifications require:

  • HTTPS or localhost-compatible secure context
  • Browser support for Service Workers
  • Browser support for Push API
  • Browser support for Notifications API

If the device or browser does not support push, the app will not enable it.

Registered Devices in WordPress

In the Mobile App settings page, you can review:

  • Device owner
  • Device label
  • Last seen time
  • Last push delivery result
  • Registration date

This gives you a basic management view for active push endpoints.

Device Labels

Device labels are generated from browser and platform details when possible, for example:

  • iPhone / Safari
  • Android / Chrome
  • Mac / Chrome

Test Push Notification

The settings page includes a Send Test Notification button so you can verify that your device is configured correctly.

Use this after:

  • enabling push for the first time
  • changing browser permissions
  • reinstalling the Mobile App
  • checking whether a device is still subscribed

Removing a Device

From WordPress Settings

Site administrators can remove a device manually from the registered devices table.

This is useful when:

  • a phone was lost
  • the app was uninstalled without turning push off first
  • an old browser subscription should be cleaned up

Automatic Cleanup

Subscriptions are removed automatically only when the push provider reports that the endpoint is expired or gone, such as HTTP 404 or 410.

Devices that are simply offline are not removed automatically.

Disabling Push from the App

When a logged-in user turns off push inside the Mobile App settings, the app unsubscribes that device and removes the related subscription.

Security Notes

Private Keys

Push private keys are stored encrypted.

Per-User Association

Each subscription is attached to the currently signed-in WordPress user, which helps keep device ownership traceable.

Best Practices

  • Test push on at least one real mobile device before launch
  • Remove unused devices from the settings page during routine maintenance
  • Use separate WordPress user accounts for each team member instead of shared logins
  • Revoke old Application Passwords when staff or devices change