Huffington Post: I finally got tired of the phone ringing, no on...
A Huffington Post customer review by GetHuman user ~napawastae from November 6th, 2017
Background on ~napawastae's case
GetHuman: ~napawastae - can you tell our other Huffington Post customers when your case took place?
~napawastae: Yes I can. It was morning, on November 4th.
GetHuman: Did you reach out to Huffington Post, and if so, how?
GetHuman: And which of these common Huffington Post customer issues best describes the reason you wanted to talk to them?
(Shows ~napawastae a list of common Huffington Post problems)
~napawastae: "Delivery problem" was why I was trying to contact.
~napawastae's review of Huffington Post customer service
GetHuman: So how would you sum up your experience for GetHuman's Huffington Post 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.
~napawastae: I finally got tired of the phone ringing, no one answered. I used to love reading the huffington post on aol. I am thinking of getting rid of AOL just to get rid of Huffington Post.
GetHuman: Let's quantify your experience contacting Huffington Post. On a scale of 1 to 5, how easy is it go get help on a Huffington Post problem?
~napawastae: 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?
~napawastae: I'd give them a one out of five on communication.
GetHuman: And what about Huffington Post's ability to quickly and effectively address your problem?
~napawastae: For that I would say one out of five.
GetHuman: And finally- any advice for other Huffington Post customers?
~napawastae: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Huffington Post to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~napawastae taken from his Huffington Post customer service problem that occurred on November 4th, 2017.