TracFone Wireless: I was very surprised that a live U.S. based per...
A TracFone Wireless customer review by GetHuman user ~Daedo Larkin from November 19th, 2017
Background on ~Daedo Larkin's case
GetHuman: ~Daedo Larkin - can you tell our other TracFone Wireless customers when your case took place?
~Daedo Larkin: Yes. It was afternoon, on November 12th.
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 ~Daedo Larkin a list of common TracFone Wireless problems)
~Daedo Larkin: "Complaint" was why I was trying to call.
~Daedo Larkin'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.
~Daedo Larkin: I was very surprised that a live U.S. based person answered on the first ring to help me with a Samsung S*** "Blocking Defence" error code issue
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?
~Daedo Larkin: 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?
~Daedo Larkin: I'd give them a four out of five on communication.
GetHuman: And what about TracFone Wireless's ability to quickly and effectively address your problem?
~Daedo Larkin: For that I would say three out of five.
GetHuman: And finally- any advice for other TracFone Wireless customers?
~Daedo Larkin: 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 ~Daedo Larkin taken from his TracFone Wireless customer service problem that occurred on November 12th, 2017.