New York Times: Wow! for the Get Human and Wow! for NY times cu...
A New York Times customer review by GetHuman user ~scavengergrrl from November 11th, 2017
Background on ~scavengergrrl's case
GetHuman: ~scavengergrrl - can you tell our other New York Times customers when your case took place?
~scavengergrrl: Yes. It was afternoon, on November 6th.
GetHuman: Did you reach out to New York Times, and if so, how?
GetHuman: And which of these common New York Times customer issues best describes the reason you wanted to talk to them?
(Shows ~scavengergrrl a list of common New York Times problems)
~scavengergrrl: "Delivery problem" was why I was trying to call.
~scavengergrrl's review of New York Times customer service
GetHuman: So how would you sum up your experience for GetHuman's New York Times 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.
~scavengergrrl: Wow! for the Get Human and Wow! for NY times customer service!! Don't know why you can't get thru on NY service number because their service rep was FANTASTIC!
GetHuman: Let's quantify your experience contacting New York Times. On a scale of 1 to 5, how easy is it go get help on a New York Times problem?
~scavengergrrl: 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?
~scavengergrrl: I'd give them a two out of five on communication.
GetHuman: And what about New York Times's ability to quickly and effectively address your problem?
~scavengergrrl: For that I would say five out of five.
GetHuman: And finally- any advice for other New York Times customers?
~scavengergrrl: Call them early in the day or late. Don't forget any personal or account information you might need for New York Times to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~scavengergrrl taken from his New York Times customer service problem that occurred on November 6th, 2017.