TXU Energy: This is the worst Electric company in Texas. Th...
A TXU Energy customer review by GetHuman user GetHuman-207501 from October 31st, 2017
Background on GetHuman-207501's case
GetHuman: GetHuman-207501 - can you tell our other TXU Energy customers when your case took place?
GetHuman-207501: Sure. It was afternoon, on October 25th.
GetHuman: Did you reach out to TXU Energy, and if so, how?
GetHuman: And which of these common TXU Energy customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-207501 a list of common TXU Energy problems)
GetHuman-207501: "Overcharges on My Account" was why I was trying to call.
GetHuman-207501's review of TXU Energy customer service
GetHuman: So how would you sum up your experience for GetHuman's TXU Energy 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-207501: This is the worst Electric company in Texas. They lost my payment and could not find it. I gave them the info and called my bank. There billing dept. *****!!!!!*They should have a better system!!!!
GetHuman: Let's quantify your experience contacting TXU Energy. On a scale of 1 to 5, how easy is it go get help on a TXU Energy problem?
GetHuman-207501: 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?
GetHuman-207501: I'd give them a three out of five on communication.
GetHuman: And what about TXU Energy's ability to quickly and effectively address your problem?
GetHuman-207501: For that I would say four out of five.
GetHuman: And finally- any advice for other TXU Energy customers?
GetHuman-207501: Call them early in the day or late. Don't forget any personal or account information you might need for TXU Energy to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-207501 taken from his TXU Energy customer service problem that occurred on October 25th, 2017.