Google's Communication Problems Continue: Blogger Can't Get His Blog Turned Back On After Six Months
from the not-cool dept
For the last few months, we've been seeing more and more stories about Google's communication problems with users. This has always been something of an issue with Google -- which seems to prefer algorithms to humans whenever possible -- but we're seeing it so often, that I'm really beginning to wonder if this is a serious problem (or potential Achilles heel) for the company. It seems like Google could take some serious lessons from a company like Zappos that treats everyone like a human and goes to amazing lengths to resolve any problems. Instead, too often dealing with Google feels like tossing a request into a giant shiny white box where you may or may not ever hear back -- and, if you do hear back, it's unlikely to be particularly helpful.For example, we've already talked about the problems many suddenly banned advertisers have had in getting any kind of explanation from Google (let alone any recourse). On top of that, there was the situation with users being locked out of their Google docs, with little communication from Google available. This is really potentially quite damaging. It gives the impression of a giant white wall between users and the company in an age where having some sort of human connection to a company is increasingly important. I recognize that Google has it in their DNA to be afraid of people gaming the system, but in shutting itself off from the world, it may be creating more problems for itself.
The latest example is instructive. Jack Yan alerts us to his own writeup of the struggle he's gone through to try to get Google to reinstate a blog it incorrectly deleted back in July. You can read the forum exchange that began in November (after many months of going through the regular official channels and being told to "wait 2 days" over and over again with nothing coming of it). Jack summarizes the forum exchange this way, with Google's explanation first, and his response in parentheses:
The exchange is incredibly frustrating to read, and I'm amazed that Jack remained as calm as he did through it all. In fact, he notes that Google itself had a cache of the site for a long time -- including when he kept submitting for reinstatement and getting told to wait two days. But now Google's own cache is gone, so he's pointing the Google folks to Yahoo's cache to prove the blog is not a spam blog. And Google's response appears to be nitpicking over the search term, rather than the cache itself, or looking for ways to get the blog back. I know plenty of folks who work at Google and care deeply about their products and how they're perceived, but I'm amazed at how badly the company seems to handle basic customer service issues like this one.
- You probably didn't follow the suggestions. (Yes, I did.)
- You didn't do it at the right time. (Yes, I did.)
- Wait two days. (Waited, nothing happened.)
- Wait till this afternoon. (Waited, nothing happened.)
- There's no cache of it. (Yes, there is.)
- You're not the owner of the site. (Owner steps in and says I am allowed to follow this up for him.)
- There's no cache of it. (Yes, there is.)
- I'll ignore the main link you give and focus on a second one that is less useful. (Look at the first one then.)
- There's no cache of it. (Yes, there is.)
- There's no cache of it. (Yes, there is.)
- Your search term is not relevant to this. (But it shows you a cache of it.)
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: blogs, communications
Companies: google
Reader Comments
Subscribe: RSS
View by: Time | Thread
oh chuck
http://photos1.blogger.com/blogger/5304/92/1600/Chuck%200a.jpg
[ link to this | view in thread ]
simple solution
[ link to this | view in thread ]
[ link to this | view in thread ]
Re:
Alternatively, treat him as a "content supplier." Most good companies listen to their suppliers.
[ link to this | view in thread ]
Paying Customers
http://www.google.com/apps/intl/en/business/features.html
It's actually an interesting question -- how do you build a scalable user support and feedback service? Code, memory, CPU time, and bandwidth are all relatively cheap compared to manpower but actual person-to-person contact is the hallmark of a good customer support system.
I think that'd be something you'd want to toss to the Insight Community Mike.
[ link to this | view in thread ]
[ link to this | view in thread ]
Re:
[ link to this | view in thread ]
Paying customers
FWIW, my school's a customer of Google Apps for education- virtually identical to business apps, except we get it free. We actually do get decent service and I've been able to get a real, live human being on the phone occasionally. Granted, they always have to pass me on to another department who might or might not call me back a few days later, but I've definitely dealt with worse paid tech support.
[ link to this | view in thread ]
Re: simple solution
IF A COMPANY CAN'T PROVIDE RELIABLE SERVICE FOR FREE, THEN EITHER CHARGE MONEY OR DON'T OFFER IT!
Why should it be okay for them to make promises and not keep them just because they don't charge?
[ link to this | view in thread ]
Simple Explanation
[ link to this | view in thread ]
If you want to run something, get a host and take care of it yourself. Don't depend on some other service to provide you tools that they can take away without notice.
With your own domain and software, you can host anywhere. Considering how inexpensive hosting is, it is almost foolish to use free tools.
[ link to this | view in thread ]
Re: Paying Customers
The real trick is how to combine automated support with human support so that the automated support and the human support are provided when at the exact appropriate times....
[ link to this | view in thread ]
[ link to this | view in thread ]
[ link to this | view in thread ]
[ link to this | view in thread ]
Re:
[ link to this | view in thread ]
Re: Re: Paying Customers
Person-to-person contact does not automatically mean good support, but all else equal, I think it's a plus. Until we get really some good AI, automation only helps us deal with foreseeable problems. A big chunk of customer support is about what happens with the unforeseeable (e.g. bugs) and for that you need people.
Plus there's a tremendous psychological benefit for the user to having the actual name of someone you can hold responsible for your problem.
IMHO, the problem is that you have small teams of developers creating products that get millions of users overnight. This allows scenarios where a single engineer can push a change that benefits 99% and screws over the remaining 1% in all sorts of strange ways.
Because that 1% consists of edge cases and outliers, you'll probably have to sort through their issues on an individual basis. Yet because you have millions of users, that 1% is really quite large. Rather than spend his time helping out the 1% he screwed, the engineer's time is better spent working on another iteration of the product designed to help out some other 99% of its users.
That's not much comfort if you're in the 1% though.
[ link to this | view in thread ]
Re: Re: Re: Paying Customers
So I think we're agreed that there are those 1% cases when a human is essential for good service. And there's also the "genius bar" examples -- where if the customer *knows* his/her problem can only be fixed by a human, that a human customer service rep should be readily available. The key is trying to augment those humans as much as possible with technology so that their efforts are maximized.
[ link to this | view in thread ]
Quick follow-up from Google
With that said, I had an e-mail exchange with Jack on Monday, which he documented here:
http://jackyan.com/blog/2010/01/googles-rick-klau-restores-social-media-consortium/
He found my e-mail address on another comment thread, reached out and we resolved the status of his blog. As he explains, this particular blog was very much a borderline case. Our automated systems rightly identified a number of indicators that mirror known patterns on actual spam blogs; when reviewed by our review team (after an appeal was filed) they still saw it as likely a spam blog.
In this case, oddly enough, the automated and human systems worked - up until Jack went to the forums. We're analyzing what broke down there, and actually began actively evaluating alternative systems last month to better scale to support our millions of users.
We do not hide behind the fact that we're a free product - we absolutely have an obligation to ensure that Blogger works for our users and that we earn their ongoing use.
I'll have more to say on this once I have a bit more info, and will be updating our users about any changes we may make in our support approaches on Blogger Buzz (http://buzz.blogger.com/).
In the meantime, anyone who'd like to reach out directly about their Blogger experience is encouraged to contact me directly: rklau -at- google.com.
--Rick
Product Manager, Blogger
[ link to this | view in thread ]
Restored
Rick Klau at Google has indeed fixed things for us and we had a private discussion on why the case was borderline.
I wish we had come across someone like Rick earlier. Only yesterday, I had a discussion with a mutual friend who identifies him as one of the good guys inside Google. The courteous and efficient way we were finally dealt with confirms that. His 24-hour turnaround, from my email to the restoration, is to be commended.
However, I am still rather miffed at what I had been through on the forums, which was frustrating. My ‘Christmas panto’ blog post was directed mostly at that experience, because I still found the procedure obstructive. The last post in the Google support thread was HTML code from the Yahoo! cache (in response to Chuck pasting the frameset code [!])—which was strangely deleted within a day. It was as though he, or someone on the forums, did not want to see that proof.
For my own (former) Blogger blogs, I had opted for FTP publishing, which I would recommend—and have done so for Vincent.
I am glad to note that there is one rule for everyone—provided you can get someone like Rick Klau who can make a judgement on whether the complainant is legit or not. Go through those forums, as I have, and there are a lot of sploggers crying foul over deletion, and those guys do not deserve to get their blogs restored. I’m guessing Rick checked me out, and saw that I had a pretty decent and honest record of blogging—and knew that he wasn’t dealing with a splogger.
On the forums, though, could Chuck have not done the same thing?
Thanks to Techdirt, there’s now a proper record of these incidents, and Rick has kindly offered his contact details—which hopefully can be a remedy to others who have had to fight for such a long period. At the end of the day, something good came of this for other legit bloggers.
[ link to this | view in thread ]
Re:
So in that case, it might even be better to host your own website on your own server, but then you'd also have to get a business DSL line to have a decent uptime, except that some providers have bad customer support as well. So you might want to start your own DSL provider business to make sure that you have proper customer support.
Wait, what was this for again? A simple blog?
[ link to this | view in thread ]
Re: Re: simple solution
Seriously though, there are lots of people out there who don't need 5 nines service for example. There is a whole spectrum of reliability being demanded by different segments of the market, along with a spectrum of ability and willingness to pay.
If they're not meeting a group of people's reliability/price tradeoff then something will have to give otherwise they'll just lose money. There's nothing inherently wrong with the company not keeping promises, they'll just lose customers if they are breaking their promises more than they had promised to do so ... if that makes sense ...
[ link to this | view in thread ]
[ link to this | view in thread ]
Re: Re: Re: simple solution
Sure, it's there choice, but this post isn't saying it isn't. This post is part of the consequences of that choice.
[ link to this | view in thread ]
Re: Re: Re: Re: simple solution
[ link to this | view in thread ]
Re: Re: Re: Re: Paying Customers
[ link to this | view in thread ]
Re:
Where is the problem?
[ link to this | view in thread ]
Re: Re:
[ link to this | view in thread ]
Re: Quick follow-up from Google
To all the people that said "if you want to complain you have to pay", "it is okay for free services to have bad service", this part of the reply says it all:
"we absolutely have an obligation to ensure that Blogger works for our users and that we earn their ongoing use."
Straight from the horse's mouth: YOU ARE ALL WRONG.
And kudos to Rick Klau for caring and trying to fix the issue, eventually.
[ link to this | view in thread ]
Re: Re: Quick follow-up from Google
When did customers start feeling like they owe companies some sort of sympathy or understanding?
[ link to this | view in thread ]
Why would you be? I can't even find an email address or contact form for Google any more. They want everyone to use the convoluted Google Groups to get help.
I'd like to actually be able to talk to someone there to complain about the absolutely idiotic practice of showing me web pages that don't have ANY of the words I searched for. "These terms are only found in links pointing to this page." Well then show me that f****** page instead of this one, which has absolutely nothing to do with what I searched for!!!
[ link to this | view in thread ]
As for the free service argument, sure it's free in terms of money, but my personal information and behavior is valuable to me, and they make money off the fact that I am will to post it on their website. They also make money any time anyone clicks an advertisement. So yes the service is free in terms of zero dollars, but the users are what gives Facebook, and Google it's value.
Also: Mike my facebook account has been disabled since 12/22 without response from facebook, if you would like to post an article about it I will demonstrate the point that I make in the first paragraph. Internet businesses still act like normal businesses in a lot of ways.
[ link to this | view in thread ]
Gone again
[ link to this | view in thread ]
Back again
[ link to this | view in thread ]
This seems
[ link to this | view in thread ]
Re: Re: Re: Re: simple solution
(a) provide a reliable service with a charge if necessary, or
(b) don't provide a service
missing out (c) provide a unreliable service for free / less than a reliable one.
Granted the takeup will depend on competitors and how much unreliability people are willing to put up with to avoid shelling out.
Plus, public transport in the UK is a fantastic example of how to provide unreliable service *and* charge a lot for it. Gotta love monopolies.
[ link to this | view in thread ]
Worse things under the sun
I had an idea for a site and Google Blogger allowed me to test it, without cost. I may well upgrade my idea to a full website at some point in the future - it just depends on how successful the results are.
Yes, of course I prefer to have my own server and yes, it's a challenge to make my 'blogspot' behave as I would like - but it's been a fun challenge to be honest and I have succeeded in getting the layout I wanted. It now has the appearance of a website, not a blog. If you want me to do that for you too, check out my free offers.
Horses for courses, I say. Just make sure that you backup any content you really couldn't cope with losing - just in case.
[ link to this | view in thread ]
Google really does stink nowadays
Bitterly disappointed in it....it's gotten glitzier, but WORSE, as time goes by.
[ link to this | view in thread ]
Blog deletion by Blogger
[ link to this | view in thread ]
[ link to this | view in thread ]
Password reset
After the above incident, I deleted all my Blogger blogs. I was on FTP publishing myself, but after seeing what Vincent went through, I decided that Google could not be trusted. To this day, Google still claims I have one blog left but wont show me what it is (its not on my dashboard). Rick Klaus successor proved to be far less on the ball, and one of the support guys claims its a blog that I have no connection with at all.
Blogger remains a total mess. Avoid at all costs.
[ link to this | view in thread ]
Re: Restored
Too bad, the same automated system disabled it again on Saturday and not yet restored.
I don't know why someone that loves Blogger so much will have to be going through this.
I wish there is a premium Blogger support. I won't mind paying.
I need help please.
[ link to this | view in thread ]
Simple Solution
[ link to this | view in thread ]
Re: Restored
[ link to this | view in thread ]