TracFone Wireless: Phone disconnected without reason. Had automati...
A TracFone Wireless customer review by GetHuman user ~ddb from November 26th, 2017
Background on ~ddb's case
GetHuman: ~ddb - can you tell our other TracFone Wireless customers when your case took place?
~ddb: Yup. It was late at night, on November 17th.
GetHuman: Did you reach out to TracFone Wireless, and if so, how?
GetHuman: And which of these common TracFone Wireless customer issues best describes the reason you wanted to talk to them?
(Shows ~ddb a list of common TracFone Wireless problems)
~ddb: "Setup service" was why I was trying to call.
~ddb's review of TracFone Wireless customer service
GetHuman: So how would you sum up your experience for GetHuman's TracFone Wireless 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.
~ddb: Phone disconnected without reason. Had automatic payments. Had to call twice customer service, and was on hold for over * hours. Told both times I was okay and call ****** to reset my phone, and I still don't have service. Switching to a different carrier.
GetHuman: Let's quantify your experience contacting TracFone Wireless. On a scale of 1 to 5, how easy is it go get help on a TracFone Wireless problem?
~ddb: I'd give them a four 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?
~ddb: I'd give them a three out of five on communication.
GetHuman: And what about TracFone Wireless's ability to quickly and effectively address your problem?
~ddb: For that I would say five out of five.
GetHuman: And finally- any advice for other TracFone Wireless customers?
~ddb: Call them early in the day or late. Don't forget any personal or account information you might need for TracFone Wireless to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~ddb taken from his TracFone Wireless customer service problem that occurred on November 17th, 2017.