NJ Unemployment: Have called all day for the last * days to be h...
A NJ Unemployment customer review by GetHuman user GetHuman-195904 from November 26th, 2017
Background on GetHuman-195904's case
GetHuman: GetHuman-195904 - can you tell our other NJ Unemployment customers when your case took place?
GetHuman-195904: Yes. It was middle of the night, on November 22nd.
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-195904 a list of common NJ Unemployment problems)
GetHuman-195904: "Account Access" was why I was trying to call.
GetHuman-195904'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-195904: Have called all day for the last * days to be hung up or told the lines are busy I am finding a real live person to talk to now
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-195904: 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-195904: I'd give them a three out of five on communication.
GetHuman: And what about NJ Unemployment's ability to quickly and effectively address your problem?
GetHuman-195904: For that I would say five out of five.
GetHuman: And finally- any advice for other NJ Unemployment customers?
GetHuman-195904: 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 GetHuman-195904 taken from his NJ Unemployment customer service problem that occurred on November 22nd, 2017.