15 | Mobile Verification

This article outlines the dependencies and backpanel configurations needed for Mobile Verification.

This article outlines the dependencies and backpanel configurations needed for Mobile Verification. It also shows the process of this feature from the app perspective

Prerequisites 

• BurstSMS integration is required, prior to enabling Mobile verification
• To access and edit the "Sign Up, Tiers, Membership and Gaming Setup" setting, the following Role Privileges will need to be enabled
• Roles "Roles Maintenance" panel
• Privilege Flags: "System Setup"

This feature allows admin users to apply a phone number verification process when new customers signup to Myplace or when mobile numbers are updated from the app or Bepoz. Mobile Verification stops members from having duplicate mobile numbers and can act as another unique identifier for member searching. It can be toggled for each tier separately, which means that users have a choice of which tiers should have mobile verification enabled.

Mobile Verification has one dependency which is BURSTSMS. Users should have a BurstSMS integration setup prior to enabling this feature. The link below will show users how to apply the BurstSMS integration into Myplace.

Burst SMS integration

Backpanel Setup

After BurstSMS is integrated, to enable mobile verification follow the steps below:

1. On backpanel, click settings on the sidebar
2. Click Sign Up, Tiers, Membership, and Gaming Setup
3. In the Tiers tab, scroll down to a tier
4. On the right-hand side tick the flag, 'Mobile Verification on Signup' for each tier that the user would like it applied to
5. Click save changes to apply
6. Check Tier Mapping to see which tiers new signups will be applied to

App view

New Signup 

Based on the Backpanel setups. When a new user signs up on the app and is associated with a tier that has mobile verification enabled, either a hint will appear on the signup screen, displaying that the mobile is already in use, or If it is a unique number then they can continue the signup process.

After the signup screen, they will initially be prompted with email verification. Once the email has been verified, the user will then need to verify their mobile. An SMS code is sent to the mobile number and users will be prompted to input this code into the app.

Once the user inputs the correct digits, the member can then use the app. There is also a button to resend a new SMS code but it will have a cooldown time of 30 seconds.  

There is also a button to change the mobile number during verification if needed. When using this ensure that the number is unique or the user will be prompted with a hint outlining that it is already in use.

If the new user sign-up is associated with a tier that has mobile verification disabled they will only be prompted with email verification. 

Update Mobile Number

From Bepoz

• When a user is in a tier that has mobile verification enabled and they change their phone number from Bepoz. There are two scenarios that can occur.
1. If the mobile number already exists in Myplace or the SSO, within Bepoz the number will revert back to the previous digits.
2. If the number is unique, when the user refreshes the app they will be prompted to verify their new mobile again and are sent an SMS code to the new number.

• If the user is in a tier that has mobile verification disabled, they can simply change the number without any extra steps

On the app

• When a user is in a tier that has mobile verification enabled and they change their phone number from the app. There are two scenarios that can occur.
1. If it is a duplicate number in Myplace or the SSO, then a hint will appear outlining that it already exists and admin accounts will receive an email notice
2. If the number is unique when the user refreshes they are prompted to verify the email using the SMS code sent to their new number
• If the user is in a tier that has mobile verification disabled, they can simply change the number without any extra steps