AOL: I attempted to connect via chat and was success...
A AOL customer review by GetHuman user ~LONGLAYD from November 24th, 2017
Background on ~LONGLAYD's case
GetHuman: ~LONGLAYD - can you tell our other AOL customers when your case took place?
~LONGLAYD: Yes I can. It was afternoon, on November 22nd.
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 ~LONGLAYD a list of common AOL problems)
~LONGLAYD: "Service problem" was why I was trying to call.
~LONGLAYD'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.
~LONGLAYD: I attempted to connect via chat and was successful this time. But the person asked me for my security question which I found Suspicious, taking minutes and minutes to "pull up my account" even though my questions were general security questions and not account specific. I ended the chat. They want to send me an email when my very question was about official AOL emails and they would not even answer. Ridiculous
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?
~LONGLAYD: I'd give them a two 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?
~LONGLAYD: I'd give them a one out of five on communication.
GetHuman: And what about AOL's ability to quickly and effectively address your problem?
~LONGLAYD: For that I would say four out of five.
GetHuman: And finally- any advice for other AOL customers?
~LONGLAYD: 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 ~LONGLAYD taken from his AOL customer service problem that occurred on November 22nd, 2017.