Page tree
Skip to end of metadata
Go to start of metadata


ONEcount forms have a progressive lookup feature whereby an existing user can be identified by demographic information as it's being entered. The system will look up the user based on the information being progressively entered in the form – e.g. email, first name, last name, city – and auto-populate the form when the user is identified. (The fields used for lookup are set in the Question Manager. See Question Manager documentation for more detail.)

If a user is trying to log in and/or subscribe to a product and fails Lookup and/or Login on the Lookup/Login page or if Lookup/Login functionality has been overridden/bypassed, the user will be directed to the blank subscription/registration form. Even though a registered/subscribed user has failed Lookup/Login based on entering incorrect/unidentifiable information in Lookup or not having his/her username and password for Login, if in your ONEcount database, he/she can still be identified by the ONEcount system by progressive lookup functionality.

Following is detail of the functionality and process as the user will experience it after failing initial Lookup/Login or bypassing Lookup/Login and being presented with a blank form.

Process

With No Lookup/Challenge Questions selected in Form Builder:
Example: User Enters First Name, Last Name, and City and is potentially identified

1. Record has: Email = no, Cell Phone = no

user presented with prompt asking for email or cell # to send verification code
user enters cell number
user gets verification code from text message
user enters code
form auto populated, and
cell # added to profile

OR

user enters email address
user gets verification code from email
user enters code
form auto populated, and
email address added to profile

2. Record has: Email = no, Cell Phone = yes

user presented with prompt asking for email or cell # to send verification code
user enters cell number
user gets verification code from text message
user enters code
form auto populated

OR

user enters email
user gets verification code from email
user enters code
form auto populated
email address added to profile

3. Record has: Email = yes, Cell Phone = no

user presented with message the verification code was sent to email address
user gets code from email
user enters code
form auto populated

4. Record has: Email = yes, Cell Phone = yes

user presented with message the verification code was sent to email address
user gets code from email
user enters code
form auto populated

With Lookup/Challenge Questions Selected in Form Builder:
Example: User enters First Name, Last Name, and City and is potentially identified

1. Record has: Email = no, Phone = no

user presented with lookup question
user passes lookup *
user presented with "Email Required – Provide Email to Send Username & Password" pop-up
user enters email address
form auto populated
user receives email w/username and password

2. Record has: Email = no, Phone = yes

user presented with lookup question
user passes lookup *
user presented with "Email Required – Provide Email to Send Username & Password" pop-up
user enters email address
form auto populated
user receives email w/username and password

3. Record has: Email = yes, Phone =no

user presented with lookup question
user passes lookup *
form auto populated

4. Record has: Email = yes, Phone = yes

user presented with lookup question
user passes lookup *
form auto populated

    • On fail lookup, a message to to complete the blank form is displayed.*
      • Lookup/Challenge Questions are selected in the Question Builder. Plase see Question Builder* documentation for more detail on how to select Lookup Questions.

You should set at least three lookup questions in the Question Builder. With more questions there is more probability that the system will present the user a challenge question instead of sending a verification code. Challenge/Lookup questions will only pop up if the question value is not empty; and they should be questions that are not being answered in the form. More selected lookup/challenge questions means more of a chance that a user has a response in the database to one of them and will be able to answer rather than requiring a verification code.

 

  • No labels