National Grid: I was on the phone with a person in less than a...
A National Grid customer review by GetHuman user GetHuman-339866 from November 21st, 2017
Background on GetHuman-339866's case
GetHuman: GetHuman-339866 - can you tell our other National Grid customers when your case took place?
GetHuman-339866: Sure. It was afternoon, on November 19th.
GetHuman: Did you reach out to National Grid, and if so, how?
GetHuman: And which of these common National Grid customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-339866 a list of common National Grid problems)
GetHuman-339866: "Lower my bill" was why I was trying to call.
GetHuman-339866's review of National Grid customer service
GetHuman: So how would you sum up your experience for GetHuman's National Grid 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-339866: I was on the phone with a person in less than a minute and got my question answered... Took a total of * minutes to complete the call from the moment I dialed the number.
GetHuman: Let's quantify your experience contacting National Grid. On a scale of 1 to 5, how easy is it go get help on a National Grid problem?
GetHuman-339866: I'd give them a four 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-339866: I'd give them a three out of five on communication.
GetHuman: And what about National Grid's ability to quickly and effectively address your problem?
GetHuman-339866: For that I would say two out of five.
GetHuman: And finally- any advice for other National Grid customers?
GetHuman-339866: Call them early in the day or late. Don't forget any personal or account information you might need for National Grid to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-339866 taken from his National Grid customer service problem that occurred on November 19th, 2017.