Tampa Electric: Had to wait forever. Your webpage doesn't prov...
A Tampa Electric customer review by GetHuman user GetHuman-226916 from November 25th, 2017
Background on GetHuman-226916's case
GetHuman: GetHuman-226916 - can you tell our other Tampa Electric customers when your case took place?
GetHuman-226916: Sure. It was morning, on November 17th.
GetHuman: Did you reach out to Tampa Electric, and if so, how?
GetHuman: And which of these common Tampa Electric customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-226916 a list of common Tampa Electric problems)
GetHuman-226916: "Lower my bill" was why I was trying to call.
GetHuman-226916's review of Tampa Electric customer service
GetHuman: So how would you sum up your experience for GetHuman's Tampa Electric 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-226916: Had to wait forever. Your webpage doesn't provide a phone number. If there's another company that provides electric I will drop you people immediately!!!
GetHuman: Let's quantify your experience contacting Tampa Electric. On a scale of 1 to 5, how easy is it go get help on a Tampa Electric problem?
GetHuman-226916: 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-226916: I'd give them a five out of five on communication.
GetHuman: And what about Tampa Electric's ability to quickly and effectively address your problem?
GetHuman-226916: For that I would say three out of five.
GetHuman: And finally- any advice for other Tampa Electric customers?
GetHuman-226916: Call them early in the day or late. Don't forget any personal or account information you might need for Tampa Electric to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-226916 taken from his Tampa Electric customer service problem that occurred on November 17th, 2017.