Huffington Post: No answers no contact ...nothing..bye bye huff...
A Huffington Post customer review by GetHuman user GetHuman-372919 from November 26th, 2017
Background on GetHuman-372919's case
GetHuman: GetHuman-372919 - can you tell our other Huffington Post customers when your case took place?
GetHuman-372919: Yes. It was evening, on November 19th.
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 GetHuman-372919 a list of common Huffington Post problems)
GetHuman-372919: "Delivery problem" was why I was trying to contact.
GetHuman-372919'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.
GetHuman-372919: No answers no contact ...nothing..bye bye huff post,you were my go to news source until you tried to make me use Facebook...bye bye!
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?
GetHuman-372919: 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?
GetHuman-372919: I'd give them a four out of five on communication.
GetHuman: And what about Huffington Post's ability to quickly and effectively address your problem?
GetHuman-372919: For that I would say one out of five.
GetHuman: And finally- any advice for other Huffington Post customers?
GetHuman-372919: 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 GetHuman-372919 taken from his Huffington Post customer service problem that occurred on November 19th, 2017.