San Francisco Chronicle: The primary announcement should be that one is...
A San Francisco Chronicle customer review by GetHuman user ~numskull from November 16th, 2017
Background on ~numskull's case
GetHuman: ~numskull - can you tell our other San Francisco Chronicle customers when your case took place?
~numskull: Yes. It was late at night, on November 6th.
GetHuman: Did you reach out to San Francisco Chronicle, and if so, how?
GetHuman: And which of these common San Francisco Chronicle customer issues best describes the reason you wanted to talk to them?
(Shows ~numskull a list of common San Francisco Chronicle problems)
~numskull: "Lower my bill" was why I was trying to call.
~numskull's review of San Francisco Chronicle customer service
GetHuman: So how would you sum up your experience for GetHuman's San Francisco Chronicle 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.
~numskull: The primary announcement should be that one is calling after hours so we dont have to listen to all the CHOICES
GetHuman: Let's quantify your experience contacting San Francisco Chronicle. On a scale of 1 to 5, how easy is it go get help on a San Francisco Chronicle problem?
~numskull: I'd give them a two 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?
~numskull: I'd give them a five out of five on communication.
GetHuman: And what about San Francisco Chronicle's ability to quickly and effectively address your problem?
~numskull: For that I would say four out of five.
GetHuman: And finally- any advice for other San Francisco Chronicle customers?
~numskull: Call them early in the day or late. Don't forget any personal or account information you might need for San Francisco Chronicle to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~numskull taken from his San Francisco Chronicle customer service problem that occurred on November 6th, 2017.