AT&T Wireless: Multiple calls... multiple agents. still no re...
A AT&T Wireless customer review by GetHuman user GetHuman-101689 from November 18th, 2017
Background on GetHuman-101689's case
GetHuman: GetHuman-101689 - can you tell our other AT&T Wireless customers when your case took place?
GetHuman-101689: Yes. It was evening, on November 13th.
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-101689 a list of common AT&T Wireless problems)
GetHuman-101689: "Change plan" was why I was trying to call.
GetHuman-101689'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-101689: Multiple calls... multiple agents. still no resolution to problem. Managers over a week late calling back. Call got dropped by network during the call. Manager did not call back
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-101689: 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-101689: I'd give them a three out of five on communication.
GetHuman: And what about AT&T Wireless's ability to quickly and effectively address your problem?
GetHuman-101689: For that I would say five out of five.
GetHuman: And finally- any advice for other AT&T Wireless customers?
GetHuman-101689: 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-101689 taken from his AT&T Wireless customer service problem that occurred on November 13th, 2017.