AT&T U-Verse: Although he kept calling me "ma'am" - I'm a "s...
A AT&T U-Verse customer review by GetHuman user GetHuman-245719 from November 19th, 2017
Background on GetHuman-245719's case
GetHuman: GetHuman-245719 - can you tell our other AT&T U-Verse customers when your case took place?
GetHuman-245719: Yes. It was evening, on November 11th.
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 GetHuman-245719 a list of common AT&T U-Verse problems)
GetHuman-245719: "Account Access" was why I was trying to call.
GetHuman-245719'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.
GetHuman-245719: Although he kept calling me "ma'am" - I'm a "sir" he asked how he could help. I needed tech support so he gave me a number and transferred me. I got a human right away with that number as well.
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?
GetHuman-245719: 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-245719: I'd give them a one out of five on communication.
GetHuman: And what about AT&T U-Verse's ability to quickly and effectively address your problem?
GetHuman-245719: For that I would say two out of five.
GetHuman: And finally- any advice for other AT&T U-Verse customers?
GetHuman-245719: 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 GetHuman-245719 taken from his AT&T U-Verse customer service problem that occurred on November 11th, 2017.