AT&T Tech Support: Wow! I was on hold w*********** for over one h...
A AT&T Tech Support customer review by GetHuman user ~studman from November 14th, 2017
Background on ~studman's case
GetHuman: ~studman - can you tell our other AT&T Tech Support customers when your case took place?
~studman: Yup. It was evening, on November 12th.
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 ~studman a list of common AT&T Tech Support problems)
~studman: "Refund a Charge" was why I was trying to call.
~studman'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.
~studman: Wow! I was on hold w*********** for over one hour and a half. This number was answered by robot, realperson and then realperson all done within * minutes. She hung up too soon though but I guess thats why its fast.
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?
~studman: 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?
~studman: 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?
~studman: For that I would say two out of five.
GetHuman: And finally- any advice for other AT&T Tech Support customers?
~studman: 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 ~studman taken from his AT&T Tech Support customer service problem that occurred on November 12th, 2017.