XVerify Email Widget: Require a Validate address button on the widget

  • watchhelp
    Asked on January 16, 2019 at 11:50 AM

    Hello.

    We use the Xverify email widget to collect email addresses with the new card/one at a time form layout. It is by far the best way to collect accurate email data: very easy on the user and inexpensive.

    Here's the issue: if we make the field required, some folks enter correct addresses, the validation fails and they can't proceed.

    If we make it NOT required, the form-filler never sees the validation result, i.e. they hit Next and may have left bad info. 

    What we need is a "Validate Address" button on that widget. Once a positive result is returned, they can hit Next. If it is NOT validated, there should be an option "I know this address is correct" then they can hit Next.

    Can this be done and soon? 
    Is there a work around?

    Thanks,

    Mark



  • Girish JotForm Support
    Replied on January 16, 2019 at 1:54 PM

    I cloned your form and was able to replicate half of the issue noted.

    i.e. When I made the email field as "Not required", entered the wrong email address, clicked on Next, the form progressed to the next page. I was able to see the error only when I went back one step.

    When I made the email field as "Required" and entered the correct or wrong email address, it worked perfectly. Please see my screencast below.

    1547664191screencast 1701 Screenshot 10

    I can see here that the validation is not failing. Could you let us know what error is popping up when the field is set to required due to which your users can't proceed?

    Currently, the Xverify widget does not have the "Validate address" button. I can forward this to our developers for review, but will not be able to provide you an ETA for this or when or if it will be implemented.

    Meanwhile, you can try our Email Validator widget for this purpose. You can refer the below guide for reference:

    How-to-Verify-an-Email-Address-Before-or-After-Form-Submission




  • watchhelp
    Replied on January 16, 2019 at 3:43 PM
    Thank you gerardw for your reply.
    1. NOT Required: you saw exactly what I saw: bad data can be entered and
    the user will never know it (unless they go back, which won't happen) This
    means the entire goal of the widget which is to collect valid email
    addresses is negated.
    2. Required: You wrote "Could you let us know what error is popping up when
    the field is set to required due to which your users can't proceed?"
    I do not understand the question since your video SHOWS that the user
    cannot proceed once a bad address is given. You got an error message saying
    "Registrations are closed for the day" and that prevents the user from
    proceeding. That IS the problem.
    3. Thank you for the idea of using Email Validator widget instead. I am
    familiar with it but it is a much less desirable solution. It forces the
    user to do a second step which is really not acceptable in many use cases.
    4. I appreciate you sending this concern to the engineering team.
    *Since the collection of valid emails is likely THE most important piece
    of data for most form users and this is by far the best way to do so, I
    would humbly ask the engineering team to prioritize this issue. *
    This is not the first time I am raising this issue.
    Thank you!
    Mark
    *Mark Ryan Pollock, Operations Manager*
    800-896-8669 / 770.263.8669 /
    mark@watchhelp.com / www.HurleyRobertsService.com

    6990 Peachtree Industrial Blvd. Ste. C
    Peachtree Corners, GA 30071
    *Expert Watch Repair Since 1980*
    *Leave us feedback: **https://getfivestars.com/f-2121
    *
    ...
  • Girish JotForm Support
    Replied on January 16, 2019 at 4:06 PM

    In response to the second point mentioned above, please note that error message "Registrations are closed for the day" came up only when I entered the wrong email address. I was not able to progress to the next page even after clicking on the Next button.

    After that, I entered the correct email address, the email got verified and I was able to move to the next page of the form.

    I was actually trying to replicate the below query:

    Here's the issue: if we make the field required, some folks enter correct addresses, the validation fails and they can't proceed.

    While testing, I was able to verify the email when I entered the correct address and the validation did not fail. 

    Thank you for your patience.

  • watchhelp
    Replied on January 21, 2019 at 3:43 PM
    Hello again,
    I apologize, I see I am not being clear.
    Let me explain. There are THREE kinds of email addresses.
    IF EMAIL *IS* REQUIRED:
    1. MickeyMouse@gmail.com = entered perfectly, will pass validation and form
    will proceed to next card -> GOOD
    2. MickeyMouse@gmai.com = entered INcorrectly. will not pass validation and
    customer will be forced to correct before continuing. ->GOOD
    3. MickeyMouse@LittleKnownEmailServer.com = entered perfectly. will NOT
    pass validation even though the address is fine. Customer is now stuck. ->
    BAD
    IF EMAIL *IS NOT* REQUIRED:
    1. MickeyMouse@gmail.com = entered perfectly, will pass validation and form
    will proceed to next card -> GOOD
    2. MickeyMouse@gmai.com = entered INcorrectly. will pass validation and
    customer will continue with form not realizing he gave us bad data -> BAD
    3. MickeyMouse@LittleKnownEmailServer.com = entered perfectly. will NOT
    pass validation and customer will continue with the form -> GOOD
    This is not hypothetical, we have had folks give us email addresses that
    are clearly valid yet fail the validation by the widget.
    I hope this is more clear.
    The widget is designed with a one page layout in mind. On an "old" format
    Jotform, the customer moves the cursor to the next field, the widget does
    it's job to try to valid the address. If if fails, a red error message
    alerts the customer. At least then, typos were prevented. (Little know
    email server emails were still a problem if the field was required...)
    With the new one question-at-a-time, card format this widget no longer
    serves it purpose properly.
    The solution:
    This is a screenshot from a USPS page.
    [image: USPS Proceed anyway option.png]
    The physical address is submitted in an attempt to validate and
    standardize. IF it fails validation, the "Proceed Anyway" checkbox pops up
    and allows you to continue despite the fact the address is seen as NOT
    valid.
    This feature should be added by Jotform to this widget, that solves all
    these problems.
    Again, because email is the single most important piece of data AND Xverify
    is by far the best way to collect it I ask that this be addressed ASAP.
    Thank you,
    Mark
    *Mark Ryan Pollock, Operations Manager*
    800-896-8669 / 770.263.8669 /
    mark@watchhelp.com / www.HurleyRobertsService.com

    6990 Peachtree Industrial Blvd. Ste. C
    Peachtree Corners, GA 30071
    *Expert Watch Repair Since 1980*
    *Leave us feedback: **https://getfivestars.com/f-2121
    *
    ...
  • Girish JotForm Support
    Replied on January 21, 2019 at 4:42 PM

    Sorry for the inconvenience caused. Regarding your concern:

    3. MickeyMouse@LittleKnownEmailServer.com = entered perfectly. will NOT
    pass validation even though the address is fine. The customer is now stuck. ->
    BAD

    I checked this again and the customer will be stuck since the email address is entered incorrectly. I can see that you have attached a picture into the thread, but it is not visible. Please attach the screenshot by referring to this guide:

    https://www.jotform.com/help/438-How-to-Post-Screenshots-to-Our-Support-Forum

    Regarding your last concern, please note that it has been raised to our backend team for evaluation. We will update you via this thread when an update comes up.

    Thank you for your patience.

  • watchhelp
    Replied on January 22, 2019 at 11:49 AM

    1548175730USPS Proceed anyway option Screenshot 10

    Thank you for pushing this concern up the line.

    I appreciate that!

    Mark

  • Kevin Support Team Lead
    Replied on January 22, 2019 at 1:12 PM

    Thank you for the image, I can see my colleague already opened a feature request for this, although we cannot provide an ETA, we will keep you updated via this thread. 

    Thanks.