Social Security: if they can not answer the phone due to high ca...
A Social Security customer review by GetHuman user ~your employer from November 17th, 2017
Background on ~your employer's case
GetHuman: ~your employer - can you tell our other Social Security customers when your case took place?
~your employer: Yes. It was evening, on November 8th.
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 ~your employer a list of common Social Security problems)
~your employer: "File a report" was why I was trying to call.
~your employer'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.
~your employer: if they can not answer the phone due to high call volume --- put more people on the line --- government jobs what a ******* joke --- stop watching honey boo-boo and do your ******* job- *** wipes
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?
~your employer: 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?
~your employer: 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?
~your employer: For that I would say four out of five.
GetHuman: And finally- any advice for other Social Security customers?
~your employer: 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 ~your employer taken from his Social Security customer service problem that occurred on November 8th, 2017.