Dominion East Ohio: I was able to wait for a callback (option) and...
A Dominion East Ohio customer review by GetHuman user ~crandall from November 26th, 2017
Background on ~crandall's case
GetHuman: ~crandall - can you tell our other Dominion East Ohio customers when your case took place?
~crandall: Yes. It was morning, on November 22nd.
GetHuman: Did you reach out to Dominion East Ohio, and if so, how?
GetHuman: And which of these common Dominion East Ohio customer issues best describes the reason you wanted to talk to them?
(Shows ~crandall a list of common Dominion East Ohio problems)
~crandall: "Setup service" was why I was trying to call.
~crandall's review of Dominion East Ohio customer service
GetHuman: So how would you sum up your experience for GetHuman's Dominion East Ohio 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.
~crandall: I was able to wait for a callback (option) and not miss my place in the order of calls, waited less than ** minutes, the tech was able to handle all the changeover billing.
GetHuman: Let's quantify your experience contacting Dominion East Ohio. On a scale of 1 to 5, how easy is it go get help on a Dominion East Ohio problem?
~crandall: 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?
~crandall: I'd give them a three out of five on communication.
GetHuman: And what about Dominion East Ohio's ability to quickly and effectively address your problem?
~crandall: For that I would say two out of five.
GetHuman: And finally- any advice for other Dominion East Ohio customers?
~crandall: Call them early in the day or late. Don't forget any personal or account information you might need for Dominion East Ohio to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~crandall taken from his Dominion East Ohio customer service problem that occurred on November 22nd, 2017.