Duquesne Light Co: The customer service provider was super nice an...
A Duquesne Light Co customer review by GetHuman user GetHuman-110075 from November 24th, 2017
Background on GetHuman-110075's case
GetHuman: GetHuman-110075 - can you tell our other Duquesne Light Co customers when your case took place?
GetHuman-110075: Yes I can. It was morning, on November 14th.
GetHuman: Did you reach out to Duquesne Light Co, and if so, how?
GetHuman: And which of these common Duquesne Light Co customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-110075 a list of common Duquesne Light Co problems)
GetHuman-110075: "Complaint" was why I was trying to call.
GetHuman-110075's review of Duquesne Light Co customer service
GetHuman: So how would you sum up your experience for GetHuman's Duquesne 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.
GetHuman-110075: The customer service provider was super nice and made it painless to get a new statement of an incorrect bill!
GetHuman: Let's quantify your experience contacting Duquesne Light Co. On a scale of 1 to 5, how easy is it go get help on a Duquesne Light Co problem?
GetHuman-110075: I'd give them a three 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-110075: I'd give them a four out of five on communication.
GetHuman: And what about Duquesne Light Co's ability to quickly and effectively address your problem?
GetHuman-110075: For that I would say one out of five.
GetHuman: And finally- any advice for other Duquesne Light Co customers?
GetHuman-110075: Call them early in the day or late. Don't forget any personal or account information you might need for Duquesne Light Co to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-110075 taken from his Duquesne Light Co customer service problem that occurred on November 14th, 2017.