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