Viacom Inc.: The woman who answered the phone spoke like a d...
A Viacom Inc. customer review by GetHuman user ~JTFLA from November 20th, 2017
Background on ~JTFLA's case
GetHuman: ~JTFLA - can you tell our other Viacom Inc. customers when your case took place?
~JTFLA: Yeah. It was evening, on November 13th.
GetHuman: Did you reach out to Viacom Inc., and if so, how?
GetHuman: And which of these common Viacom Inc. customer issues best describes the reason you wanted to talk to them?
(Shows ~JTFLA a list of common Viacom Inc. problems)
~JTFLA: "None of those really matches why I wanted to call Viacom Inc. that day." was why I was trying to call.
~JTFLA's review of Viacom Inc. customer service
GetHuman: So how would you sum up your experience for GetHuman's Viacom Inc. 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.
~JTFLA: The woman who answered the phone spoke like a degenerate and was rude. I got transferred multiple times to extensions with no name or answer and could not get anyone to give me contact information for anyone or names or titles of anyone who could help me. ******!
GetHuman: Let's quantify your experience contacting Viacom Inc.. On a scale of 1 to 5, how easy is it go get help on a Viacom Inc. problem?
~JTFLA: 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?
~JTFLA: I'd give them a one out of five on communication.
GetHuman: And what about Viacom Inc.'s ability to quickly and effectively address your problem?
~JTFLA: For that I would say two out of five.
GetHuman: And finally- any advice for other Viacom Inc. customers?
~JTFLA: Call them early in the day or late. Don't forget any personal or account information you might need for Viacom Inc. to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~JTFLA taken from his Viacom Inc. customer service problem that occurred on November 13th, 2017.