NJ Unemployment: I waited almost ** minutes just so the voice ca...
Una NJ Unemployment reseña del cliente por el usuario de GetHuman GetHuman-19253 de noviembre 17º, 2017
Background on GetHuman-19253's case
GetHuman: GetHuman-19253 - can you tell our other NJ Unemployment customers when your case took place?
GetHuman-19253: Yup. It was afternoon, on noviembre 15º.
GetHuman: Did you reach out to NJ Unemployment, and if so, how?
GetHuman: And which of these common NJ Unemployment customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-19253 a list of common NJ Unemployment problems)
GetHuman-19253: "Make a Claim" was why I was trying to call.
GetHuman-19253's review of NJ Unemployment customer service
GetHuman: So how would you sum up your experience for GetHuman's NJ Unemployment 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-19253: I waited almost ** minutes just so the voice can say "we are unable to take this call. Please hang up and dial again" WHAT?!
GetHuman: Let's quantify your experience contacting NJ Unemployment. On a scale of 1 to 5, how easy is it go get help on a NJ Unemployment problem?
GetHuman-19253: 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?
GetHuman-19253: I'd give them a five out of five on communication.
GetHuman: And what about NJ Unemployment's ability to quickly and effectively address your problem?
GetHuman-19253: For that I would say three out of five.
GetHuman: And finally- any advice for other NJ Unemployment customers?
GetHuman-19253: Llámalos temprano en el día o tarde. No olvide ninguna información personal o de cuenta que pueda necesitar para NJ Unemployment para saber quién es usted.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-19253 taken from his NJ Unemployment customer service problem that occurred on noviembre 15º, 2017.