AT&T Wireless: English obvious not his *st language & I had to...
A AT&T Wireless customer review by GetHuman user GetHuman-52205 from November 16th, 2017
Background on GetHuman-52205's case
GetHuman: GetHuman-52205 - can you tell our other AT&T Wireless customers when your case took place?
GetHuman-52205: Yes I can. It was morning, on November 9th.
GetHuman: Did you reach out to AT&T Wireless, and if so, how?
GetHuman: And which of these common AT&T Wireless customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-52205 a list of common AT&T Wireless problems)
GetHuman-52205: "Service or technical issue" was why I was trying to call.
GetHuman-52205's review of AT&T Wireless customer service
GetHuman: So how would you sum up your experience for GetHuman's AT&T 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.
GetHuman-52205: English obvious not his *st language & I had to ask for a few things to be repeated. They disconneced us because AT&T did not use automatic deduction for *st time.
GetHuman: Let's quantify your experience contacting AT&T Wireless. On a scale of 1 to 5, how easy is it go get help on a AT&T Wireless problem?
GetHuman-52205: 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?
GetHuman-52205: I'd give them a five out of five on communication.
GetHuman: And what about AT&T Wireless's ability to quickly and effectively address your problem?
GetHuman-52205: For that I would say two out of five.
GetHuman: And finally- any advice for other AT&T Wireless customers?
GetHuman-52205: Call them early in the day or late. Don't forget any personal or account information you might need for AT&T Wireless to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-52205 taken from his AT&T Wireless customer service problem that occurred on November 9th, 2017.