Orlando Sentinel: the call went well. I will have to wait until T...
A Orlando Sentinel customer review by GetHuman user ~wantmy paper from November 25th, 2017
Background on ~wantmy paper's case
GetHuman: ~wantmy paper - can you tell our other Orlando Sentinel customers when your case took place?
~wantmy paper: Yes. It was afternoon, on November 22nd.
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 ~wantmy paper a list of common Orlando Sentinel problems)
~wantmy paper: "Cancel subscription" was why I was trying to call.
~wantmy paper'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.
~wantmy paper: the call went well. I will have to wait until Thursday to see if my subscription is back on track though. Billing error on the part of the paper.
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?
~wantmy paper: I'd give them a one 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?
~wantmy paper: I'd give them a four out of five on communication.
GetHuman: And what about Orlando Sentinel's ability to quickly and effectively address your problem?
~wantmy paper: For that I would say one out of five.
GetHuman: And finally- any advice for other Orlando Sentinel customers?
~wantmy paper: 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 ~wantmy paper taken from his Orlando Sentinel customer service problem that occurred on November 22nd, 2017.