AT&T Tech Support: These people sucked. This is supposed to be tec...
A AT&T Tech Support customer review by GetHuman user GetHuman-379148 from November 27th, 2017
Background on GetHuman-379148's case
GetHuman: GetHuman-379148 - can you tell our other AT&T Tech Support customers when your case took place?
GetHuman-379148: Yup. It was morning, on November 23rd.
GetHuman: Did you reach out to AT&T Tech Support, and if so, how?
GetHuman: And which of these common AT&T Tech Support customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-379148 a list of common AT&T Tech Support problems)
GetHuman-379148: "Refund a Charge" was why I was trying to call.
GetHuman-379148's review of AT&T Tech Support customer service
GetHuman: So how would you sum up your experience for GetHuman's AT&T Tech Support 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-379148: These people sucked. This is supposed to be tech support, and all they would do is tell me to call someone else.
GetHuman: Let's quantify your experience contacting AT&T Tech Support. On a scale of 1 to 5, how easy is it go get help on a AT&T Tech Support problem?
GetHuman-379148: 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-379148: I'd give them a one out of five on communication.
GetHuman: And what about AT&T Tech Support's ability to quickly and effectively address your problem?
GetHuman-379148: For that I would say four out of five.
GetHuman: And finally- any advice for other AT&T Tech Support customers?
GetHuman-379148: Call them early in the day or late. Don't forget any personal or account information you might need for AT&T Tech Support to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-379148 taken from his AT&T Tech Support customer service problem that occurred on November 23rd, 2017.