AOL put a second bogus account charge on my bil...
A AOL customer review by GetHuman user GetHuman-175679 from November 12th, 2017
Background on GetHuman-175679's case
GetHuman: GetHuman-175679 - can you tell our other AOL customers when your case took place?
GetHuman-175679: Yes. It was middle of the night, on November 10th.
GetHuman: Did you reach out to AOL, and if so, how?
GetHuman: And which of these common AOL customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-175679 a list of common AOL problems)
GetHuman-175679: "Technical support" was why I was trying to call.
GetHuman-175679's review of AOL customer service
GetHuman: So how would you sum up your experience for GetHuman's AOL 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-175679: AOL put a second bogus account charge on my bill. Indian man acknowledged the second account was a hack and I asked AOL to close it. Instead they closed the valid paying account. After being bouncedthrough six individuals, none of which resolved the problem, I closed my assount of ** years* Hello Gmail.
GetHuman: Let's quantify your experience contacting AOL. On a scale of 1 to 5, how easy is it go get help on a AOL problem?
GetHuman-175679: I'd give them a four 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-175679: I'd give them a five out of five on communication.
GetHuman: And what about AOL's ability to quickly and effectively address your problem?
GetHuman-175679: For that I would say four out of five.
GetHuman: And finally- any advice for other AOL customers?
GetHuman-175679: Call them early in the day or late. Don't forget any personal or account information you might need for AOL to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-175679 taken from his AOL customer service problem that occurred on November 10th, 2017.