eHow.com: The only human I was connected to called hersel...
A eHow.com customer review by GetHuman user GetHuman-333420 from November 19th, 2017
Background on GetHuman-333420's case
GetHuman: GetHuman-333420 - can you tell our other eHow.com customers when your case took place?
GetHuman-333420: Yes I can. It was morning, on November 16th.
GetHuman: Did you reach out to eHow.com, and if so, how?
GetHuman: And which of these common eHow.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-333420 a list of common eHow.com problems)
GetHuman-333420: "Technical support" was why I was trying to contact.
GetHuman-333420's review of eHow.com customer service
GetHuman: So how would you sum up your experience for GetHuman's eHow.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.
GetHuman-333420: The only human I was connected to called herself a receptionist that gave me a bogus email addres and connected me to "Brian" who was automated got me to no other person and finally hung up on me. Your help *****.
GetHuman: Let's quantify your experience contacting eHow.com. On a scale of 1 to 5, how easy is it go get help on a eHow.com problem?
GetHuman-333420: 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-333420: I'd give them a three out of five on communication.
GetHuman: And what about eHow.com's ability to quickly and effectively address your problem?
GetHuman-333420: For that I would say two out of five.
GetHuman: And finally- any advice for other eHow.com customers?
GetHuman-333420: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for eHow.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-333420 taken from his eHow.com customer service problem that occurred on November 16th, 2017.