Skip to main content

My black friday nightmare with Walmart.com, Part 2

One of the things I left out of my post about my nightmare buying a TV from Walmart.com was that I used Consumerist's recipe to launch an EECB (Executive Email Carpet Bomb) on Walmart. Following the recipe, I composed an email and sent it off to 4 variants of the email of their Executive Vice President of General Merchandise. So who called me yesterday? Amberly from Walmart.com's Executive Escalation Department. Yeah it got that serious! She explained the same thing as the other robotic agents I had been talking to. However she promised to escalate to the billing dept. Did I believe her? Not entirely but she sounded more confident than the others. Especially since she was from the Executive Escalation Department. I asked how she learnt about the case and she said they got my email (sweet!).

About 30 minutes later, Amberly called me back and she had actual information for me. Apparently, orders are randomly flagged for review by Walmart. My first order for the 55 inch was flagged and when they (Walmart.com) called AMEX to verify my name, the data didn't match up. Which is certainly news to me since AMEX has always known me as "Tundey Akinsanya". So after the first order was unsuccessful, my credit card was flagged and subsequent orders with that same card were subjected to a review. So that's why ordering the TV 5 times didn't help; having a customer service rep clone the order didn't help; having a customer service rep take the order over the phone also didn't help. Solution: have Lara use her card (same account but different number) to buy the TV and then call the Executive Escalation Department to refund me the difference in price.

All that just because I wanted to get the free extended warranty from AMEX, the cheapest price from Walmart and the convenience of being able to return to a physical store. The 5th order was placed yesterday and so far no cancellation email.

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology.

InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options:

convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations)use one of Al Gore's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously. You'll need every bit of time you can get.
quit immediately while you still have your sanityFirst, InfoPath:

To me InfoPath is like programming in assembly language. Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button:

in most technology: buttonA.enabled = false (or something similar).

In InfoPath, you simply can't do this.…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horri…