AT&T: was to get installation today, no one showed up...
A AT&T customer review by GetHuman user ~Dana W from November 22nd, 2017
Background on ~Dana W's case
GetHuman: ~Dana W - can you tell our other AT&T customers when your case took place?
~Dana W: Yup. It was middle of the night, on November 14th.
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 ~Dana W a list of common AT&T problems)
~Dana W: "Overcharge/Strange charge" was why I was trying to call.
~Dana W'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.
~Dana W: was to get installation today, no one showed up, was told someone put phone * in wrong, then was told next available date was * weeks from now, when I said that was unacceptable, I was transferred (for the *TH time!!!)& told there was a problem with AT&T equipment outside my home & they had no idea when it would be fixed & would not reschedule installation at this time!!!
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?
~Dana W: 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?
~Dana W: I'd give them a three out of five on communication.
GetHuman: And what about AT&T's ability to quickly and effectively address your problem?
~Dana W: For that I would say four out of five.
GetHuman: And finally- any advice for other AT&T customers?
~Dana W: 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 ~Dana W taken from his AT&T customer service problem that occurred on November 14th, 2017.