Fox News: She listened to me, then had a non-empathatic a...
A Fox News customer review by GetHuman user ~mandee from November 26th, 2017
Background on ~mandee's case
GetHuman: ~mandee - can you tell our other Fox News customers when your case took place?
~mandee: Yup. It was afternoon, on November 16th.
GetHuman: Did you reach out to Fox News, and if so, how?
GetHuman: And which of these common Fox News customer issues best describes the reason you wanted to talk to them?
(Shows ~mandee a list of common Fox News problems)
~mandee: "Update Account Info" was why I was trying to call.
~mandee's review of Fox News customer service
GetHuman: So how would you sum up your experience for GetHuman's Fox News 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.
~mandee: She listened to me, then had a non-empathatic attitude and obviously did not appear to listen and insultantely asked..." and how can Fox news help you with this situation?" as a war vet and as this is a very serious situation about me and my life...it would have been a better relationship if I felt welcomed to Fox News...not rejected.
GetHuman: Let's quantify your experience contacting Fox News. On a scale of 1 to 5, how easy is it go get help on a Fox News problem?
~mandee: I'd give them a four 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?
~mandee: I'd give them a one out of five on communication.
GetHuman: And what about Fox News's ability to quickly and effectively address your problem?
~mandee: For that I would say one out of five.
GetHuman: And finally- any advice for other Fox News customers?
~mandee: Call them early in the day or late. Don't forget any personal or account information you might need for Fox News to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~mandee taken from his Fox News customer service problem that occurred on November 16th, 2017.