This number for the Washington Post I found qui...
A Washington Post customer review by GetHuman user ~criggs from November 24th, 2017
Background on ~criggs's case
GetHuman: ~criggs - can you tell our other Washington Post customers when your case took place?
~criggs: Sure. It was morning, on November 21st.
GetHuman: Did you reach out to Washington Post, and if so, how?
GetHuman: And which of these common Washington Post customer issues best describes the reason you wanted to talk to them?
(Shows ~criggs a list of common Washington Post problems)
~criggs: "Cancel or change subscription" was why I was trying to call.
~criggs's review of Washington Post customer service
GetHuman: So how would you sum up your experience for GetHuman's Washington Post 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.
~criggs: This number for the Washington Post I found quite useless. It connects to some clueless phone jockeys who don't know their backside from a hole in the ground and simply pass along messages that they really don't understand* waste of time.
GetHuman: Let's quantify your experience contacting Washington Post. On a scale of 1 to 5, how easy is it go get help on a Washington Post problem?
~criggs: 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?
~criggs: I'd give them a five out of five on communication.
GetHuman: And what about Washington Post's ability to quickly and effectively address your problem?
~criggs: For that I would say one out of five.
GetHuman: And finally- any advice for other Washington Post customers?
~criggs: Call them early in the day or late. Don't forget any personal or account information you might need for Washington Post to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~criggs taken from his Washington Post customer service problem that occurred on November 21st, 2017.