AT&T U-Verse: Try this trick: Press * (cancellation option) t...
A AT&T U-Verse customer review by GetHuman user ~George from November 25th, 2017
Background on ~George's case
GetHuman: ~George - can you tell our other AT&T U-Verse customers when your case took place?
~George: Sure. It was afternoon, on November 17th.
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 ~George a list of common AT&T U-Verse problems)
~George: "Refund" was why I was trying to call.
~George'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.
~George: Try this trick: Press * (cancellation option) to be transferred to the retention department.Reached call center in cleveland, OH right away and Sharron was very nice and helpful. Got my issue taken care of (returned equipment was not showing as returned). They will try to upsell you though.
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?
~George: 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?
~George: 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?
~George: For that I would say three out of five.
GetHuman: And finally- any advice for other AT&T U-Verse customers?
~George: 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 ~George taken from his AT&T U-Verse customer service problem that occurred on November 17th, 2017.