Social Security: THE PERSON I SPOKE TO WAS VERY HELPFUL. I DON'T...
Social Security Ulasan pelanggan oleh pengguna GetHuman ~jbar4650 dari November 19, 2017
Background on ~jbar4650's case
GetHuman: ~jbar4650 - can you tell our other Social Security customers when your case took place?
~jbar4650: Yup. It was afternoon, on November 11.
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 ~jbar4650 a list of common Social Security problems)
~jbar4650: "Complaint" was why I was trying to call.
~jbar4650'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.
~jbar4650: THE PERSON I SPOKE TO WAS VERY HELPFUL. I DON'T KNOW WHY PEOPLE ARE COMPLAINING ABOUT THE WAIT TIME BECAUSE AFTER ALL THERE ARE A LOT OF PEOPLE CALLING AND YOU HAVE TO EXPECT THAT IT WILL TAKE A WHILE FOR SOMEONE TO GET TO YOU
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?
~jbar4650: 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?
~jbar4650: I'd give them a four out of five on communication.
GetHuman: And what about Social Security's ability to quickly and effectively address your problem?
~jbar4650: For that I would say one out of five.
GetHuman: And finally- any advice for other Social Security customers?
~jbar4650: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Social Security mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from ~jbar4650 taken from his Social Security customer service problem that occurred on November 11, 2017.