TracFone Wireless: language barrier did not understand me. had m...
A TracFone Wireless customer review by GetHuman user ~sofrustrated from November 24th, 2017
Background on ~sofrustrated's case
GetHuman: ~sofrustrated - can you tell our other TracFone Wireless customers when your case took place?
~sofrustrated: 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 ~sofrustrated a list of common TracFone Wireless problems)
~sofrustrated: "Technical support" was why I was trying to call.
~sofrustrated'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.
~sofrustrated: language barrier did not understand me. had me start over multiple times . did not know what i was asking agent disconnected
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?
~sofrustrated: 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?
~sofrustrated: I'd give them a five out of five on communication.
GetHuman: And what about TracFone Wireless's ability to quickly and effectively address your problem?
~sofrustrated: For that I would say two out of five.
GetHuman: And finally- any advice for other TracFone Wireless customers?
~sofrustrated: 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 ~sofrustrated taken from his TracFone Wireless customer service problem that occurred on November 14th, 2017.