AT&T - California: ATT is absolutely the WORSE company to have to...
A AT&T - California customer review by GetHuman user ~Anonymous from November 10th, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other AT&T - California customers when your case took place?
~Anonymous: Yes. It was afternoon, on November 5th.
GetHuman: Did you reach out to AT&T - California, and if so, how?
GetHuman: And which of these common AT&T - California customer issues best describes the reason you wanted to talk to them?
(Shows ~Anonymous a list of common AT&T - California problems)
~Anonymous: "Setup service" was why I was trying to call.
~Anonymous's review of AT&T - California customer service
GetHuman: So how would you sum up your experience for GetHuman's AT&T - California 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.
~Anonymous: ATT is absolutely the WORSE company to have to deal with. This one phone call was great, which I think had the same odds as winning the lottery. It'll never happen again, I'm sure.
GetHuman: Let's quantify your experience contacting AT&T - California. On a scale of 1 to 5, how easy is it go get help on a AT&T - California problem?
~Anonymous: 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?
~Anonymous: I'd give them a four out of five on communication.
GetHuman: And what about AT&T - California's ability to quickly and effectively address your problem?
~Anonymous: For that I would say one out of five.
GetHuman: And finally- any advice for other AT&T - California customers?
~Anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for AT&T - California to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his AT&T - California customer service problem that occurred on November 5th, 2017.