Blogger.com: Totally ****. There is no number to call, no ch...
A Blogger.com customer review by GetHuman user ~south_uk31 from November 28th, 2017
Background on ~south_uk31's case
GetHuman: ~south_uk31 - can you tell our other Blogger.com customers when your case took place?
~south_uk31: Yeah. It was middle of the night, on November 22nd.
GetHuman: Did you reach out to Blogger.com, and if so, how?
GetHuman: And which of these common Blogger.com customer issues best describes the reason you wanted to talk to them?
(Shows ~south_uk31 a list of common Blogger.com problems)
~south_uk31: "None of those really matches why I wanted to contact Blogger.com that day." was why I was trying to contact.
~south_uk31's review of Blogger.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Blogger.com customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
~south_uk31: Totally ****. There is no number to call, no chat window. Something rang for around ** minutes, then I gave up. Good product, but appalling customer support.
GetHuman: Let's quantify your experience contacting Blogger.com. On a scale of 1 to 5, how easy is it go get help on a Blogger.com problem?
~south_uk31: I'd give them a one out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
~south_uk31: I'd give them a two out of five on communication.
GetHuman: And what about Blogger.com's ability to quickly and effectively address your problem?
~south_uk31: For that I would say one out of five.
GetHuman: And finally- any advice for other Blogger.com customers?
~south_uk31: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Blogger.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~south_uk31 taken from his Blogger.com customer service problem that occurred on November 22nd, 2017.