Orlando Sentinel: Was looking for local contact number but got ov...
A Orlando Sentinel customer review by GetHuman user GetHuman-140273 from November 11th, 2017
Background on GetHuman-140273's case
GetHuman: GetHuman-140273 - can you tell our other Orlando Sentinel customers when your case took place?
GetHuman-140273: Yup. It was middle of the night, on November 4th.
GetHuman: Did you reach out to Orlando Sentinel, and if so, how?
GetHuman: And which of these common Orlando Sentinel customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-140273 a list of common Orlando Sentinel problems)
GetHuman-140273: "Delivery problem" was why I was trying to call.
GetHuman-140273's review of Orlando Sentinel customer service
GetHuman: So how would you sum up your experience for GetHuman's Orlando Sentinel 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-140273: Was looking for local contact number but got overseas (Philippines) assistance that was not helpful to begin with.
GetHuman: Let's quantify your experience contacting Orlando Sentinel. On a scale of 1 to 5, how easy is it go get help on a Orlando Sentinel problem?
GetHuman-140273: 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?
GetHuman-140273: I'd give them a one out of five on communication.
GetHuman: And what about Orlando Sentinel's ability to quickly and effectively address your problem?
GetHuman-140273: For that I would say two out of five.
GetHuman: And finally- any advice for other Orlando Sentinel customers?
GetHuman-140273: Call them early in the day or late. Don't forget any personal or account information you might need for Orlando Sentinel to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-140273 taken from his Orlando Sentinel customer service problem that occurred on November 4th, 2017.