Houston Chronicle: Keep hitting * and you will speak to a rep. No...
A Houston Chronicle customer review by GetHuman user ~anonymous from November 20th, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other Houston Chronicle customers when your case took place?
~anonymous: Yup. It was afternoon, on November 10th.
GetHuman: Did you reach out to Houston Chronicle, and if so, how?
GetHuman: And which of these common Houston Chronicle customer issues best describes the reason you wanted to talk to them?
(Shows ~anonymous a list of common Houston Chronicle problems)
~anonymous: "Delivery issue" was why I was trying to call.
~anonymous's review of Houston Chronicle customer service
GetHuman: So how would you sum up your experience for GetHuman's Houston Chronicle 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: Keep hitting * and you will speak to a rep. Now if speaking to a rep helps with delivery service* that's another issue, but at least you get to speak to someone regarding poor service.
GetHuman: Let's quantify your experience contacting Houston Chronicle. On a scale of 1 to 5, how easy is it go get help on a Houston Chronicle problem?
~anonymous: I'd give them a four 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 one out of five on communication.
GetHuman: And what about Houston Chronicle's ability to quickly and effectively address your problem?
~anonymous: For that I would say one out of five.
GetHuman: And finally- any advice for other Houston Chronicle customers?
~anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Houston Chronicle to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his Houston Chronicle customer service problem that occurred on November 10th, 2017.