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