Blogger.com: I would like a refund on postage on goods retur...
A Blogger.com customer review by GetHuman user ~Jean Davies from November 19th, 2017
Background on ~Jean Davies's case
GetHuman: ~Jean Davies - can you tell our other Blogger.com customers when your case took place?
~Jean Davies: Yes. It was middle of the night, on November 18th.
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 ~Jean Davies a list of common Blogger.com problems)
~Jean Davies: "None of those really matches why I wanted to contact Blogger.com that day." was why I was trying to contact.
~Jean Davies'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.
~Jean Davies: I would like a refund on postage on goods returned to the sum of ***£**-**. The goods returned were from Bright-life and the receipt was on the parcel.
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?
~Jean Davies: 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?
~Jean Davies: I'd give them a one out of five on communication.
GetHuman: And what about Blogger.com's ability to quickly and effectively address your problem?
~Jean Davies: For that I would say two out of five.
GetHuman: And finally- any advice for other Blogger.com customers?
~Jean Davies: 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 ~Jean Davies taken from his Blogger.com customer service problem that occurred on November 18th, 2017.