TracFone Wireless: Great response and quick service. Phone locked...
A TracFone Wireless customer review by GetHuman user ~Matthew Hodge from November 19th, 2017
Background on ~Matthew Hodge's case
GetHuman: ~Matthew Hodge - can you tell our other TracFone Wireless customers when your case took place?
~Matthew Hodge: Yeah. It was afternoon, on November 14th.
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 ~Matthew Hodge a list of common TracFone Wireless problems)
~Matthew Hodge: "Account access" was why I was trying to call.
~Matthew Hodge'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.
~Matthew Hodge: Great response and quick service. Phone locked up with a prompt to enter a PUK Code. Quickly fixed the issue within five minutes.
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?
~Matthew Hodge: 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?
~Matthew Hodge: 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?
~Matthew Hodge: For that I would say two out of five.
GetHuman: And finally- any advice for other TracFone Wireless customers?
~Matthew Hodge: 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 ~Matthew Hodge taken from his TracFone Wireless customer service problem that occurred on November 14th, 2017.