Send rider contact details to driver only AFTER a match has been confirmed about backend

[dmilet]

hmm. How is the driver supposed to contact a proposed rider to confirm if the information is correct, prior to accepting.
Should drivers accept matches before confirming the details with the rider ?

[sasjkia]

@dmilet I understand your concern but the good thing is that the ride cancellation feature works well and I've tested several times to ensure that the rider can go back into the pool and get matched again. So now it's a case of ensuring the UX makes the process clear.

We need to avoid sending out the full address and contact details of potentially vulnerable people to a whole pool of drivers. At least if people have to accept first, we know who has the details. I can't really think of another solution and I don't think this change is going to prevent people from using the service.

[dmilet]

Do I remove

• address
• phone number
• email address

Anything else?
Please confirm
Thanks

[sasjkia]

Keep address but remove street number. Does this require it be a separate entry field on the front end?

Remove rest pls.

[dmilet]

Yes we don't currently separate street name and number
I'll remove the entire address for new

[sasjkia]

Best to pause on removing the address; there's a frontend issue pending that will separate the street number from the name

[dmilet]

Not sure how it's going to be implemented. I never had to split house number and street name on any form I had to fill in. Do we really want to ask our users to do that?

[sasjkia]

@dmilet it's not too uncommon to have multiple address lines. We can ask Tino, who has 10 years of US experience, for some suggestions.

Alternatively, is there a way to strip out any numbers in that field on the database side?

[dmilet]

See the usual format for addresses
http://www.bitboost.com/ref/international-address-formats/united_states/

I have never seen a web site that asks to split house number from street name, they're always on the same line

[sasjkia]

Are you able to hide numbers from the database side?

If not, my consideration is rider safety above all here; I think there are UX solutions to avoid confusion/form abandonment.

[dmilet]

I think it's too complicated to hide the numbers from the back end
5th avenue
becomes
5 avenue

and god knows what else

If safety is your concern, let's just hide everything but the zip code

[sasjkia]

I'd considered it but it seems that zip codes are quite big in places

[dmilet]

so the process is:

1. driver accepts proposed match, based on zip code (remember we calculate distances based on zip codes only, that is a very rough estimation of the distances anyway)
2. driver gets full contact info
3. driver calls/emails rider to confirm in person
4. driver may decide to cancel the match if too far not not suitable