The Baltimore Sun: My next door neighbor gets her paper every morn...
A The Baltimore Sun customer review by GetHuman user ~tesstemp from November 21st, 2017
Background on ~tesstemp's case
GetHuman: ~tesstemp - can you tell our other The Baltimore Sun customers when your case took place?
~tesstemp: Sure. It was middle of the night, on November 16th.
GetHuman: Did you reach out to The Baltimore Sun, and if so, how?
GetHuman: And which of these common The Baltimore Sun customer issues best describes the reason you wanted to talk to them?
(Shows ~tesstemp a list of common The Baltimore Sun problems)
~tesstemp: "Delivery problem" was why I was trying to call.
~tesstemp's review of The Baltimore Sun customer service
GetHuman: So how would you sum up your experience for GetHuman's The Baltimore Sun 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.
~tesstemp: My next door neighbor gets her paper every morning, Mine is simply not there. I call and am told they will correct the problem immediately and in * days I'll get that paper!
GetHuman: Let's quantify your experience contacting The Baltimore Sun. On a scale of 1 to 5, how easy is it go get help on a The Baltimore Sun problem?
~tesstemp: 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?
~tesstemp: I'd give them a three out of five on communication.
GetHuman: And what about The Baltimore Sun's ability to quickly and effectively address your problem?
~tesstemp: For that I would say two out of five.
GetHuman: And finally- any advice for other The Baltimore Sun customers?
~tesstemp: Call them early in the day or late. Don't forget any personal or account information you might need for The Baltimore Sun to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~tesstemp taken from his The Baltimore Sun customer service problem that occurred on November 16th, 2017.