Verification Code

After introducing all PII, ST agents will have to request applicants to check their email address to perform a verification process for us to make sure that the email account is real and that it belongs to the them. They will receive an email with a verification code that will have to be introduced in the Quest app.

20.png

If the email verification is successful, the following message will be displayed:

21.png

On the other hand, if the code introduced is invalid, the following message will be displayed:

22.png

For these cases, ST agents will have the RE-SEND CODE button, to perform the verification again. After the information is introduced, Street Team Agents will be requested to take a picture of them, for audit purposes.

23.png

If the picture is clear and legible, the CONFIRM button should be pressed, if otherwise, press the RETAKE button to take a new picture.


Device Option

In this section, applicants will be presented with the device options available. For the moment, the Keep Your Own Device option will be the only one available.

24.png

If the first option is selected, the following pop-up will request the applicant to indicate which Device Type they have (iOS, Android, etc.) In the Identification Type section, ST agents can select between Phone Number and IMEI/IMED. If the first option is selected, the Phone number should be provided, and then the system will also request the last 4 digits of the IMEI. But if the IMEI option is selected from the beginning, applicants will have to provide the number, that normally has 15 to 18 digits.

25.png

The Quest app will always provide instructions for applicants to know how to find the information requested.

26.png

If the validation is successful, the ST agent will be able to continue with the enrollment process. But if the device cannot be validated, the Quest app will inform that the device is not compatible, and the enrollment process cannot be completed.

27.png

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.