AT&T Go Phone: I FINALLY GOT THE TECH SUPPORT I NEEDED! LOUIE...
A AT&T Go Phone customer review by GetHuman user ~JOANNE from November 18th, 2017
Background on ~JOANNE's case
GetHuman: ~JOANNE - can you tell our other AT&T Go Phone customers when your case took place?
~JOANNE: Yup. It was evening, on November 14th.
GetHuman: Did you reach out to AT&T Go Phone, and if so, how?
GetHuman: And which of these common AT&T Go Phone customer issues best describes the reason you wanted to talk to them?
(Shows ~JOANNE a list of common AT&T Go Phone problems)
~JOANNE: "Complaint" was why I was trying to call.
~JOANNE's review of AT&T Go Phone customer service
GetHuman: So how would you sum up your experience for GetHuman's AT&T Go Phone 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.
~JOANNE: I FINALLY GOT THE TECH SUPPORT I NEEDED! LOUIE * LP***B WAS EXCELLENT, HELPED ME WITH MY * GO PHONE ACCOUNTS...SET ME UP ON AUTO REFILL, WHICH PREVIOUSLY I HAVE BEEN TOLD COULD NOT BE DONE!! VERY, VERY HELPFUL, POLITE, KNOWLEDGEABLE!! THANK YOU AGAIN, LOUIE,,,YOU ARE THE BEST!
GetHuman: Let's quantify your experience contacting AT&T Go Phone. On a scale of 1 to 5, how easy is it go get help on a AT&T Go Phone problem?
~JOANNE: 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?
~JOANNE: I'd give them a five out of five on communication.
GetHuman: And what about AT&T Go Phone's ability to quickly and effectively address your problem?
~JOANNE: For that I would say five out of five.
GetHuman: And finally- any advice for other AT&T Go Phone customers?
~JOANNE: Call them early in the day or late. Don't forget any personal or account information you might need for AT&T Go Phone to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~JOANNE taken from his AT&T Go Phone customer service problem that occurred on November 14th, 2017.