TXU Energy: On top of that I owed $**.** called and made ar...
A TXU Energy customer review by GetHuman user GetHuman-417322 from November 2nd, 2017
Background on GetHuman-417322's case
GetHuman: GetHuman-417322 - can you tell our other TXU Energy customers when your case took place?
GetHuman-417322: Yeah. It was evening, on October 24th.
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-417322 a list of common TXU Energy problems)
GetHuman-417322: "Meter Reading" was why I was trying to call.
GetHuman-417322'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-417322: On top of that I owed $**.** called and made arrangements and was still disconnected. Then recieved a bill saying I owe $***.**. This is ridiculous somepne needs to step up to the plate because customer service *****.
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-417322: I'd give them a three 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-417322: I'd give them a four out of five on communication.
GetHuman: And what about TXU Energy's ability to quickly and effectively address your problem?
GetHuman-417322: For that I would say five out of five.
GetHuman: And finally- any advice for other TXU Energy customers?
GetHuman-417322: 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-417322 taken from his TXU Energy customer service problem that occurred on October 24th, 2017.