Wall Street Journal: I have called over ** times and the call gets r...
A Wall Street Journal customer review by GetHuman user ~gentleman from November 21st, 2017
Background on ~gentleman's case
GetHuman: ~gentleman - can you tell our other Wall Street Journal customers when your case took place?
~gentleman: Yeah. It was morning, on November 18th.
GetHuman: Did you reach out to Wall Street Journal, and if so, how?
GetHuman: And which of these common Wall Street Journal customer issues best describes the reason you wanted to talk to them?
(Shows ~gentleman a list of common Wall Street Journal problems)
~gentleman: "Cancel subscription" was why I was trying to call.
~gentleman's review of Wall Street Journal customer service
GetHuman: So how would you sum up your experience for GetHuman's Wall Street Journal 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.
~gentleman: I have called over ** times and the call gets routed to philipines, nothing is ever done. the most horrible service I have encountered from a paper
GetHuman: Let's quantify your experience contacting Wall Street Journal. On a scale of 1 to 5, how easy is it go get help on a Wall Street Journal problem?
~gentleman: 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?
~gentleman: I'd give them a one out of five on communication.
GetHuman: And what about Wall Street Journal's ability to quickly and effectively address your problem?
~gentleman: For that I would say two out of five.
GetHuman: And finally- any advice for other Wall Street Journal customers?
~gentleman: Call them early in the day or late. Don't forget any personal or account information you might need for Wall Street Journal to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~gentleman taken from his Wall Street Journal customer service problem that occurred on November 18th, 2017.