AT&T: I waited for less than * minute and talked with...
A AT&T customer review by GetHuman user GetHuman-133919 from November 16th, 2017
Background on GetHuman-133919's case
GetHuman: GetHuman-133919 - can you tell our other AT&T customers when your case took place?
GetHuman-133919: Yes. It was late at night, on November 7th.
GetHuman: Did you reach out to AT&T, and if so, how?
GetHuman: And which of these common AT&T customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-133919 a list of common AT&T problems)
GetHuman-133919: "Device Support" was why I was trying to call.
GetHuman-133919's review of AT&T customer service
GetHuman: So how would you sum up your experience for GetHuman's AT&T 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-133919: I waited for less than * minute and talked with a real US person! This * is for DSL*landline customers, exactly what I needed. She found out for me that there is an area wide problem with my message service, not just me, and that it is being worked on right now. Thanks for this contact number!
GetHuman: Let's quantify your experience contacting AT&T. On a scale of 1 to 5, how easy is it go get help on a AT&T problem?
GetHuman-133919: 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?
GetHuman-133919: I'd give them a five out of five on communication.
GetHuman: And what about AT&T's ability to quickly and effectively address your problem?
GetHuman-133919: For that I would say four out of five.
GetHuman: And finally- any advice for other AT&T customers?
GetHuman-133919: Call them early in the day or late. Don't forget any personal or account information you might need for AT&T to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-133919 taken from his AT&T customer service problem that occurred on November 7th, 2017.