3 FAQ

1. Can the same mobile device be enrolled for multiple users for push notifications?

   No, the same device cannot be enrolled for multiple users for push notifications. A push token is generated for a user + device combination and if there is already a push token registered for the device and another user re-installs the application then the earlier token is invalidated and overridden.

2. Is it possible to have privacy/priority settings for push notifications, that is, an option to not display the message content on the lock screen?

   Currently, this feature is not supported. The message content will be shown to the user even if the device is locked.

3. Will an application upgrade/update require re-registration for push notifications?

   No, the application upgrade/update will not need re-registration for push notifications. The earlier registration holds good.

4. Is the delivery of push notification to the end user from the respective OS servers audited in OBDX?

   There are logs available in the system about the delivery of the notification to the iOS or Android server. The delivery of the notification to the end customer on the device from the respective servers (iOS and Android) is not available in OBDX.

5. Does OBDX have in-app messaging enabled to send messages to customers like mandatory app update to latest version?

   No, in-app messaging capability for mandatory app updates is not supported.

6. How many maximum number of devices can be registered to get push notifications for a particular user?

   There is no restriction on the maximum number of devices that can be registered for push notifications.

7. If a customer/admin de-registers a device for push notifications from the front end, how can it be re-enabled to get push notifications back again?

   The user can reinstall the app. On reinstalling, the user will be asked to enable push notifications for that device and once the user logs in, a push token can be associated with the user.