NJ Unemployment: The Secretary of the Director answered and she...
A NJ Unemployment customer review by GetHuman user ~NY resident from November 26th, 2017
Background on ~NY resident's case
GetHuman: ~NY resident - can you tell our other NJ Unemployment customers when your case took place?
~NY resident: Sure. It was middle of the night, on November 23rd.
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 ~NY resident a list of common NJ Unemployment problems)
~NY resident: "Problem With a Claim" was why I was trying to call.
~NY resident'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.
~NY resident: The Secretary of the Director answered and she was kind enough to transfer to someone who was able to help me. They were both kind and patient. Pleasantly surprised.
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?
~NY resident: I'd give them a five 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?
~NY resident: I'd give them a four out of five on communication.
GetHuman: And what about NJ Unemployment's ability to quickly and effectively address your problem?
~NY resident: For that I would say five out of five.
GetHuman: And finally- any advice for other NJ Unemployment customers?
~NY resident: 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 ~NY resident taken from his NJ Unemployment customer service problem that occurred on November 23rd, 2017.