Yahoo: I have not been able to get my mail in at least...
A Yahoo customer review by GetHuman user GetHuman-104029 from November 23rd, 2017
Background on GetHuman-104029's case
GetHuman: GetHuman-104029 - can you tell our other Yahoo customers when your case took place?
GetHuman-104029: Yes. It was afternoon, on November 20th.
GetHuman: Did you reach out to Yahoo, and if so, how?
GetHuman: And which of these common Yahoo customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-104029 a list of common Yahoo problems)
GetHuman-104029: "Account hacked" was why I was trying to contact.
GetHuman-104029's review of Yahoo customer service
GetHuman: So how would you sum up your experience for GetHuman's Yahoo 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-104029: I have not been able to get my mail in at least one month. Seems as if I am not the only one to be having that problem. Yahoo doesn't care about the person getting their email. This is causing a ton of problems. I don't have two hours to wait and then not getting anyone.
GetHuman: Let's quantify your experience contacting Yahoo. On a scale of 1 to 5, how easy is it go get help on a Yahoo problem?
GetHuman-104029: 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-104029: I'd give them a two out of five on communication.
GetHuman: And what about Yahoo's ability to quickly and effectively address your problem?
GetHuman-104029: For that I would say one out of five.
GetHuman: And finally- any advice for other Yahoo customers?
GetHuman-104029: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Yahoo to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-104029 taken from his Yahoo customer service problem that occurred on November 20th, 2017.