Oncor: After more than * yr. of trying to get their po...
A Oncor customer review by GetHuman user ~Susan in Texas from November 13th, 2017
Background on ~Susan in Texas's case
GetHuman: ~Susan in Texas - can you tell our other Oncor customers when your case took place?
~Susan in Texas: Yes I can. It was middle of the night, on November 9th.
GetHuman: Did you reach out to Oncor, and if so, how?
GetHuman: And which of these common Oncor customer issues best describes the reason you wanted to talk to them?
(Shows ~Susan in Texas a list of common Oncor problems)
~Susan in Texas: "Change appointment" was why I was trying to call.
~Susan in Texas's review of Oncor customer service
GetHuman: So how would you sum up your experience for GetHuman's Oncor 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.
~Susan in Texas: After more than * yr. of trying to get their pole moved OUT OF MY DRIVEWAY, I called this number, and within a total of * min from answering phone, they gave me a work order number and said they will contact me with time and detaiuls within * business days! WOW!!!
GetHuman: Let's quantify your experience contacting Oncor. On a scale of 1 to 5, how easy is it go get help on a Oncor problem?
~Susan in Texas: I'd give them a five 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?
~Susan in Texas: I'd give them a four out of five on communication.
GetHuman: And what about Oncor's ability to quickly and effectively address your problem?
~Susan in Texas: For that I would say three out of five.
GetHuman: And finally- any advice for other Oncor customers?
~Susan in Texas: Call them early in the day or late. Don't forget any personal or account information you might need for Oncor to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Susan in Texas taken from his Oncor customer service problem that occurred on November 9th, 2017.