Duke Energy (IN): No Need to press any thing the computer automat...
A Duke Energy (IN) customer review by GetHuman user ~edwardsirrigation from November 9th, 2017
Background on ~edwardsirrigation's case
GetHuman: ~edwardsirrigation - can you tell our other Duke Energy (IN) customers when your case took place?
~edwardsirrigation: Yup. It was evening, on November 7th.
GetHuman: Did you reach out to Duke Energy (IN), and if so, how?
GetHuman: And which of these common Duke Energy (IN) customer issues best describes the reason you wanted to talk to them?
(Shows ~edwardsirrigation a list of common Duke Energy (IN) problems)
~edwardsirrigation: "Meter Reading" was why I was trying to call.
~edwardsirrigation's review of Duke Energy (IN) customer service
GetHuman: So how would you sum up your experience for GetHuman's Duke Energy (IN) 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.
~edwardsirrigation: No Need to press any thing the computer automatic sends the call to customer service. Love get human
GetHuman: Let's quantify your experience contacting Duke Energy (IN). On a scale of 1 to 5, how easy is it go get help on a Duke Energy (IN) problem?
~edwardsirrigation: I'd give them a two 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?
~edwardsirrigation: I'd give them a one out of five on communication.
GetHuman: And what about Duke Energy (IN)'s ability to quickly and effectively address your problem?
~edwardsirrigation: For that I would say one out of five.
GetHuman: And finally- any advice for other Duke Energy (IN) customers?
~edwardsirrigation: Call them early in the day or late. Don't forget any personal or account information you might need for Duke Energy (IN) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~edwardsirrigation taken from his Duke Energy (IN) customer service problem that occurred on November 7th, 2017.