Con Edison: Sure, they actually do call you back as promise...
A Con Edison customer review by GetHuman user GetHuman-320822 from November 11th, 2017
Background on GetHuman-320822's case
GetHuman: GetHuman-320822 - can you tell our other Con Edison customers when your case took place?
GetHuman-320822: Yeah. It was morning, on November 2nd.
GetHuman: Did you reach out to Con Edison, and if so, how?
GetHuman: And which of these common Con Edison customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-320822 a list of common Con Edison problems)
GetHuman-320822: "Overcharge on Account" was why I was trying to call.
GetHuman-320822's review of Con Edison customer service
GetHuman: So how would you sum up your experience for GetHuman's Con Edison 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-320822: Sure, they actually do call you back as promised EXCEPT no one is on the line when I answered and then it disconnects. Tried this several times few weeks ago and then again this week...gave up!
GetHuman: Let's quantify your experience contacting Con Edison. On a scale of 1 to 5, how easy is it go get help on a Con Edison problem?
GetHuman-320822: 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-320822: I'd give them a four out of five on communication.
GetHuman: And what about Con Edison's ability to quickly and effectively address your problem?
GetHuman-320822: For that I would say three out of five.
GetHuman: And finally- any advice for other Con Edison customers?
GetHuman-320822: Call them early in the day or late. Don't forget any personal or account information you might need for Con Edison to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-320822 taken from his Con Edison customer service problem that occurred on November 2nd, 2017.