Issue Summary

Unlike other contact methods, the mobile contact method is automatically added upon login on the mobile app if there wasn't an existing mobile contact method for their new phone.  Currently, this new Mobile contact method is automatically added below the old mobile contact method.

The issue arises when the "First mobile contact" is configured and enabled in Central Notification Template (CNT).

The existing "New Alert" notification rule would still be sending notification to the "First mobile contact" which would now be on the old phone unless the "Second mobile contact" is also part of the notification rule.  Then again, what if there are more than 2 mobile contact methods already, the new one would be the next one at the bottom of the mobile contact list and may never be notified because of the CNT.

Suggest Resolution

Below are a couple of possible suggested resolutions:

1. To always add the new Mobile contact method as the first mobile contact method and move the old ones down. This will allow the mobile app on the new phone to be the "First mobile contact" to receive mobile push notifications per existing CNT
2. Automatically move old unused mobile contact methods to the bottom. Currently, these old mobile contact methods are disabled but left to occupy the first mobile contact.

Workarounds

User or Admin would need to delete old mobile contact methods or drag the new one to the top