Houston Chronicle: HORRIBLE HORRIBLE SERVICE.....WHY DO THEY HAVE...
A Houston Chronicle customer review by GetHuman user GetHuman-159481 from November 19th, 2017
Background on GetHuman-159481's case
GetHuman: GetHuman-159481 - can you tell our other Houston Chronicle customers when your case took place?
GetHuman-159481: Sure. It was middle of the night, on November 18th.
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 GetHuman-159481 a list of common Houston Chronicle problems)
GetHuman-159481: "Refund" was why I was trying to call.
GetHuman-159481'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.
GetHuman-159481: HORRIBLE HORRIBLE SERVICE.....WHY DO THEY HAVE VACATION HOLD? DO THEY KNOW WHAT VACATION HOLD IS ALL ABOUT?
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?
GetHuman-159481: 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?
GetHuman-159481: I'd give them a five out of five on communication.
GetHuman: And what about Houston Chronicle's ability to quickly and effectively address your problem?
GetHuman-159481: For that I would say four out of five.
GetHuman: And finally- any advice for other Houston Chronicle customers?
GetHuman-159481: 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 GetHuman-159481 taken from his Houston Chronicle customer service problem that occurred on November 18th, 2017.