AT&T U-Verse: A load of you know what, I have been on the pho...
A AT&T U-Verse customer review by GetHuman user ~pscott from November 22nd, 2017
Background on ~pscott's case
GetHuman: ~pscott - can you tell our other AT&T U-Verse customers when your case took place?
~pscott: Yeah. It was evening, on November 18th.
GetHuman: Did you reach out to AT&T U-Verse, and if so, how?
GetHuman: And which of these common AT&T U-Verse customer issues best describes the reason you wanted to talk to them?
(Shows ~pscott a list of common AT&T U-Verse problems)
~pscott: "Account access" was why I was trying to call.
~pscott's review of AT&T U-Verse customer service
GetHuman: So how would you sum up your experience for GetHuman's AT&T U-Verse 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.
~pscott: A load of you know what, I have been on the phone for and hour and ** minutes so far and still haven't been able to get my point across. They aren't in the US, keep putting me on hold. They are also charging long distance minutes for non AT&T phone *'s called. They can have their Uverse.
GetHuman: Let's quantify your experience contacting AT&T U-Verse. On a scale of 1 to 5, how easy is it go get help on a AT&T U-Verse problem?
~pscott: I'd give them a one 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?
~pscott: I'd give them a two out of five on communication.
GetHuman: And what about AT&T U-Verse's ability to quickly and effectively address your problem?
~pscott: For that I would say one out of five.
GetHuman: And finally- any advice for other AT&T U-Verse customers?
~pscott: Call them early in the day or late. Don't forget any personal or account information you might need for AT&T U-Verse to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~pscott taken from his AT&T U-Verse customer service problem that occurred on November 18th, 2017.