Social Security: One word, Rude. First call, rude told me to go...
A Social Security customer review by GetHuman user GetHuman-245008 from October 30th, 2017
Background on GetHuman-245008's case
GetHuman: GetHuman-245008 - can you tell our other Social Security customers when your case took place?
GetHuman-245008: Yup. It was middle of the night, on October 22nd.
GetHuman: Did you reach out to Social Security, and if so, how?
GetHuman: And which of these common Social Security customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-245008 a list of common Social Security problems)
GetHuman-245008: "Update Account Info" was why I was trying to call.
GetHuman-245008's review of Social Security customer service
GetHuman: So how would you sum up your experience for GetHuman's Social Security 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-245008: One word, Rude. First call, rude told me to go to local office. Second call, got data correct but still rude**A pain in the ***
GetHuman: Let's quantify your experience contacting Social Security. On a scale of 1 to 5, how easy is it go get help on a Social Security problem?
GetHuman-245008: I'd give them a three 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-245008: I'd give them a two out of five on communication.
GetHuman: And what about Social Security's ability to quickly and effectively address your problem?
GetHuman-245008: For that I would say one out of five.
GetHuman: And finally- any advice for other Social Security customers?
GetHuman-245008: Call them early in the day or late. Don't forget any personal or account information you might need for Social Security to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-245008 taken from his Social Security customer service problem that occurred on October 22nd, 2017.