Duke Energy (NC & SC): Brilliant way to get around the awful phone tre...
A Duke Energy (NC & SC) customer review by GetHuman user ~anonymous from November 21st, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other Duke Energy (NC & SC) customers when your case took place?
~anonymous: Yeah. It was morning, on November 18th.
GetHuman: Did you reach out to Duke Energy (NC & SC), and if so, how?
GetHuman: And which of these common Duke Energy (NC & SC) customer issues best describes the reason you wanted to talk to them?
(Shows ~anonymous a list of common Duke Energy (NC & SC) problems)
~anonymous: "Book appointment" was why I was trying to call.
~anonymous's review of Duke Energy (NC & SC) customer service
GetHuman: So how would you sum up your experience for GetHuman's Duke Energy (NC & SC) 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.
~anonymous: Brilliant way to get around the awful phone tree. I was immediately connected to a customer service rep.
GetHuman: Let's quantify your experience contacting Duke Energy (NC & SC). On a scale of 1 to 5, how easy is it go get help on a Duke Energy (NC & SC) problem?
~anonymous: 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?
~anonymous: I'd give them a five out of five on communication.
GetHuman: And what about Duke Energy (NC & SC)'s ability to quickly and effectively address your problem?
~anonymous: For that I would say three out of five.
GetHuman: And finally- any advice for other Duke Energy (NC & SC) customers?
~anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Duke Energy (NC & SC) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his Duke Energy (NC & SC) customer service problem that occurred on November 18th, 2017.