Pittsburgh Post-Gazette: Awful. * phone falls before I found somebody...
A Pittsburgh Post-Gazette customer review by GetHuman user ~anonymous from November 26th, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other Pittsburgh Post-Gazette customers when your case took place?
~anonymous: Yup. It was morning, on November 19th.
GetHuman: Did you reach out to Pittsburgh Post-Gazette, and if so, how?
GetHuman: And which of these common Pittsburgh Post-Gazette customer issues best describes the reason you wanted to talk to them?
(Shows ~anonymous a list of common Pittsburgh Post-Gazette problems)
~anonymous: "Complaint" was why I was trying to call.
~anonymous's review of Pittsburgh Post-Gazette customer service
GetHuman: So how would you sum up your experience for GetHuman's Pittsburgh Post-Gazette 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.
~anonymous: Awful. * phone falls before I found somebody: total time about ** min. Dropped my subscription as a result.
GetHuman: Let's quantify your experience contacting Pittsburgh Post-Gazette. On a scale of 1 to 5, how easy is it go get help on a Pittsburgh Post-Gazette problem?
~anonymous: 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?
~anonymous: I'd give them a four out of five on communication.
GetHuman: And what about Pittsburgh Post-Gazette's ability to quickly and effectively address your problem?
~anonymous: For that I would say one out of five.
GetHuman: And finally- any advice for other Pittsburgh Post-Gazette customers?
~anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Pittsburgh Post-Gazette to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his Pittsburgh Post-Gazette customer service problem that occurred on November 19th, 2017.