Dayton Power & Light Co: I did a call back and when dpnl called me back...
A Dayton Power & Light Co customer review by GetHuman user ~bb123 from November 10th, 2017
Background on ~bb123's case
GetHuman: ~bb123 - can you tell our other Dayton Power & Light Co customers when your case took place?
~bb123: Sure. It was morning, on November 4th.
GetHuman: Did you reach out to Dayton Power & Light Co, and if so, how?
GetHuman: And which of these common Dayton Power & Light Co customer issues best describes the reason you wanted to talk to them?
(Shows ~bb123 a list of common Dayton Power & Light Co problems)
~bb123: "Lower my bill" was why I was trying to call.
~bb123's review of Dayton Power & Light Co customer service
GetHuman: So how would you sum up your experience for GetHuman's Dayton Power & Light Co 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.
~bb123: I did a call back and when dpnl called me back the person who answered hung up on me. I had to call back blocked and they still are not answering my call.
GetHuman: Let's quantify your experience contacting Dayton Power & Light Co. On a scale of 1 to 5, how easy is it go get help on a Dayton Power & Light Co problem?
~bb123: 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?
~bb123: I'd give them a one out of five on communication.
GetHuman: And what about Dayton Power & Light Co's ability to quickly and effectively address your problem?
~bb123: For that I would say four out of five.
GetHuman: And finally- any advice for other Dayton Power & Light Co customers?
~bb123: Call them early in the day or late. Don't forget any personal or account information you might need for Dayton Power & Light Co to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~bb123 taken from his Dayton Power & Light Co customer service problem that occurred on November 4th, 2017.