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