AT&T Go Phone: Once I found all the necessary numbers, the aut...
A AT&T Go Phone customer review by GetHuman user GetHuman-405458 from November 28th, 2017
Background on GetHuman-405458's case
GetHuman: GetHuman-405458 - can you tell our other AT&T Go Phone customers when your case took place?
GetHuman-405458: Yup. It was morning, on November 21st.
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 GetHuman-405458 a list of common AT&T Go Phone problems)
GetHuman-405458: "Complaint" was why I was trying to call.
GetHuman-405458'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.
GetHuman-405458: Once I found all the necessary numbers, the automated system connected me with a human very quickly - about ** sec. or less. She was able to resolve my problems.
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?
GetHuman-405458: 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?
GetHuman-405458: I'd give them a one out of five on communication.
GetHuman: And what about AT&T Go Phone's ability to quickly and effectively address your problem?
GetHuman-405458: For that I would say two out of five.
GetHuman: And finally- any advice for other AT&T Go Phone customers?
GetHuman-405458: 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 GetHuman-405458 taken from his AT&T Go Phone customer service problem that occurred on November 21st, 2017.