Confirm phone # entered correctly

[lippytak]

This is the most important question. If someone makes a typo on their phone # then their odds of approval plummet.

[daguar]

How do we want to do this with the cleanest UX?

[alanjosephwilliams]

If we were to set aside return on investment considerations, I think the cleanest and most valuable UX would be the "Venmo Way", which would be immediate notification/confirmation that we have your number and can use it effectively. This would include:

• Breaking out the phone number solicitation into its own view
• Sending an SMS to the phone number entered on submission
• Giving the user the ability to opt-out of receiving the SMS—because either its not their cell phone, its not a cell phone, or they don't have the phone on them.

On the other end of the spectrum, we could simply *require the phone number

• *do basic validation on that input + require user action to skip providing a phone number in the event they do not have one.

In either case, I can imagine capturing some value by breaking phone number into its own view.

On Tue, Apr 7, 2015 at 8:27 AM, Dave Guarino notifications@github.com wrote:

How do we want to do this with the cleanest UX?

— Reply to this email directly or view it on GitHub https://github.com/codeforamerica/clean/issues/472#issuecomment-90610091 .

t: @alanjosephwilli p: 817 713 6264

[lippytak]

For v1 I was thinking of just asking the user to input it twice. Maybe 'confirmation' was the wrong word...I think SMS confirmation is overkill at this point.

[alanjosephwilliams]

You think I've prematurely optimized???

On Tue, Apr 7, 2015 at 1:57 PM, Jake Solomon notifications@github.com wrote:

For v1 I was thinking of just asking the user to input it twice. Maybe 'confirmation' was the wrong word...I think SMS confirmation is overkill at this point.

— Reply to this email directly or view it on GitHub https://github.com/codeforamerica/clean/issues/472#issuecomment-90730497 .

t: @alanjosephwilli p: 817 713 6264

[alanjosephwilliams]

I'm going to implement a narrowly scoped enhancement on this front this sprint:

• get input from the phone number form after focus moves to another field
• use jquery to get that input, and display it at the bottom of the page, in the plain language question "Your phone number is 555-555-5555. San Francisco HSA will contact you at this number before you can enroll in CalFresh".

Feel free to wordsmith that copy—but the point is to avoid asking a question that would need a response interaction to be sensible. Instead, simply give the assister and client a chance to see the number they entered (and by extension, change it) before they move on.