@rokstarI agree with your frustration but the watch IS new territory to Rogers. I can 99.9% guarantee you that almost everyone at Rogers save a very very very few higher ups did not know about this watch launch/watch support until the day it was announced or immediately before then. Apple doesn’t allow anybody and everybody access to what they classify as secret information.
So you have this activation debacle caused by two main reasons:
1. Customer support/techs/almost everyone at Rogers learning on the fly about how to diagnose and solve problems related to the Watch activation.
2. Seems like Rogers did a pretty terrible job beta testing the system. Or it could point back to point #1....not enough people knew about the launch to get a large enough sample size to properly beta test the system.
3. Rogers just doesn’t spend money to make sure things go smoothly day 1. Look at almost every iPhone launch when the activation servers crash. They could make their server system more robust but they don’t because the incremental cost of doing that is not worth it to them. Guess they’d rather their customers suffer a bit initially.
Look...I spent like 9 days trying to get my Apple Watch up and running. So I’ve been through some severe punishment. But I know there’s not much we can do other than to accept it or look elsewhere. Rogers isn’t going to spend the money to make sure things go smoothly day 1. They’re just not going to.
Also, re: the watch reservations, I have no idea why things are so slow. I can only speculate it’s a combination of lack of stock (Rogers shipped a ton more 40s than 44s and the stock situation is the EXACT same with Apple - tons of 40s, very few 44s) as well we perhaps holding back on the bulk of shipments until the activation system is at least semi operational.
From a customer perspective though, I agree with you. We shouldn’t really have to care what it takes for Rogers to get it right. Things should just be done right day 1. I don’t know if that’ll ever happen though.
