AEP (OH): They don't come out each month and check meters...
A AEP (OH) customer review by GetHuman user GetHuman-112964 from November 13th, 2017
Background on GetHuman-112964's case
GetHuman: GetHuman-112964 - can you tell our other AEP (OH) customers when your case took place?
GetHuman-112964: Yes. It was late at night, on November 4th.
GetHuman: Did you reach out to AEP (OH), and if so, how?
GetHuman: And which of these common AEP (OH) customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-112964 a list of common AEP (OH) problems)
GetHuman-112964: "No service" was why I was trying to call.
GetHuman-112964's review of AEP (OH) customer service
GetHuman: So how would you sum up your experience for GetHuman's AEP (OH) 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-112964: They don't come out each month and check meters. they bill you what they want no matter what this is wrong very wrong I want to pay for what I use not what they guess I use. Lazy company I called and spoke with a lily who was very rude.
GetHuman: Let's quantify your experience contacting AEP (OH). On a scale of 1 to 5, how easy is it go get help on a AEP (OH) problem?
GetHuman-112964: 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-112964: I'd give them a five out of five on communication.
GetHuman: And what about AEP (OH)'s ability to quickly and effectively address your problem?
GetHuman-112964: For that I would say five out of five.
GetHuman: And finally- any advice for other AEP (OH) customers?
GetHuman-112964: Call them early in the day or late. Don't forget any personal or account information you might need for AEP (OH) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-112964 taken from his AEP (OH) customer service problem that occurred on November 4th, 2017.