The New Yorker: Amazing. To find their phone number! Their emai...
A The New Yorker customer review by GetHuman user GetHuman-410711 from November 3rd, 2017
Background on GetHuman-410711's case
GetHuman: GetHuman-410711 - can you tell our other The New Yorker customers when your case took place?
GetHuman-410711: Sure. It was evening, on October 26th.
GetHuman: Did you reach out to The New Yorker, and if so, how?
GetHuman: And which of these common The New Yorker customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-410711 a list of common The New Yorker problems)
GetHuman-410711: "None of those really matches why I wanted to call The New Yorker that day." was why I was trying to call.
GetHuman-410711's review of The New Yorker customer service
GetHuman: So how would you sum up your experience for GetHuman's The New Yorker 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-410711: Amazing. To find their phone number! Their email customer service regarding a subscription was useless.
GetHuman: Let's quantify your experience contacting The New Yorker. On a scale of 1 to 5, how easy is it go get help on a The New Yorker problem?
GetHuman-410711: 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?
GetHuman-410711: I'd give them a five out of five on communication.
GetHuman: And what about The New Yorker's ability to quickly and effectively address your problem?
GetHuman-410711: For that I would say four out of five.
GetHuman: And finally- any advice for other The New Yorker customers?
GetHuman-410711: Call them early in the day or late. Don't forget any personal or account information you might need for The New Yorker to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-410711 taken from his The New Yorker customer service problem that occurred on October 26th, 2017.