Skip to Content
3-05-2012 @ 4:00PM
And in all of this, only one guy is even remarking about the fact that someone had a job to do, and failed to do it, and believes there should be consequences. Firing? No, I don't think so. But something, yes. And something equal to the fact that the company has been shown to be incompetent in their software QA.Simmer down, you. Listen for another few seconds. Is Blizzard incompetent? No, of course not, and the evidence supports that statement. But perception, particularly in the field of customer service, is *everything*. And whether you want to make this all a group endeavor or not, that group was made of individuals who each dropped the ball. The job didn't get done because at least one set of hands that should have been there to catch it, didn't. For a company that has lost 2 million subscribers in about 2 years, failures like this should be taken seriously, and that old "sorry about the inconvenience" starts to sound insincere -- which compounds the problem.Bottom line: someone(s) at Blizzard should be getting "The Talking To"(tm), and if they're not, then Blizzard is demonstrating with their actions that continued erosion of their customers' regard isn't significant. *That* is a problem not just for Blizzard, but for their customers. That is, for *Us*.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.