AT&T: Pretty much getting ripped off. I had to send a...
A AT&T customer review by GetHuman user ~David Miranda from November 27th, 2017
Background on ~David Miranda's case
GetHuman: ~David Miranda - can you tell our other AT&T customers when your case took place?
~David Miranda: Yes. It was middle of the night, on November 19th.
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 ~David Miranda a list of common AT&T problems)
~David Miranda: "Refund" was why I was trying to call.
~David Miranda'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.
~David Miranda: Pretty much getting ripped off. I had to send a phone back they said it was broken. I had no proof it wasnt so now I have to pay $*** so going to new company. Would never recommend at&t to anyone. Manager pretty much said there was nothing they can do and dont care if I go to a new company. So new company it is.
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?
~David Miranda: 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?
~David Miranda: 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?
~David Miranda: For that I would say one out of five.
GetHuman: And finally- any advice for other AT&T customers?
~David Miranda: 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 ~David Miranda taken from his AT&T customer service problem that occurred on November 19th, 2017.