St. Louis Post-Dispatch: Been working on a delivery problem for * weeks...
A St. Louis Post-Dispatch customer review by GetHuman user ~Mike from November 16th, 2017
Background on ~Mike's case
GetHuman: ~Mike - can you tell our other St. Louis Post-Dispatch customers when your case took place?
~Mike: Sure. It was middle of the night, on November 11th.
GetHuman: Did you reach out to St. Louis Post-Dispatch, and if so, how?
GetHuman: And which of these common St. Louis Post-Dispatch customer issues best describes the reason you wanted to talk to them?
(Shows ~Mike a list of common St. Louis Post-Dispatch problems)
~Mike: "Lower my bill" was why I was trying to call.
~Mike's review of St. Louis Post-Dispatch customer service
GetHuman: So how would you sum up your experience for GetHuman's St. Louis Post-Dispatch 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.
~Mike: Been working on a delivery problem for * weeks, not solved and promised phone calls from supervisor have not happened. Customer Service? A JOKE!
GetHuman: Let's quantify your experience contacting St. Louis Post-Dispatch. On a scale of 1 to 5, how easy is it go get help on a St. Louis Post-Dispatch problem?
~Mike: I'd give them a three 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?
~Mike: I'd give them a four out of five on communication.
GetHuman: And what about St. Louis Post-Dispatch's ability to quickly and effectively address your problem?
~Mike: For that I would say five out of five.
GetHuman: And finally- any advice for other St. Louis Post-Dispatch customers?
~Mike: Call them early in the day or late. Don't forget any personal or account information you might need for St. Louis Post-Dispatch to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Mike taken from his St. Louis Post-Dispatch customer service problem that occurred on November 11th, 2017.