Social Security: they did not acknowledge me on the phone. they...
A Social Security customer review by GetHuman user ~daisysunshine from November 22nd, 2017
Background on ~daisysunshine's case
GetHuman: ~daisysunshine - can you tell our other Social Security customers when your case took place?
~daisysunshine: Yup. It was afternoon, on November 19th.
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 ~daisysunshine a list of common Social Security problems)
~daisysunshine: "Question About Benefits" was why I was trying to call.
~daisysunshine'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.
~daisysunshine: they did not acknowledge me on the phone. they carried on a personal conversation and did not assist me at all. horrible customer service
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?
~daisysunshine: 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?
~daisysunshine: I'd give them a five out of five on communication.
GetHuman: And what about Social Security's ability to quickly and effectively address your problem?
~daisysunshine: For that I would say two out of five.
GetHuman: And finally- any advice for other Social Security customers?
~daisysunshine: 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 ~daisysunshine taken from his Social Security customer service problem that occurred on November 19th, 2017.