Issue with Sacramento Bee
A Sacramento Bee customer review by GetHuman user GetHuman-alanlang from December 7th, 2017
Background on GetHuman-alanlang's case
GetHuman: GetHuman-alanlang - can you tell our other Sacramento Bee customers when your case took place?
GetHuman-alanlang: Yeah. It was middle of the night, on December 6th.
GetHuman: Did you reach out to Sacramento Bee, and if so, how?
GetHuman: And which of these common Sacramento Bee customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-alanlang a list of common Sacramento Bee problems)
GetHuman-alanlang: "Delivery problem" was why I was trying to call.
GetHuman-alanlang's review of Sacramento Bee customer service
GetHuman: So how would you sum up your experience for GetHuman's Sacramento Bee 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-alanlang: Issue with Sacramento Bee
GetHuman: Can you tell the rest of us a bit more from what happened on 12/06/17?
GetHuman-alanlang: Did not get all of news paper
GetHuman: Let's quantify your experience contacting Sacramento Bee. On a scale of 1 to 5, how easy is it go get help on a Sacramento Bee problem?
GetHuman-alanlang: 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-alanlang: I'd give them a three out of five on communication.
GetHuman: And what about Sacramento Bee's ability to quickly and effectively address your problem?
GetHuman-alanlang: For that I would say two out of five.
GetHuman: And finally- any advice for other Sacramento Bee customers?
GetHuman-alanlang: Call them early in the day or late. Don't forget any personal or account information you might need for Sacramento Bee to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-alanlang taken from his Sacramento Bee customer service problem that occurred on December 6th, 2017.