Social Security: when we finally got a real human,that knew what...
Una recensione del cliente Social Security da parte dell'utente GetHuman GetHuman-294901 da novembre 9º, 2017
Background on GetHuman-294901's case
GetHuman: GetHuman-294901 - can you tell our other Social Security customers when your case took place?
GetHuman-294901: Sure. It was late at night, on novembre 1º.
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-294901 a list of common Social Security problems)
GetHuman-294901: "Missing Payment" was why I was trying to call.
GetHuman-294901'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-294901: when we finally got a real human,that knew what he was doing!, we got service. the lady was terrible
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-294901: 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?
GetHuman-294901: I'd give them a three out of five on communication.
GetHuman: And what about Social Security's ability to quickly and effectively address your problem?
GetHuman-294901: For that I would say four out of five.
GetHuman: And finally- any advice for other Social Security customers?
GetHuman-294901: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Social Security sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-294901 taken from his Social Security customer service problem that occurred on novembre 1º, 2017.