Chicago Tribune: Call was answered within seconds after hearing...
A Chicago Tribune customer review by GetHuman user GetHuman-134326 from November 18th, 2017
Background on GetHuman-134326's case
GetHuman: GetHuman-134326 - can you tell our other Chicago Tribune customers when your case took place?
GetHuman-134326: Sure. It was afternoon, on November 13th.
GetHuman: Did you reach out to Chicago Tribune, and if so, how?
GetHuman: And which of these common Chicago Tribune customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-134326 a list of common Chicago Tribune problems)
GetHuman-134326: "Cancel subscription" was why I was trying to call.
GetHuman-134326's review of Chicago Tribune customer service
GetHuman: So how would you sum up your experience for GetHuman's Chicago Tribune 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-134326: Call was answered within seconds after hearing only busy signal from the other number. Rep was very hard to understand. He mumbled and talked too fast.
GetHuman: Let's quantify your experience contacting Chicago Tribune. On a scale of 1 to 5, how easy is it go get help on a Chicago Tribune problem?
GetHuman-134326: 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?
GetHuman-134326: I'd give them a four out of five on communication.
GetHuman: And what about Chicago Tribune's ability to quickly and effectively address your problem?
GetHuman-134326: For that I would say five out of five.
GetHuman: And finally- any advice for other Chicago Tribune customers?
GetHuman-134326: Call them early in the day or late. Don't forget any personal or account information you might need for Chicago Tribune to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-134326 taken from his Chicago Tribune customer service problem that occurred on November 13th, 2017.