Newark Star Ledger: It is impossible to get help on Sunday! This i...
A Newark Star Ledger customer review by GetHuman user GetHuman-306761 from November 22nd, 2017
Background on GetHuman-306761's case
GetHuman: GetHuman-306761 - can you tell our other Newark Star Ledger customers when your case took place?
GetHuman-306761: Sure. It was afternoon, on November 19th.
GetHuman: Did you reach out to Newark Star Ledger, and if so, how?
GetHuman: And which of these common Newark Star Ledger customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-306761 a list of common Newark Star Ledger problems)
GetHuman-306761: "Complaint" was why I was trying to call.
GetHuman-306761's review of Newark Star Ledger customer service
GetHuman: So how would you sum up your experience for GetHuman's Newark Star Ledger 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-306761: It is impossible to get help on Sunday! This is the third day I have not received my newspaper! Very unhappy!
GetHuman: Let's quantify your experience contacting Newark Star Ledger. On a scale of 1 to 5, how easy is it go get help on a Newark Star Ledger problem?
GetHuman-306761: I'd give them a four 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-306761: I'd give them a one out of five on communication.
GetHuman: And what about Newark Star Ledger's ability to quickly and effectively address your problem?
GetHuman-306761: For that I would say four out of five.
GetHuman: And finally- any advice for other Newark Star Ledger customers?
GetHuman-306761: Call them early in the day or late. Don't forget any personal or account information you might need for Newark Star Ledger to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-306761 taken from his Newark Star Ledger customer service problem that occurred on November 19th, 2017.