Contributor
•
2 Messages
Cannot activate Apple Watch NumberSync because of dash in my e-mail address
So, I just got my brand new Apple Watch series 5 and I want to enable cellular NumberSync. I tapped through all the sign-in and setup-up screens until I get to the confirmation screen to add my device to my plan. It's required that I enter my e-mail address so AT&T can send me updates about my order, but I keep getting a form error telling me to "Enter an email address" and I can't continue. The user name part of my e-mail address happens to have a dash ("-") in it, and if I remove the dash the form error goes away--but then that's not my e-mail address!
Are there any workarounds to this glitch, or do I have to wait for AT&T to (hopefully) fix the bug in their sign-up forms? Don't tell me to get a different e-mail address--this is clearly a bug in the sign-up forms.
Siddalee1028
Contributor
•
1 Message
5 years ago
It has been a ridiculous time waster and laborious process for me. I did everything on the watch, got through to AT&T on the watch and went through all steps, only to receive a screen telling me that a customer service person had to review it before activation. Waited a night and tried again. This time got an email saying that my order was received and that I would get my new sync number to activate it in the next 24 hours. Day 3, I have been on the phone with 4 different people for more than 2 hours, gotten a credit check for this $10 additional charge/line, and it is STILL NOT ACTIVATED. They finally let me off the line because it was going to take “quite a bit more time” to process and they would call me back. I will be exploring other service providers soon. This is absurd.
0
0
mmm-mmm
Contributor
•
2 Messages
5 years ago
An update on this issue...
I contacted AT&T support about this problem. After spending over three hours with support, and getting shuffled between several people, they were able to manually add NumberSync to my account--but it still didn't work. They opened a case and told me it would be resolved within 24 hours, but it wasn't. Finally, after about 48 hours it started worked.
So difficult and such a waste of time for something that should "just work"!
0
0