Dayton Power & Light Co: Worst customer service of any company I've ever...
A Dayton Power & Light Co customer review by GetHuman user ~todd from November 3rd, 2017
Background on ~todd's case
GetHuman: ~todd - can you tell our other Dayton Power & Light Co customers when your case took place?
~todd: Yup. It was late at night, on October 28th.
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 ~todd a list of common Dayton Power & Light Co problems)
~todd: "Meter reading" was why I was trying to call.
~todd'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.
~todd: Worst customer service of any company I've ever dealt with including cable companies. They are always understaffed and most phone reps are just flat rude.
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?
~todd: I'd give them a five 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?
~todd: I'd give them a four out of five on communication.
GetHuman: And what about Dayton Power & Light Co's ability to quickly and effectively address your problem?
~todd: For that I would say one out of five.
GetHuman: And finally- any advice for other Dayton Power & Light Co customers?
~todd: 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 ~todd taken from his Dayton Power & Light Co customer service problem that occurred on October 28th, 2017.