Social Security: Worst phone tree I've ever had the misfortune t...
A Social Security customer review by GetHuman user ~Charlie from November 3rd, 2017
Background on ~Charlie's case
GetHuman: ~Charlie - can you tell our other Social Security customers when your case took place?
~Charlie: Yes. It was morning, on October 27th.
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 ~Charlie a list of common Social Security problems)
~Charlie: "Can't Login" was why I was trying to call.
~Charlie'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.
~Charlie: Worst phone tree I've ever had the misfortune to encounter. SS published number was a nightmare of electronic voices. I knew I was losing it when I started shouting at the phone. So I went to Medicare at GetHuman and that number got me a human much faster, although certainly not "fast".
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?
~Charlie: 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?
~Charlie: 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?
~Charlie: For that I would say four out of five.
GetHuman: And finally- any advice for other Social Security customers?
~Charlie: 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 ~Charlie taken from his Social Security customer service problem that occurred on October 27th, 2017.