Denver Post: I never get my delivery without calling, and ev...
A Denver Post customer review by GetHuman user ~Anonymous from November 28th, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other Denver Post customers when your case took place?
~Anonymous: Yes I can. It was middle of the night, on November 27th.
GetHuman: Did you reach out to Denver Post, and if so, how?
GetHuman: And which of these common Denver Post customer issues best describes the reason you wanted to talk to them?
(Shows ~Anonymous a list of common Denver Post problems)
~Anonymous: "Lower my bill" was why I was trying to call.
~Anonymous's review of Denver Post customer service
GetHuman: So how would you sum up your experience for GetHuman's Denver 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.
~Anonymous: I never get my delivery without calling, and even then most times I don't get a re-delivery. How does my area carrier still have a job?! Supervisor assured me it'll be taken care of, but I've heard that over a dozen times without results.
GetHuman: Let's quantify your experience contacting Denver Post. On a scale of 1 to 5, how easy is it go get help on a Denver Post problem?
~Anonymous: I'd give them a one 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?
~Anonymous: I'd give them a two out of five on communication.
GetHuman: And what about Denver Post's ability to quickly and effectively address your problem?
~Anonymous: For that I would say five out of five.
GetHuman: And finally- any advice for other Denver Post customers?
~Anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Denver Post to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his Denver Post customer service problem that occurred on November 27th, 2017.