Kansas City Star: I don't want to talk to a answering service, th...
A Kansas City Star customer review by GetHuman user GetHuman-331193 from November 19th, 2017
Background on GetHuman-331193's case
GetHuman: GetHuman-331193 - can you tell our other Kansas City Star customers when your case took place?
GetHuman-331193: Yup. It was morning, on November 9th.
GetHuman: Did you reach out to Kansas City Star, and if so, how?
GetHuman: And which of these common Kansas City Star customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-331193 a list of common Kansas City Star problems)
GetHuman-331193: "Complaint" was why I was trying to call.
GetHuman-331193's review of Kansas City Star customer service
GetHuman: So how would you sum up your experience for GetHuman's Kansas City Star 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-331193: I don't want to talk to a answering service, they don't know anything. whatever happened to custumer service who actually work at the star.
GetHuman: Let's quantify your experience contacting Kansas City Star. On a scale of 1 to 5, how easy is it go get help on a Kansas City Star problem?
GetHuman-331193: 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-331193: I'd give them a five out of five on communication.
GetHuman: And what about Kansas City Star's ability to quickly and effectively address your problem?
GetHuman-331193: For that I would say one out of five.
GetHuman: And finally- any advice for other Kansas City Star customers?
GetHuman-331193: Call them early in the day or late. Don't forget any personal or account information you might need for Kansas City Star to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-331193 taken from his Kansas City Star customer service problem that occurred on November 9th, 2017.