Originally published at: https://tidbits.com/2020/03/04/spring-forward-fail-back-apple-still-cant-tell-time/
Leap years have been on the Julian calendar since it was put into effect in 45 BCE. A recent customer-service failure shows Apple’s back-end developers are still trying to figure it out.
I worked for Apple when they changed their back-end accounting system (a third-party system whose vendor I don’t recall - sorry) at the beginning of this century. I remember the higher-ups in the chain singing the praises of how this new system would resolve the problems they were having paying commissions, etc. Of course, anyone who has actually been through an accounting system change-over knows how potentially disastrous this can be. Sure enough, when it actually went live, it was miserable for many of my colleagues. I would have thought the leap year thing wouldn’t even have been an issue (certainly not 20 years later!).
1 Like
This is the story the every decision made without the proper consultation of the people who use and maintain systems! Always. How terrible! Well, they apparently are still using it — or something that emulates it!
Sounds like we should to keep a copy of the paid AC+ invoice pdf on the device it covers.
I think you missed the part of the story at the end where my wife brought in the actual receipt and they still didn’t want to honor it because their systems are bad. But she eventually convinced them to see reason.
Yes I missed that part. You said the store clerk went and consulted with someone, then came back. Did you ask to speak with his supervisor or the store manager? They have more authority/access than 1st level support. I’ve had to do this a few times to get a problem resolved (I always get the name of each level person I speak with. However, I AM surprised the store staff didn’t check Apple’s list of well-known Apple commentators/authors and then just fix the problem. 
More complicated! I was brief, but my wife showed them the receipt, which has the agreement number and serial number on it, among other details. They declined to honor the warranty. She got me on the phone. I was polite but incoherent apparently over the speakerphone. They agreed to discuss it. They went off for five minutes and came back and said, well, ok. If she hadn’t have been persistent, they probably would have sent her away! That was their plan.
I’m not as well known these days, since I stopped writing the Seattle Times column years ago, and I try to make sure I never get special treatment as a journalist! (I’m sure you’re joking, but I don’t want special treatment—I want normal treatment to be great.)
Yep, I was which was why I used the “wink” emoticon.
I’d probably bring the incident to the attention of the manager saying that more training is obviously involved if the staff didn’t recognize an official Apple receipt. But at least it all worked out for you.
“Based on how fragile and inflexible everything is, I have a nagging suspicion that Apple still relies on ancient WebObjects code powered by exhausted hamsters.”
… Hey, Glenn! The WebObjects stuff was the good stuff! Yea, hamsters!
Not all Apple “geniuses” are so difficult. Years ago I had a friend visiting form out of state; her Macbook Pro had a swelling battery that was obviously defective. I took her to a nearby Apple Store. The “genius” took a look at it and asked if we had the receipt for it, which was generally required for the repair program involved (bad battery replacement); we did not. Nevertheless, he said they had some batteries in the back; he took the MacBook Pro to and returned in 10 minutes, having replaced the bad battery with a good one. Best service I’ve ever had. Those batteries were dangerous. It left to themselves they would explode or simply catch fire. Knowing that I was very glad to get it replaced.
That’s not to say that Apple Store staff are not encouraged to blow off a customer with a problem they can’t, or don’t want to, solve. But sometimes they deserve credit for the high customer service rating they get. I’ve had other good experiences in an Apple Store. Maybe I’m just lucky. 
1 Like
It’s not just Apple, and it’s not just dates. The inability of major tech companies to foresee and/or fix what should be simple problems with everyday information continually blows my mind.
I had an issue recently with an online ordering system for a web store I’d used many times before. It simply wouldn’t place the order—no visible error message either. After several attempts on three different devices, I finally found the problem: my phone number was formatted incorrectly (with parentheses around the area code instead of just dashes). The only indication that the phone number was the problem was that the field border was dark red instead of black, dark enough that the difference wasn’t obvious on my MBP (I didn’t catch it until I tried placing the order on my iPhone). (I was persistent because it was a one-day sale involving items I’d been waiting to see go on sale, and I didn’t want to miss the sale window waiting for a customer service response.)
The thing is, I hadn’t made any changes to my contact information; the phone number was formatted exactly as the site had already filled it in from my account! I emailed customer service about it after I had completed my order, and they responded that they had recently made some back-end changes in their ordering system such that parentheses were no longer allowed in phone numbers.
The fact that my existing stored phone number had not been converted to the new formatting requirements would suggest that many other, if not all, existing customers had the same issue. Yes, it’s a confluence of two problems (the actual formatting problem, and the lack of useful error messages), but I wonder how many potential sales were lost that day because other customers encountered the same problem and simply gave up.
2 Likes
I’ve had similar problems with both the STANDARD phone number format (area code) and what I call the “NERD” format of area code-exchange number-individual number. Turned out the software only allowed the NUMBERS ONLY format 1234567890 yet still allowed the ENTRY of both the Standard & Nerd formats; it just wouldn’t let you send the form and didn’t give any indication of the format.
Your actual main problem was the company implementing the new ordering system BEFORE they changed their customer database to comply with the new system.