TracFone Wireless: person not sue what he was doing,, kept asking...
A TracFone Wireless customer review by GetHuman user ~jim dodson from November 18th, 2017
Background on ~jim dodson's case
GetHuman: ~jim dodson - can you tell our other TracFone Wireless customers when your case took place?
~jim dodson: Yup. It was afternoon, on November 9th.
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 ~jim dodson a list of common TracFone Wireless problems)
~jim dodson: "Device Support" was why I was trying to call.
~jim dodson'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.
~jim dodson: person not sue what he was doing,, kept asking for repeat information, five times, finally just gave up..only wanted to update phone******** for one year at *oo 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?
~jim dodson: 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?
~jim dodson: 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?
~jim dodson: For that I would say one out of five.
GetHuman: And finally- any advice for other TracFone Wireless customers?
~jim dodson: 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 ~jim dodson taken from his TracFone Wireless customer service problem that occurred on November 9th, 2017.