Kansas City Star: The customer service employees worked from the...
A Kansas City Star customer review by GetHuman user ~Hskeh from November 24th, 2017
Background on ~Hskeh's case
GetHuman: ~Hskeh - can you tell our other Kansas City Star customers when your case took place?
~Hskeh: Yes I can. It was morning, on November 15th.
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 ~Hskeh a list of common Kansas City Star problems)
~Hskeh: "Complaint" was why I was trying to call.
~Hskeh'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.
~Hskeh: The customer service employees worked from the Philippines, not from Kansas City, so they had no way of understanding or fixing the problem. However, the email option didn't work either. I tried * times over * days and never received a reply.
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?
~Hskeh: 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?
~Hskeh: 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?
~Hskeh: For that I would say one out of five.
GetHuman: And finally- any advice for other Kansas City Star customers?
~Hskeh: 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 ~Hskeh taken from his Kansas City Star customer service problem that occurred on November 15th, 2017.