AT&T Universal Card: I was no asked for a phone number so that they...
A AT&T Universal Card customer review by GetHuman user GetHuman-276937 from November 22nd, 2017
Background on GetHuman-276937's case
GetHuman: GetHuman-276937 - can you tell our other AT&T Universal Card customers when your case took place?
GetHuman-276937: Yeah. It was middle of the night, on November 21st.
GetHuman: Did you reach out to AT&T Universal Card, and if so, how?
GetHuman: And which of these common AT&T Universal Card customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-276937 a list of common AT&T Universal Card problems)
GetHuman-276937: "Update account information" was why I was trying to call.
GetHuman-276937's review of AT&T Universal Card customer service
GetHuman: So how would you sum up your experience for GetHuman's AT&T Universal Card 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-276937: I was no asked for a phone number so that they could call me.
GetHuman: Let's quantify your experience contacting AT&T Universal Card. On a scale of 1 to 5, how easy is it go get help on a AT&T Universal Card problem?
GetHuman-276937: I'd give them a five 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-276937: I'd give them a five out of five on communication.
GetHuman: And what about AT&T Universal Card's ability to quickly and effectively address your problem?
GetHuman-276937: For that I would say four out of five.
GetHuman: And finally- any advice for other AT&T Universal Card customers?
GetHuman-276937: Call them early in the day or late. Don't forget any personal or account information you might need for AT&T Universal Card to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-276937 taken from his AT&T Universal Card customer service problem that occurred on November 21st, 2017.