NJ Unemployment: * *** hours & still waiting. How about you hire...
A NJ Unemployment customer review by GetHuman user ~Action Bronson from November 25th, 2017
Background on ~Action Bronson's case
GetHuman: ~Action Bronson - can you tell our other NJ Unemployment customers when your case took place?
~Action Bronson: Yes I can. It was middle of the night, on November 17th.
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 ~Action Bronson a list of common NJ Unemployment problems)
~Action Bronson: "File application" was why I was trying to call.
~Action Bronson'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.
~Action Bronson: * *** hours & still waiting. How about you hire some of us "unemployed" to help you clowns answer the phones?!?!?! Only in Merica
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?
~Action Bronson: 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?
~Action Bronson: I'd give them a one out of five on communication.
GetHuman: And what about NJ Unemployment's ability to quickly and effectively address your problem?
~Action Bronson: For that I would say five out of five.
GetHuman: And finally- any advice for other NJ Unemployment customers?
~Action Bronson: Call them early in the day or late. Don't forget any personal or account information you might need for NJ Unemployment to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Action Bronson taken from his NJ Unemployment customer service problem that occurred on November 17th, 2017.