When I download the lists now from IO I get an error message because they download with either an = or a + or both before the number.

Looks good to me. Thanks

This is what I've done (not live yet). Feedback welcome.

1) Phone numbers are validated when saving. So "123-1234" is invalid, but "416-123-1234" is valid and so is "1-416-123-1234".

2) Phone numbers are formatted for display as "(416) 123-1234" everywhere they appear.

3) Phone numbers in the CSV downloads will include country code and be formatted as "+1 (416) 123-1234" (provided it's a CA or US country code). Support for other country codes work, based on the country selected for the curler when they fill in their profile. So you can't select "Canada" for your country, but give us a number with a "China" country code, but you could select "China" for country and give us a number with a "China" country code. I'm not sure yet if this will be an issue, but if and when it is, we may have to tweak. Supporting format standardization internationally gets tricky if you don't know the country code that should be applied.

4) Phone numbers when displayed will have a special "tel:" link, which means you can click / touch the number on devices that support calling (phones, Facetime, Google voice, etc.). The number within the link has formatting removed and country code included. E.g. "+14161231234". This is fine as it's machine (device) readable. The country code helps so you don't get that "forgot to dial 1 message" from the carrier.

Glad I found this. I was about to make that suggestion too!